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

List of elements from DDI-L 3.3 to be mapped to data model of aggregator #686

Open
MortenSikt opened this issue Nov 21, 2024 · 0 comments
Open
Assignees

Comments

@MortenSikt
Copy link

Baseline is elements defined in the CDC DDI 3.3 Profile (https://cmv.cessda.eu/profiles/cdc/ddi-3.3/1.0.0/profile.html)

  • /ddi:DDIInstance/s:StudyUnit/r:UserID

  • /ddi:DDIInstance/s:StudyUnit/r:UserID/@typeOfUserID

  • /ddi:DDIInstance/s:StudyUnit/r:Citation/r:Title/r:String

  • /ddi:DDIInstance/s:StudyUnit/r:Citation/r:Title/r:String/@xml:lang

  • /ddi:DDIInstance/s:StudyUnit/r:Citation/r:Creator/r:CreatorReference*

  • /ddi:DDIInstance/s:StudyUnit/r:Citation/r:Creator/r:CreatorReference/r:TypeOfObject

  • /ddi:DDIInstance/s:StudyUnit/r:Citation/r:Publisher/r:PublisherReference*

  • /ddi:DDIInstance/s:StudyUnit/r:Citation/r:Publisher/r:PublisherReference/r:TypeOfObject

  • /ddi:DDIInstance/s:StudyUnit/r:Citation/r:InternationalIdentifier/r:IdentifierContent

  • /ddi:DDIInstance/s:StudyUnit/r:Citation/r:InternationalIdentifier/r:ManagingAgency

  • /ddi:DDIInstance/s:StudyUnit/r:Abstract/r:Content

  • /ddi:DDIInstance/s:StudyUnit/r:Abstract/r:Content/@xml:lang

  • /ddi:DDIInstance/s:StudyUnit/r:Coverage/r:TopicalCoverage/r:Subject**

  • /ddi:DDIInstance/s:StudyUnit/r:Coverage/r:TopicalCoverage/r:Subject/@xml:lang

  • /ddi:DDIInstance/s:StudyUnit/r:Coverage/r:TopicalCoverage/r:Subject/@controlledVocabularyName

  • /ddi:DDIInstance/s:StudyUnit/r:Coverage/r:TopicalCoverage/r:Subject/@controlledVocabularyURN

  • /ddi:DDIInstance/s:StudyUnit/r:Coverage/r:SpatialCoverage/r:Description/r:Content

  • /ddi:DDIInstance/s:StudyUnit/r:Coverage/r:SpatialCoverage/r:Description/r:Content/@xml:lang

  • /ddi:DDIInstance/s:StudyUnit/r:Coverage/r:SpatialCoverage/r:CountryCode

  • /ddi:DDIInstance/s:StudyUnit/r:AnalysisUnit**

  • /ddi:DDIInstance/s:StudyUnit/r:AnalysisUnit/@controlledVocabularyName

  • /ddi:DDIInstance/s:StudyUnit/r:AnalysisUnit/@controlledVocabularyListURN

  • /ddi:DDIInstance/s:StudyUnit/d:DataCollection/d:Methodology/d:TimeMethod/d:TypeOfTimeMethod**

  • /ddi:DDIInstance/s:StudyUnit/d:DataCollection/d:Methodology/d:TimeMethod/d:TypeOfTimeMethod/@controlledVocabularyName

  • /ddi:DDIInstance/s:StudyUnit/d:DataCollection/d:Methodology/d:TimeMethod/d:TypeOfTimeMethod/@controlledVocabularyURN

  • /ddi:DDIInstance/s:StudyUnit/d:DataCollection/d:Methodology/d:SamplingProcedure/d:TypeOfSamplingProcedure**

  • /ddi:DDIInstance/s:StudyUnit/d:DataCollection/d:Methodology/d:SamplingProcedure/d:TypeOfSamplingProcedure/@controlledVocabularyName

  • /ddi:DDIInstance/s:StudyUnit/d:DataCollection/d:Methodology/d:SamplingProcedure/d:TypeOfSamplingProcedure/@controlledVocabularyURN

  • /ddi:DDIInstance/s:StudyUnit/d:DataCollection/d:CollectionEvent/d:ModeofCollection/d:TypeOfModeOfCollection**

  • /ddi:DDIInstance/s:StudyUnit/d:DataCollection/d:CollectionEvent/d:ModeofCollection/d:TypeOfModeOfCollection@controlledVocabularyName

  • /ddi:DDIInstance/s:StudyUnit/d:DataCollection/d:CollectionEvent/d:ModeofCollection/d:TypeOfModeOfCollection@controlledVocabularyURN

  • /ddi:DDIInstance/s:StudyUnit/a:Archive/a:ArchiveSpecific/a:Item/a:Access/a:TypeOfAccess

  • /ddi:DDIInstance/s:StudyUnit/a:Archive/a:ArchiveSpecific/a:Item/a:Access/a:TypeOfAccess/@controlledVocabularyName

  • /ddi:DDIInstance/s:StudyUnit/a:Archive/a:ArchiveSpecific/a:Item/a:Access/r:Description/r:Content

  • /ddi:DDIInstance/s:StudyUnit/a:Archive/a:ArchiveSpecific/a:Item/a:Access/r:Description/r:Content/@xml:lang

*Note that for Creator and Publisher, the profile seems abit odd. I do assume that it is Creator/PublisherName that is of interest here, it is caputered within reference by resolution of the reference.. Don't know if that makes sense

**(xml:lang), vocabName and vocabURN are included for all CVs. Unsure if they have similar counterpart in DDI-C/Data Model. The important part is to capture the actual code value/descriptive term from DDI-L metadata. So it is not critical that the attributes are matched

The main difference I can see between the 3.3 profile and the 3.2 profile is the xpaths/expression of references to CVs, there is different name usage. Additionally 3.2 does not support CV for TypeOfAccess, this is through a freetext field, and @context attribute is used for indicating that content is code value.

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

No branches or pull requests

2 participants