Move TEI (and derivative) data to public repo

digicademy / svsal

The School of Salamanca. Web Application

MIT License

16 stars 7 forks source link

Move TEI (and derivative) data to public repo #27

Open awagner-mainz opened 5 years ago

awagner-mainz commented 5 years ago

... (either gitlab or github)

[ ] A webhook could trigger the webapp pulling new TEI sources from the repo when they are pushed from editing workflow.
[x] This could at some point in the future imply pushing prerendered data formats (see below) to the repo on rendering them (thereby also enabling #14 ).

Data to store:

[ ] TEI/XML (SvSal ~~and Simple~~)
[x] ~~Plaintext files~~
[x] ~~RDF (XML, TTL, JSON-LD)~~
[x] ~~iiif Manifests~~
[x] ~~METS files~~
[x] ~~pdf and ebook files~~

And I suggest we store only data for full works (and volumes), not passages.

dvglc commented 5 years ago

This is closely related to a different (and not yet solved or even documented) issue: how to cite the research data as a whole, or particular works. Do we cite them using a version number? If so, do we use the version number of the research data package, the version number of a particular TEI dataset (even if citing the HTML version, for example)? When is the version number updated: when updating the TEI, or when all webhooks have completed? (If we use dates, similar questions may arise.)

dvglc commented 4 years ago

I think this issue/ticket needs much more discussion. For example, webdata derived from the TEI data are still listed as desiderata for public archival, just like the TEI data themselves. But I thought we had (informally) decided to focus on archiving the TEI rather than the webdata? If so, we should remove these items from the "data to store".

awagner-mainz commented 4 years ago

In any case we can split the derivative data out of this issue. How we publish (versions of) derivative data is IMHO indeed something we need to discuss and plan for a longer term only.

I am eliminating them from the list above - and for now I refrain from adding a new ticket, pending discussion in the project.

awagner-mainz commented 4 years ago

I am (more or less, just need to find the time) about to write a github/zenodo integration that parses individual TEI files from a github release, extracts their metadata and ingests them individually to zenodo. Will have to fiddle around with piping zenodo's DOI back into the files, among other things.

But will that be even any help for the webapp? Is it related to this issue?

awagner-mainz commented 4 years ago

Finally, I suggest we upload the TEI files we have published already to individual zenodo records manually for now...