I was basing this on what's on our site: https://tei-c.org/Guidelines/P5/#previous If they don't deserve to be there, I don't know that it's important to archive them in Zenodo. But what does need to be there is the earlier stuff: https://tei-c.org/Vault/Vault-GL.html although since each version is different, that will have to be done manually. Cheers, Martin On 2019-09-21 7:21 p.m., Lou Burnard wrote:
There's not a lot of point in conserving your archival history if you decide that some versions "don't really matter". The 0.* versions are as much a part of the continued evolution of P5 as the "official" releases, whatever that means.
On 21/09/2019 18:07, Martin Holmes wrote:
Hi Peter,
This looks fantastic. Thanks for putting in all the work to figure out the Zenodo API!
I would be inclined to say that version 0.x doesn't really matter. Those were not intended to be official releases, were they?
Cheers, Martin
On 2019-09-21 4:11 p.m., Peter Stadler wrote:
Hi all,
having a long train ride home from Graz I was looking into our TEI Zenodo publications of the Guidelines. Since we decided that we wanted all our published releases to show up at Zenodo and because these are quite a few I decided to write a little script rather than doing those uploads manually. I want to document here what I tested and what I’m about to do so you can stop me if it’s mad or something is missing. (BTW, Zenodo has a sandbox where I was testing my scripts)
#1 I have not found a way to directly upload to Zenodo from an URL so first I needed to download all the zip archives from Sourceforge (GitHub only has releases from 2.9.0 onwards) to my local machine #2 I wanted to use the HTML readme files we already have to use them as zenodo description (find them at https://www.tei-c.org/Vault/P5/current/doc/tei-p5-doc/) but needed to get rid of the HTML header etc. I was doing this with XSLT, see https://gist.github.com/peterstadler/a33df4f7cb3f1234c8f15d73a080a192 #3 needed to rename some of the readme files to get proper three digit version numbers #4 create a python script for adding our releases to zenodo, see https://gist.github.com/peterstadler/79d402bb989c8a066b482381979557a3
The whole process works quite nicely but will need some manual tweaking (of e.g. dates) afterwards (once I move from the sandbox to the real system). Because I will need to call the zenodo support after the ingestion to fix the sort order, I want to be sure that I have everything. NB: all the metadata can be changed afterwards but the files may not be touched anymore. Every new upload than creates a new version which will show up as the latest(!) So here are some questions:
a) At Sourceforge there is a release 0.9 while in the readme there is a 0.6 (but not vice versa). Is this just a typo somewhere and do these releases belong together?! b) There is some gap between 0.6 and 0.9 (or 1.0) and before 0.2.1. Does anyone have more releases anywhere? c) release notes are missing for 0.2.1 and 1.4.1
Many thanks for reading until the end Best Peter
_______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
_______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
_______________________________________________ Tei-council mailing list Tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council