- User Since
- Feb 14 2017, 10:57 AM (244 w, 3 d)
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:
- as you analyzed: recognize the deposit in the UI
- recognize in the deposit storage, what is the source (origin) of the deposit
- here it happens that the deposit itself is only metadata
- identify which deposits are metadata-only deposits
This can be resolved :-)
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.
Tue, Oct 19
Mon, Oct 18
@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
Fri, Oct 15
Thu, Oct 14
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.
Wed, Oct 13
Tue, Oct 12
Fri, Oct 1
- September 2021 update
The features page is online and accessible for admins and ambassadors to get feedback:
Sep 22 2021
Sep 13 2021
Sep 10 2021
Checklist available here:
Sep 9 2021
Sep 8 2021
Sep 7 2021
Good idea to add this documentation!
I have added a few comments.
Sep 3 2021
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
Sep 2 2021
@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.
Aug 31 2021
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).
Aug 30 2021
@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.
Aug 27 2021
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.
Aug 26 2021
This looks great!
Aug 20 2021
Aug 18 2021
@sdruskat Good news about the GitHub support.