Allow any proxy-metadata-* parameter and pass them through to the RO-Crate-rendering stylesheet, so the user can add a free text description, their name, orcid, licence, etc, and have that turn up in the RO-Crate metadata object.
One of these parameters will be proxy-metadata-format which will (at first) have just one acceptable value: ro-crate, and which will cause the pipeline to pass the query request itself (rather than the query results) to a stylesheet which will then transform it into an RO-Crate metadata object. Later we could add other transformations to generate other metadata formats such as plain text citations, Zenodo metadata objects, etc.
Potentially one or more of these metadata objects could also get wodged into the TEI corpus document, too, inside elements, controlled by a proxy-metadata-embed parameter.
[x] Set up XProc pipeline to accept proxy-metadata-* parameters and return query metadata.
[x] Write stylesheet to produce a fairly complete RO-Crate metadata object.
[x] Update the QueryBuilderForm front ends to include a UI for these parameters. Maybe a trove-metadata web component?
Allow any
proxy-metadata-*parameter and pass them through to the RO-Crate-rendering stylesheet, so the user can add a free text description, their name, orcid, licence, etc, and have that turn up in the RO-Crate metadata object.One of these parameters will be
proxy-metadata-formatwhich will (at first) have just one acceptable value:ro-crate, and which will cause the pipeline to pass the query request itself (rather than the query results) to a stylesheet which will then transform it into an RO-Crate metadata object. Later we could add other transformations to generate other metadata formats such as plain text citations, Zenodo metadata objects, etc.Potentially one or more of these metadata objects could also get wodged into the TEI corpus document, too, inside elements, controlled by a
proxy-metadata-embedparameter.proxy-metadata-*parameters and return query metadata.trove-metadataweb component?