adding fields for download commands to dataset templates

[cmeesters]

Hi,

It occurred to me, that perhaps dataset nanopub templates (e.g. the simple or the one on summary level and others) can be insufficient.

Why? Usually the URL is sufficient to find data and to download to a desktop PC or portable device. However, sometimes data sizes exceed Zenodo or other portals allowances. In this case, data ideally are archived and published using institutional archiving software. In such a case data (re-)use will occur on servers, cloud instances, HPC systems and will be triggered with curl and similar command line tools.

When, for instance, iRODS dropped its REST API, the new http client API calls for complex curl commands. The URL may not be sufficient to retrieve data in a thread safe manner. Data stewards and researchers need to provide an example call to provide their data to 3rd parties.

Similar cases might exist. Particularly, the development of various institutional solutions will lead to an extremely heterogeneous API field.

So, perhaps these thoughts merit the introduction of optional example command fields in nanopubs describing data sets?

Cheers
Christian

[tkuhn]

Hi Christian,

Sorry for my late reaction. Yes, I see your point. I am not sure it should be that way, but I understand that such more complex commands might be needed.

Do you know of an RDF predicate that could be used for that, from schema.org, DCAT, or similar? Then it would be easy to create a new template with it.

Regards,
Tobias

[cmeesters]

Hoi Tobias,

I'm afraid, no. I am not aware of any solution to this issue and have to confess, that I did not do any research. How do the yoda developers in your vicinity handle this situation?

Is there no way to extend existing nanopub templates? Extending a template does not render existing nanopub invalid, right? (just general curiosity)

Cheers
Christian

[tkuhn]

I am afraid that I don't have any Yoda developers in my vicinity... :)

But we can define a new property if none exists. You can define one, for example, with this nanopublication template: https://nanodash.knowledgepixels.com/publish?template=http://purl.org/np/RA9bHqTRDDookF7TA4Rp4wmYbiunco0kBgUnV1nlSHedc&template-version=latest

We can also give it a nicer URI than the one within the namespace of the nanopub itself. I can show you how.

Right, updating the template or just defining a new one doesn't render anything invalid that already exists.

[cmeesters]

Ah, that would be great - right now, I will not find time before the end of the month.