Feedback and discussion to bug and enhancement by Taina’s test, #72
Agenda
Alex still not finished, finished fix for the bugs (Taina’s issue). - Alex almost finished. → DEADLINE = 16th of September (Alex will finish everything that is open - nothing else will be addressed).
Alex will send email to Taina and Darren, for them to do 1 test again - give soon feedback
Release of CMV to CESSDA SPs for testing
The invitation text can be finalized as soon we have url of staging environment with the released version, see #74. @Kerrin Borschewski will send out emails. @Alexander Mühlbauer will be used as a contact email for SPs. → Kerrin write email to Matthew etc. and ask if they are working on it or if they need further information
open issue: Report from Darren about DDI collaboration
Information from Darren: (→ Profile almost ready - small issues to check with us before published)
The “minor issues” I’d like to go on the agenda for Wednesday 9th are:
https://github.com/cessda/cessda.cmv/issues/57
Can CDC handle e.g. en-GB or sl-SL? (→ MDO and EQB had a TelCo on the question of “which ISO code to use for language metadata”. The decision is: Use ISO639-3 as a language code. And where EQB needs it, there will be a combination of language and country code for certain elements requested.”. but this is not a CDC-requirement) → ISO639-3 in the profiles cannot be used) → decision: stick to ISO639-1.
Also, check logic of MandatoryIfParentPresentNodeConstraint constraint implementation (see /codeBook/stdyDscr/stdyInfo/sumDscr/collDate/@date for use case)
Final confirmation that the following are correct:
@Alexander Mühlbauer discusses feature #61 with cdc developers, e.g. John - (Recognize DDI in OAI-PMH and extract it) → Alex sent email, hasn’t received an answer yet.
Action Items
see above
Kerrin write email to Matthew etc. and ask if they are working on it or if they need further information
Alex will send email to Taina and Darren, for them to do 1 test again - give soon feedback (Alex will mention in mail which endpoint to use - at the moment, only DDI2.5 XMLs are possible to check)
Original report on BitBucket by Kerrin Borschewski.
Participants
@Kerrin Borschewski; @Taina Jääskeläinen; @Jeannine Beeken; @Alexander Mühlbauer; @Darren Bell @Wolfgang Zenk-Möltgen
Agenda 2.9.2020 – leftovers from this meeting??
Implementation of open issues CMV Tool
Agenda
Alex still not finished, finished fix for the bugs (Taina’s issue). - Alex almost finished. → DEADLINE = 16th of September (Alex will finish everything that is open - nothing else will be addressed).
Alex will send email to Taina and Darren, for them to do 1 test again - give soon feedback
Release of CMV to CESSDA SPs for testing
open issue: Report from Darren about DDI collaboration
Information from Darren: (→ Profile almost ready - small issues to check with us before published)
“Everyone – I have now published v0.4 of the CDC 2.5 Profile and v0.2 of the CDC 1.2.2. Profile.
These incorporate issues 45;46;47;48;49;50;51;52;53;54;55;56;58 from https://github.com/cessda/cessda.cmvissues
Additionally, I have inserted (where relevant) the MandatoryIfParentPresentNodeConstraint.
On Wednesday, if we can resolve a few minor issues, then we can publish v1.0 of both profiles and commnunciate the following through BaseCamp:
https://drive.google.com/file/d/1FrfFVZb0_cv9Uazs9WfcGqe3leUeCGf_/view?usp=sharing
and I can also start work on the 3.2 CDC Profile.
The “minor issues” I’d like to go on the agenda for Wednesday 9th are:
https://github.com/cessda/cessda.cmv/issues/57
Can CDC handle e.g. en-GB or sl-SL? (→ MDO and EQB had a TelCo on the question of “which ISO code to use for language metadata”. The decision is: Use ISO639-3 as a language code. And where EQB needs it, there will be a combination of language and country code for certain elements requested.”. but this is not a CDC-requirement) → ISO639-3 in the profiles cannot be used) → decision: stick to ISO639-1.
@agency should be one of https://vocabularies.cessda.eu/#!detail/CessdaPersistentIdentifierTypes i.e. ARK or DOI or Handle or URN. Optional or mandatory? - in CDC studynumber is mandatory. AGENCY-attribute needs to be mandatory
<![CDATA[ </cmv:Constraints>]]>
/codeBook/stdyDscr/stdyInfo/sumDscr/anlyUnit/concept/@vocab defaultValue="DDI Analysis Unit" fixedValue="true
/codeBook/stdyDscr/method/dataColl/timeMeth/concept/@vocab defaultValue="DDI Time Method" fixedValue="true"
/codeBook/stdyDscr/method/dataColl/sampProc/concept/@vocab defaultValue="DDI Sampling Procedure" fixedValue="true"
codeBook/stdyDscr/method/dataColl/collMode/concept/@vocab defaultValue="DDI Mode of Collection" fixedValue="true"
Best wishes, Darren”
Darren to update profile to use “http”-example (https://bitbucket-assetroot.s3.amazonaws.com/cessda/cessda.cmv/1589967636.15/27/Alex_example_CV_27_ver2_good-case.xml?AWSAccessKeyId=AKIA6KOSE3BNJRRFUUX6&Expires=1599657176&Signature=qtr20Ts3LudgfA6Bnaf8P7H5l%2BY%3D)
Action Items
Darren to update profile to use “https”-example (https://bitbucket-assetroot.s3.amazonaws.com/cessda/cessda.cmv/1589967636.15/27/Alex_example_CV_27_ver2_good-case.xml?AWSAccessKeyId=AKIA6KOSE3BNJRRFUUX6&Expires=1599657176&Signature=qtr20Ts3LudgfA6Bnaf8P7H5l%2BY%3D) - stick to the URLs at the moment. Taina will talk for future reference to Sigit about language specific URNs