Closed pdaengeli closed 6 months ago
could you restructure the metadata-ms-page.json? The most performant would be to get separate files per siglum. ie. https://dhbern.github.io/parzival-static-api/api/json/metadata-ms-page/${id}.json
Structure could be the same as in the files that are at the moment in the lib folder: https://github.com/DHBern/presentation_parzival/tree/main/src/lib/metadata-ms-page
Perhaps this is implemented already with the split_output
param.
If I set it to true I get the following output:
d.json
, fr1.json
Would that work? Then I change the default and commit the JSON files.
yes, that's what I need! It's the same files that are used atm Thank you!
Indeed, diffing shows that they are identitcal:
fr1
d
(more complex)I'll commit and push shortly.
Good to go now, e.g. https://dhbern.github.io/parzival-static-api/api/json/metadata-ms-page/fr1.json
How about defining a constant for https://dhbern.github.io/parzival-static-api/api/
and use it in +server.js#L9
and +page.js#L5
?
The following static endpoints are ready for consumption/integration:
Furthermore there is a flat collection of all TEI files available at:
Given the lacking Git control in eXist it would be good to use these files in order to have a single source of truth. Consequently, we should remove these files from the
parzival_data
repo and keep only the ODD file and other TEIPublisher-related stuff there.Any additional needs are best recorded in a new issue at
parzival-static-api
.