This is already well beyond a prototype, so I'm closing this task.

As the "prototype" part of the vault is definitely over, I'm closing this task.

We can always allow people to truncate the identifier to some arbitrary (shorter) length. The canonical URI would be the full identifier, but our URI resolver can recognize shortened identifiers and point to a disambiguation page with all the objects whose identifier starts with the given string.

I agree with all the suggestions: the full id should definitely contain all
this information.
Nevertheless, the sheer length of the result *may* turn out to be a blocker
for adoption as a reference to software in the academic publishing
framework. We can propose this, and see if we need to also provide a
shorter backup if really there is a strong negative feedback.

I'm not opposed to having explicit hash scheme names in the IDs—it is a good idea, only to be weighed against the cost in terms of length.
But we should also have schema version numbers, in case more radical changes will be needed in the future, e.g., renaming the object types in the graph.
If we retain both suggestions, that would give:

• swh:1:revision:sha1_git:<git sha1 of a revision>
• swh:1:content:blake2s256:<blake2s256 of a content>

I've been thinking about this in relation to T836.

we're taking a different route for this now, based on @grouss WIP

I don't know if I should finish cleaning up slow_loader for code review, since the hglib interface is so slow as to be next to useless.

done (by @olasd last week)

We now have a "full" content mirror on azure (the data for each 16th bucket is up to date as of the time the snapshot was taken).

systemd-journal-remote has been configured to receive logs on pergamon; systemd-journal-upload has been configured on all machines to push the journal messages to pergamon.

this has been done by @olasd a while ago, as part of the work described at https://www.softwareheritage.org/2016/11/09/listing-47-million-repositories-refactoring-our-github-lister/

this is a duplicate of T120

We now have a (empty) Diffusion repo for this: https://forge.softwareheritage.org/source/swh-loader-mercurial/

*drum roll*
*tsssss*

Remains to update the azure workers with the latest indexer.
I'm on it.

Done as of T585.

Sum up and status:

• Use of fossology's nomossa (nomos standalone version)
• DB schema updated (swh-storage)
• Api endpoints opened to add/read nomos's output (swh-storage)
• New Indexer added (swh-indexer)
• Puppet manifest for that indexer (swh-profile, swh-site)
• Deploy DB upgrade (uffizi)
• Deploy swh-storage upgrade (uffizi)
• Deploy indexer on azure nodes
• Feed existing contents stored in azure to keep up with other indexers
• Update missing licenses in storage
• Feed failed contents (the ones that were tagged, license unknown) back in

Updated previous comment. It's ok.

Current analysis' details in P120