Is the diagram in the link below the answer to this task?
https://docs.softwareheritage.org/devel/architecture.html

This list of user stories is something that can be written in a wiki.
@douardda or do you prefer having this list of scenarios in the docs ( for example in: docs.softwareheritage.org/user-stories)

Also we decided (on today's call) to keep diagrams with mermaid.

This is the blueprint page for all use-cases:
https://docs.softwareheritage.org/devel/swh-deposit/specs/blueprint.html

Reviewed and opened the HAL issue (which is on a closed forge, so most of you can't open):
https://gitlab.ccsd.cnrs.fr/ccsd/hal/-/issues/302

Redirection should be to https://docs.softwareheritage.org/devel/swh-model/persistent-identifiers.html

@ardumont it is exactly the diagram I was looking for. Thanks!
I think we need a diagram that shows the functionality dependence between modules.

The access to the glossary from the main docs page is hard find.
It's under Indices and tables which is not exactly the evident as a glossary related category.
Also there is no access from the left menu.

Here is the document on which we based this summary

Also, I'm searching for a page or image that shows the relations between modules.

I've sent an email (@ardumont in CC) to Bruno and Yannick about this error and about T2611.

id  |        reception_date         | complete_date | external_id  | swh_id | status  | client_id | collection_id | parent_id | status_detail | swh_id_context | check_task_id | load_task_id
-----+-------------------------------+---------------+--------------+--------+---------+-----------+---------------+-----------+---------------+----------------+---------------+--------------
 902 | 2020-09-17 13:16:42.70178+00  |               | hal-02942052 |        | partial |         2 |             1 |           |               |                |               |
 903 | 2020-09-17 14:17:59.276928+00 |               | hal-02942052 |        | partial |         2 |             1 |           |               |                |               |

Which means the deposit is not completed before the Application error.

I have tested today at 11.20 with the same error on HAL's platform.
@ardumont : can you check what the logs say about that?
I think it's about the client credentials, they use the HAL prod credentials and they are listed as HAL preprod client.

The idea was to update the information about the slug on the documentation we give to clients :

1. https://docs.softwareheritage.org/devel/swh-deposit/getting-started.html#single-deposit
2. https://docs.softwareheritage.org/devel/swh-deposit/spec-api.html#create-deposit

I think we can resolve this task as we agreed on staying with the xml format for the metadata-only deposit.

@vlorentz can I assign you this task, as you are working on specs and docs?
it's only about adding information on the new SWHID qualifiers.

Great ! thanks for tackling this !

Adding this link to the case study:
https://docs.google.com/document/d/1EZIBvENaY-atx9PvoOKUb9setQTERV2rmLvpMrJd2e0/edit?usp=sharing

I prefer A2 as well.

I see we have three-four options:

@vlorentz can you please review the naming and the choice of the tag with or without the attribute (e.g id, url)?

In T2312#47921, @moranegg wrote:

After this morning's meeting with @vlorentz and @ardumont:
We will keep the metadata-only deposit specs with the idea of a separate namespace swh for which we need to write the schema (not sure we have that).

This way, the xml with metadata has a section where the identified artifact is mentioned:

Reference a snapshot, revision or release:

With ${type} in {snp (snapshot), rev (revision), rel (release) }:
<swh:deposit>
  <swh:reference>
    <swh:object id="swh:1:${type}:aaaaaaaaaaaaaa..."/>
  </swh:reference>
</swh:deposit>

We need to add to the list of types: directory and content

The possibility to deposit metadata on an origin should be implemented as well, but is not suited for institutional repositories (e.g HAL).
Reference an origin:

<swh:deposit>
  <swh:reference>
    <swh:origin url="https://github.com/user/repo"/>
  </swh:reference>
</swh:deposit>

This specs fits the POST of a new deposit in SWORD and is described in the SWORD v2 documentation (6.3.3. Creating a Resource with an Atom Entry)