An interesting diagram that can fit the mirror documentation: https://www.programmevitam.fr/pages/VaS/

Accepting cause the comment is only to improve the docstring

This is a very nice idea to try and mock less things with tests.

I elevated the priority of this task because I have done a demo yesterday and it would be better to have the chosen icon in a top menu

Pointing to an archived copy of the source code repository isn't the same as the archived copy of the repository.
SWH archive url -> well formatted for acceptance

This task will take us one step towards a searchable archive :-)

Thank you @vlorentz for this important script that will take us one step towards a searchable archive :-)

Oh je-suis-GPL isn't a real test, di we really loose the xml for that?

I think that all are also tests, but I need the external_id column to be sure

All deposits here are tests you can even delete them completely from the archive

I need a more clear distinction when data and metadata are used..
data and atom are not compatible things... atom is always metadata.
data should always refer to the software source code content.

I'm uncertain about which scenario is tested.

I agree on linking Gitorious to the wiki page, but we should find a consistency that can generate automatically the coverage page.

Thanks for checking !

I'm not sure about my comment to change tool to fetcher.

@anlambert What do you think?

That's a good start !
I have some comments in-lined.
Maybe a clear plan for test and coverage, can be useful and help you continue the development.

A reference to AtomPub protocol which is used with SWORD:
https://www.ibm.com/developerworks/library/x-atompp1/x-atompp1-pdf.pdf

Prod
This was due to corrupted file. The error was difficult to understand and wasn't logged on the moderation view (on HAL side).
This task is now closed.

Examples for a community driven documentation:

• https://docs.godotengine.org/en/stable/
• https://javascript.info/
• https://wiki.archlinux.org/