Skip to content
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

2022 10 27 object exempla wlpotter #60

Open
wants to merge 7 commits into
base: master
Choose a base branch
from

Conversation

wlpotter
Copy link
Collaborator

Here are a few 'real data' exemplar files based on the work done on Sinai Arabic 320. I've created the ms object, codicological unit, and two textual artifacts for that manuscript. I've also included a work and person authority record with 'real' data from airtable and other authority file sources.

These records are using the template based on #59, FYI.

I will go through and make a few notations, but we can discuss further whenever we get a chance @kirschbombe

"iiif_manifest": "https://iiif.library.ucla.edu/ark%3A%2F99999%2Fz18s67k3/manifest",
"text_direction": "right-to-left",
"viewing_hint": "paged",
"thumnail_url": "https://iiif.sinaimanuscripts.library.ucla.edu/iiif/2/ark%3A%2F99999%2Fz18s67k3%2F76301r6v/full/!200,200/0/default.jpg"
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

haha oops...typo on the field name -- that's what I get for not copying and pasting from the template...

"note": null,
"features": null
},
"events": [
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

here is an example of what a production event could look like. I've retained its id and, like with paratexts, used the object's ARK as a sub-namespace. Note that the sources field references the ARK for this record's colophon

@@ -0,0 +1,94 @@
{
"id": "ark:/99999/z18s67k3",
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Between the first sample data and this one I learned more about ARKs 😆 So this uses the DLP's shoulder but the naming authority's name space is the one reserved for testing, so as not to confuse this with actual data

"note": [
"Colophon on 194v-195r. Scribe's name followed by two separate blessing, which include formulas about the scribe’s unworthiness and humility before God on (f. 195r)"
],
"attested_entities": {
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shoot this should instead be directly nested "attested_person" and "attested_place" fields...

"Colophon on 194v-195r. Scribe's name followed by two separate blessing, which include formulas about the scribe’s unworthiness and humility before God on (f. 195r)"
],
"attested_entities": {
"attested_person": [
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should the CMS somehow also populate the associated person field from attested persons? I don't want to reduplicate, but it would be a pain to have to search in all these different fields to find related entities...

"note": null
}
],
"bibliography": [
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

probably these two encyclopedia entries belong with the work authority?

"related_objects": {
"contained_in": [
{
"type": "primary_text_of",
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

here is the example of the top-level and more specific relationship types

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants