The page can go now to validation in my opinion: https://www.softwareheritage.org/community/users/ (published privately)

Here are a few suggestion to the user community page:

FAQ living document is still here (awaiting a more permanent home on a new repository swh-ambassadors):
https://hedgedoc.softwareheritage.org/lw-XTHaYQv2fDPJ9bIpU1Q

• you can already add the mention in section 10 Get involved, or any other section that suits you.

Here is the email notifications received from bouncing email.
This email was received by Elisabetta when sending an email from Elisabetta.mori@softwareheritage.org to morane@softwareheritage.org:

https://github.com/clg55/Scilab-Workbench

What are the drawbacks of Wikidata?

To validate with management and team

Draft TOC is available here: https://hedgedoc.softwareheritage.org/user-documentation-draft

It works! Good job. thanks

Good job! thanks.

To me the advantages are strong ,especially point 1 and 4.

We have different errors at the moment:
When depositing a zip.:

SWORD SWH response: rejected- failed validating with Xsd11Group(model='all', occurs=[1, 1]): Reason: Unexpected child with tag 'swh:create-origin' at position 1. Schema: ... ... Instance: https://inria.halpreprod.archives-ouvertes.fr/hal-02527986 Path: /{https://www.softwareheritage.org/schema/2018/deposit}deposit (swh:deposit) https://deposit.staging.swh.network/1/hal-preprod/1066/status/

Here is the list of keycloack roles:
https://forge.softwareheritage.org/source/puppet-swh-site/browse/production/data/common/common.yaml$3398-3410

Should be in the new version, but the uri field is empty.
To debug ASAP

Thank for the implementation and deployment of the deposit admin view!
Here are new comments for this new version:

• name of metadata column and mention of metadata on each button is a bit redundant:
  • keep metadata column name or put the icons in the deposit-id column
  • place a info icon or other icon on each button
• show the uri of the metadata provenance, it isn't shown at the moment- field empty (even if it sent with metadata-provenance)
• show metadata in metadata box (currently it is empty)

Nice to know that this is almost done!!
Thank you @vlorentz for the diff. Also thank you @anlambert and @ardumont for the review.
Looking forward to test this.

3. When getting the wrong SWHID (an in production SWHID which is not on staging) it will show as "SWORD SWH response: Bad request "

In moderation on HAL:

1. On HAL preprod when moderating it is impossible to change the SWHID on both:
   • the moderation view
   • the edit view
2. The error from SWH is impossible to understand and shown on the moderator's interface

Since there is no blog-post about the end of the project on the FAIRsFAIR website, I don't think we need to add one on our side.
But we should add in the "Hall of fame" part of this page the FAIRsFAIR project:
https://www.softwareheritage.org/support/partners/