Just a question about using a path with a different branch, for example for a tag of a version (which is not a release):

• in this case, the anchor is the snp and the branch name (the tag) is in the path?

Here is the link to the open issue on the CodeMeta repository:
https://github.com/codemeta/codemeta/issues/240

A few suggestion for the repository view:

1. I like the divided tabs, but in each tab, the context should be kept
2. In source code tab : context of the source code (SSC)
   • opencv\opencv\[dir-id] with snapshot date and branch
   • Also readme should be kept in the SSC tab
3. About metadata:
   • there is metadata in revision
   • there is deposited metadata for origin in the origin_metadata table
   • there is indexed metadata for origin
   • there will be metadata that can be associated to each artifact
   • A metadata tab is nice but will be very difficult to understand to which part of the repository the metadata is relevant,
     • show metadata as a separate button, as proposed in the task, is a temporary solution
     • we should reflect on this with the upcoming metadata additions (most registries, show metadata on the right, with several metadata functionalities, see Zenodo, HAL or SwMath)

seems so from the design ;-)

try again button, will it appear only for failed requests ?

The behavior of the page:
I enter the link to the repository
click submit (which I suggest to change to save)
and there is a green box appearing below the form.

I think the reference here should be the vault page

From the design, there is also a change of colors on the visits page.

Great UX proposal not to interrupt the browsing with the download page.

Will you change Visit type into Origin type?
the former is more accurate, the latter is more comprehensible by someone that is not familiar with the data model.

I agree that a search box is a great way to keep the user engaged.
The text in the search box can be leading, here in the example we have Enter keyword, but the result is a search on the url, right?
If the search is the actual search on url:
Enter url
Enter repository
Search the archive

In the sidebar menu I would keep the API access (unless it is accessible during the navigation - not on the landing page).
Also the access to the API on the side, is very small.

I've seen the new example, is this the right transformation?

If you agree with this proposal with @vlorentz's example, I can submit the issue tomorrow.

Great news !!

I just discovered that there is a pending term maintaineron schema.org, thanks @vlorentz
for pointing this out.
https://schema.org/maintainer

@vlorentz can we say that your new validator resolves this?

Here is the first draft:
https://www.softwareheritage.org/?p=21219&preview=true

Available here:
https://codemeta.github.io/codemeta-generator/

Thanks @olasd for the accurate and detailed summary !

Thanks @anlambert ! That's great news !!

After discussion with @rdicosmo, GitHub is the best place for the community that wants to use the CodeMeta Generator.

I actually don't have it in both cases.
I'm firefox quantum 68.2

Complete email:

example: https://archive.softwareheritage.org/swh:1:cnt:a6463d2ce390990c31c2f2fa8019606721f0ca13;origin=http://git.savannah.gnu.org/git/gnugo.git/

Thanks @anlambert for the detailed explanation.
This is exactly right !

Hi @sdruskat,
Thanks for your input.
I agree with you that for the end user this looks like a problem.
On the other hand, we are an infrastructure that needs to consider many platforms for the long term, so we can't pick and choose whatever feels more comfortable for the user.

@vlorentz I'm not sure it is an easy hack, could you review the task and decide?

@anlambert: Can you also update this page as well- https://docs.softwareheritage.org/devel/swh-model/persistent-identifiers.html
Adding the first item (hal-02446202) to the references?

publiccode.yml : https://docs.italia.it/italia/developers-italia/publiccodeyml-en/en/master/index.html

@anlambert thanks!
I'll do the translation so I'm claiming the task.

@anlambert: great. Thanks !