-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sorting out reserved and open URIs for persons, places, works, etc. #950
Comments
Okay, so I've begun working on this. I have a script that outputs the URIs, and some related info, for all the records that are currently on a given branch (including deprecated records, which I mark as such). The results of this for "master", "dev", and "new-places-from-Syriac-World" are here. The good news is that all persons, places, and works that are on dev have a record on master. Syriac World places have not been pulled in, but see #873 which should be ready to go. I think the next steps for tracking down potentially missing TEI records are as follows:
So far I have left of taxonomy and bibl records from this report (and SPEAR since the URIs work differently). We may want to circle back and check on these at some point as well. |
@dlschwartz now that we have the csv transform working for persons and places (and I may make the works module since @jsaintlauren and I are hoping to add some new hagiography records this spring, and we are getting ready to start tagging entities in the mss catalogue, some of which might need newly minted URIs), I was thinking we should make sure we've tracked down all the URIs or csv data that have not yet been converted and added as TEI to the app.
I know we had #865 as a discussion of places, which I need to follow up on.
I have no idea what the situation with persons or works is...I think I will proceed as follows and we can confer with @davidamichelson @jsaintlauren and @nathangibson on other places to look for these data.
That's everything I can think of for right now. It might then be useful to formalize and centralize an intra-Syriaca method of reserving URIs and creating new records (e.g. a shared Google sheet that has URI lists for all entity types). As we discussed, the csv transform should ideally cut down on any wait time between URI reservation, record creation, and publishing on the server, but it would still be useful to have a centralized way of tracking that process.
The text was updated successfully, but these errors were encountered: