ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
LevelDB field nameTypeDescriptionExamplesNotes from meetingSuggested termPT SuggestionsAuthorityExampleImplementedPT Notesresolvedadd to modefile
2
collection/itemaccess_narative1:1Who should have accessThe material is still being worked on and will be open access upon publication of the dissertation "A Grammar of Bulu Puroik". Projected date of publication is early 2018.LDaCA would consider this a license{
"license": "Closed",
"licenseConditions": [
"Contact PARADISEC",
]
}		https://schema.org/license{
"license": {"@id": "LICENSE.txt"},
"usageinfo": "Contact PARADISEC to request access"
} Move the narrative to a document called LICENSE.txt (or whatever)		xSee the profile - this says to use the license prop pointing to document, and also see usageInfo where you could put free-text stuff about how to access
3
collection/itemcomments/admin_comment1:1General CommentsAudio resampled with Adobe AuditionFind something from schema.orgcommenthttps://schema.org/comment{"comment": "some comment"}xyes1
4
collectionmedia1:1Description of the original mediaAudio cassette tapes; Participant questionnaires; FieldnotesMediaObjectdescription (on File) or material for https://schema.org/MediaObject{
"@id":"somefile.wav",
"material": "Cassette Tape"

{
"@id":"somefile1.wav",
"description": "Fieldnotes"}		xMediaObject is a class not a property and it's already used in RO-Crate aliased via the context to File. Looks like you have this property at the Object level but it would be more flexible if applied to each File so you can talk about media with more precision. (The examples you give here are quite different1
5
collectionmetadata_source1:1Where the metadata came fromdepositor and tape boxesMediaObjecthttps://schema.org/MediaObjectTODOxDidn't you have something like this Nyingarn
6
collectionorthographic_notes1:1Notes on the orthography used in the metadata. The writing conventions that need to be understood to read the metadata.Contains some unicode characters in line with IPA symbols, such as tlda underneath for creaky voice, and bar-i for high-mid vowel.<mods:note type="orthographicNotes">Uses British English spelling conventions.</mods:note>Yep - lets import that term into LDAC termshttps://www.loc.gov/standards/mods/mods-notes.html"orthographicNotes": "blah"xhttps://github.com/Language-Research-Technology/language-data-commons-vocabs/issues/291
7
collectiontape_location1:1Where the tapes are storedDepositor arranged digitisation privately and sent WAV files.Maybe use holding_archive similar to NyingarnitemLocationhttps://schema.org/itemLocationitemLocation": "Paradiec office"xyes1
8
collectionfield_of_research1:1ANZSRC fields of researchLiterature in Japanese<controlaccess>
<subject source="ANZSRC">0806 Information Systems</subject>
</controlaccess>		about -> DefinedTermhttps://www.loc.gov/ead/tglib/elements/controlaccess.html {"@id": "...",
"about": {"@id": "https://linked.data.gov.au/def/anzsrc-for/2020/450108"}
}

{
"@id": "https://linked.data.gov.au/def/anzsrc-for/2020/450108"
"@type": "DefinedTerm",
"name": "Aboriginal and Torres Strait Islander linguistics and languages"
}		xWe could ask for help from the vocabs people at ARDC on thisyes
9
collection/itemoperator1:1Operates the collection, person responsible for digitisingthe itemJohn FerlitoAdd a paradisec contextagentAdd Operator to LDAC terms?? (I'm not really clear on the meaning of this one)https://schema.org/agent"operator": {"@id", "https://orcid.org/asdas"}xAgent is a appropriate if you use CreateAction (or the other Action classes). IF you want a single property to capture "Operates the collection, person responsible for digitisingthe item" then that's trickier these are two different things.
10
collection/itemuniversity1:1The associated universityUniversity of Sydneyaffiliation
{
"@context": "http://schema.org",
"@type": "Person",
"name": "John Doe",
"affiliation": {
"@type": "Organization",
"name": "University of Example"
}
}
https://schema.org/sourceOrganization
{
"@context": "http://schema.org",
"@type": "Person",
"name": "John Doe",
"affiliation": {"@id": "https://ror.org/03f0f6041"}
},
{
"@id": "https://ror.org/03f0f6041",
"@type": "Organisation",
"identifier": "https://ror.org/03f0f6041",
"name": "University of Technology Sydney"
},
xThe example here shows affiliation on a person which is standard usage but are you sayingn that this is an OBJECT level property in PARADISEC??(will need this when we do a Object level mode
11
collectiongrants1:manyGrants related to the collectionCE140100041Add a paradisec contextfunderhttps://schema.org/funder{
"@context": "http://schema.org",
"@type": "CreativeWork",
"name": "Research Project",
"funder": {
"@type": "Organization",
"name": "XYZ Foundation",
"identifier": "ABC123"
}
}
{
"@id": "https://doi.org/10.5281/zenodo.1009240",
"@type": "Dataset",
"funder": {
"@id": "https://ror.org/038sjwq14"
},
},
{
"@id": "https://eresearch.uts.edu.au/projects/provisioner",
"@type": "Organization",
"description": "The University of Technology Sydney Provisioner project is ...",
"funder": [
{
"@id": "https://ror.org/03f0f6041"
},
{
"@id": "https://ands.org.au"
}
],
"identifier": "https://eresearch.uts.edu.au/projects/provisioner",
"name": "Provisioner"
},
{
"@id": "https://ror.org/03f0f6041",
"@type": "Organisation",
"identifier": "https://ror.org/03f0f6041",
"name": "University of Technology Sydney"
},
{
"@id": "https://ands.org.au",
"@type": "Organization",
"description": "The core purpose of the Australian National Data Service (ANDS) is ...",
"identifier": "https://ands.org.au",
"name": "Australian National Data Service"
},		xThis is covered in the RO-Crate spec: https://www.researchobject.org/ro-crate/specification/1.1/contextual-entities.html#funding-and-grants
12
collectioncollection_admins1:manyUsers with admin rights to the collectionJohn Ferlito, Nick Wardprovenance stuff maybe? or paradisec contextdata manager
https://schema.org/accountablePerson (or use something internal)
{ "paradisec:admins": id }xI don't think this is a very good way to do this, adding people to a collection like this. In the LDaCA model we would use a license for this and separate out license management. (but to be fair we have not even built this so why would you listen to me)

DO NOT use roleName like this - if a person has multiple roles in the crate which is very common then once you flatten the graph you can't tell the difference between all the roles. This is why using Provenance (Actions) is much more flexible and precise.
13
itemdialect1:1The dialect (not the language which is captured elsewhere with standard terms)Gun-nartpa, An-barradialect
Use language code if known
{
"@context": "http://schema.org",
"@type": "CreativeWork",
"name": "Sample Document",
"inLanguage": {
"@id": "#southamericanenglish"
},
{
""@id": "#southamericanenglish",
@type": "Language",
"name": "Southern American English",
"specializationOf": {"@id": "https://glottolog.org/resource/languoid/id/stan1293''}
},
{"@id": "https://glottolog.org/resource/languoid/id/stan1293'',
"name": "English",
"@type": "Language"}		xNick and John say: None of the schemas has an appropriate encoding, typically using a descriptive field, e.g. <mods:note type="language">Dialect: Southern American English</mods:note>
</mods:language>

PT says :we probably need to use an entty of type language with a special ID for the dialect -- see example.
14
itemingest_notes1:1Notes on the ingest processUnable to retrieve the whole tape, only the first 40mins of the tape was capturedConsumeActionhttps://schema.org/ConsumeActionx
15
itemoriginated_on_narrative1:1String of when it was generated19 - 11 - 1980 (written on side B)dateCreatedhttps://schema.org/dateCreatedx
16
itemreceived_on1:1When the media was received2022-11-02dateReceivedhttps://schema.org/dateReceivedx
17
itemtracking1:1tracks where the media isDigitised. At PDSC Sydney to be returned- 2018/08/1 <mods:location>
<mods:location> <mods:physicalLocation>XXXX</mods:physicalLocation> </mods:location>
xDidn't we talk about this for NYingarn?
18
itemurl1:1An extra external IRLhttps://research.library.kutztown.edu/sikaianaURLhttps://schema.org/URL
19
itemdiscourse_type1:1Discourse typereport, singingThis exstsdiscourse_typecommunicationModehttp://www.language-archives.org/OLAC/1.1/olac-discourse-type.xsdlanguageGenrexWe've moved all the Olac terms we thought were relevant to the LDAC schema if things are missing we can add them see row 21
20
itemadmins1:manyUsers with admin rights to the itemJohn Ferlitoprovenance stuff maybe? or paradisec context{
"@context": "http://schema.org",
"@type": "DigitalDocument",
"author" ""accountablePerson": {
"@type": "Person",
"name": "Jane Smith",
"role": "administrator"
}
}. 		paradisec:adminsxAlso EAD <controlaccess>
<persname role="administrator">Jane Smith</persname>
</controlaccess>
21
itemdata_categories1:manyData Categorieslexicon, songNot clear how this maps to OLAC, which has lexicon under datatype, but not song ....Linguistic Data Typehttp://www.language-archives.org/REC/type.html#Linguistic%20Data%20TypecommunicationMode: ("@id": "https://w3id.org/ldac/terms#Song"}xThis is covered in our schema -- we do have song - see row 19
22
itemdata_types1:manyData typesCollectionCollectionhttps://www.dublincore.org/specifications/dublin-core/dcmi-terms/dcmitype/Collection/xDon't understand these last two -- are some items collections?
23
itemdata_types1:manyData typesDatasetAdd more to the types field to schema.org typesDatasethttps://www.dublincore.org/specifications/dublin-core/dcmi-terms/dcmitype/Dataset/xI think everythign is a dataset in our model -- what's an example of this?
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100