Use Case: represent a portal of RO-Crates

[dgarijo]

As a content RO-Crate provider, I would like to set up a portal/landing page for my ROs in a machine-readable manner.

If I want to expose a landing page with only a few ROs without using existing registries, but still make the landing page machine-readable, it would be great to provide a mechanism/suggestion for doing it so. For example, implementing a DCAT approach, or which properties of schema.org should we use (since RO-Crates are sdo:Datasets).

[dgarijo]

Note: this may be out of the scope of the RO definition, feel free to relocate the issue if appropriate

[stain]

Related API standards for iteration of (changed) resources:

SWORD, OAI-PMH, TRS

[stain]

@marc-portier had some ideas on this as well as @ptsefton have done listing of RO-Crates

[ptsefton]

I implemented a very simple approach to this in ro-crate-html-js -- there's a script included with that, meta-crate, to list a series of crates in an index-crate with hasPart relationships (and generate HTML).

https://github.com/UTS-eResearch/ro-crate-html-js

[stain]

Peter has tool for iterating RO-Crates in a folder and then makes an outer collection crate that embeds parts of their metadata (?)