In T3677#72924, @vlorentz wrote:

Oh and another use-case we discussed: when browsing an origin/directory/..., showing on the side the set of sources that provided metadata for that origin/directory/.... This is, again, to improve discoverability.

Following our discussion, we might call the tag metadata-source, since using the term origin for metadata can be misleading.

Why do we want that:

1. as you analyzed: recognize the deposit in the UI
2. recognize in the deposit storage, what is the source (origin) of the deposit
   • here it happens that the deposit itself is only metadata
3. identify which deposits are metadata-only deposits

This can be resolved :-)

In T3677#72872, @vlorentz wrote:

The same might be true when the target is an origin-url.

It's not

This should be tested with a deposit of metadata-only with the target origin.
When the SWHID is without context the column origin in the deposit admin view shows the SWHID, which is very confusing by the wey.

I think we (or I should say- I) missed ambiguity of the concept origin.

Yes context is a better option.
Then target is not in the grouped context.

this is old. I think this is resolved..
@ardumont , @anlambert ?

@anlambert here is another task to improve the deposit moderation/admin view

@anlambert here is the task we have briefly discussed as step 2 this morning

https://docs.softwareheritage.org/devel/contributing/tutorial-docs-contribution.html#doc-contribution

We have followed the plan on the hedgedoc (in the last comment).
Just realized we haven't decided if the support-tools should be in sys-admin dimension, so I'm adding this to this task to decide.

@olasd , @ardumont and @vsellier : I think that we can gently resolve this task.

1. September 2021 update

The features page is online and accessible for admins and ambassadors to get feedback:
https://www.softwareheritage.org/features/

Checklist available here:
https://hedgedoc.softwareheritage.org/InevnioRDM-SWH-checklist?both

Good idea to add this documentation!
I have added a few comments.

Leave as is for a first deployment.
We will test on the partners platform and iterate.

This is really good!
I discussed this option with Kat from Data Current (in charge of the SWH stories interface) and she was wondering if the highlighted text will be centered.
Seems from your example that this will be the case.

@anlambert we have discussed this task this morning with @ardumont and @vlorentz.
I want to start working on the improvements of the deposit admin view to open it up for deposit clients.
Would you have time during September to help on this task? (it is a roadmap task, btw)

To discuss with @rdicosmo

@anlambert : Looks very good!
Can you show an example for a code fragment where you view a content with a few lines marked-up ?

Ipol's editor has agreed that this solution will be good for their use case.

At the moment, I think that all the properties you have selected in the task are needed.
+1 for License (it is something they show on the interface even if it is based on a heuristic).

@anlambert; after discussing with @rdicosmo, here are a few context elements:
We are working on different use cases for the iframe, the first is a rather simpler one with the SWH stories, where just having the source code in a minimalist way is best.
In the future we will also need to answer a more complex use-case where the iframe resembles more as an embedded copy of the archive.

That's really nice, but I still prefer the minimalist first iframe :-)

Looks better with the first implementation with "Go to the archive" :-)
With the badge, it seems right and left side aren't balanced.

This looks great!

@sdruskat Good news about the GitHub support.