Produce technical documentation on Data Models

[richard-jones]

• PR: [when the PR is created, put a link to it here. DO NOT use the "linked PR" feature]
• User Test Scripts: [when there are user test scripts available link them here]

---

Produce documentation showing the data models required, may be derived from the Data Modelling breakout sessions.

Acceptance Criteria

List the criteria which must be met for the issue to be considered complete

• A technical mapping description of the data models required in Invenio

[richard-jones]

@npapantonis @LalithaKambhammettu to note from today that this will feed into work possibly for the Library in providing an Admin Guide for the form

[richard-jones]

Data model docs here https://docs.google.com/spreadsheets/d/106fzB6EiVJmnd3kRmTc1HEkx2h8zTR2S8PFlr-_qMHY/edit

[npapantonis]

HI @peters, ***@***.***>, This is an GitHub Board item re “Produce technical documentation on Data Models” with the acceptance criteria of “A technical mapping description of the data models required in Invenio”. It was noted by CL that this will feed into work possibly for the Library in providing an Admin Guide for the form; and Cottage Labs have appended the following (also attached) for you to review, accept, or update with any feedback Data model docs here https://docs.google.com/spreadsheets/d/106fzB6EiVJmnd3kRmTc1HEkx2h8zTR2S8PFlr-_qMHY/edit Please can you review this and let us know if you have any comments or if this ticket can be closed off? Kind Regards, Noel From: Richard Jones ***@***.***> Sent: 12 November 2024 14:09 To: ImperialCollegeLondon/fair-data-repository ***@***.***> Cc: Papantonis, Noel ***@***.***>; Assign ***@***.***> Subject: Re: [ImperialCollegeLondon/fair-data-repository] Produce technical documentation on Data Models (Issue #42) This email from ***@***.******@***.***> originates from outside Imperial. Do not click on links and attachments unless you recognise the sender. If you trust the sender, add them to your safe senders list<https://spam.ic.ac.uk/SpamConsole/Senders.aspx> to disable email stamping for this address. Assigned #42<#42> to @npapantonis<https://github.com/npapantonis>. — Reply to this email directly, view it on GitHub<#42 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAR2V3F3X62VWB7Q2ZRMWJT2AIDXTAVCNFSM6AAAAABK4GN4EKVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJVGI3DKMZTHA2DENY>. You are receiving this because you were assigned.Message ID: ***@***.******@***.***>>

[npapantonis]

@richard-jones Wayne has now review the listing provided and has a couple of queries:

• Subject/keywords: is greyed out with ‘OMIT’ in the Form Behaviour column. Does that mean depositors won’t have the option to enter subject/keyword terms, or have I misunderstood?

• Rights: again in the Form Behaviour column: "* Allow only CC0 or CC-BY. (one of these to be default and pre-filled).” I can’t remember what was said about this in the last breakout group meeting. Some repositories that focus on natural sciences e.g. Dryad, use CC0 as default, but most institutional repositories prefer CC-BY. As a STEM focused institution we are somewhat in between. At minimum depositors should have the option of choosing between the two. Most institutional repositories also provide a menu of licences to choose from, with the full range of Creative Commons licences as the minimum. This is a tricky one. I suspect most depositors will just use the default, but some might want CC-BY-NC (non-commercial), but maybe we could recommend Restricted access for those datasets and stipulate that Open is only suitable for datasets that can be published without any restrictions on reuse?

[npapantonis]

@richard-jones @J4bbi @Steven-Eardley @cc-a FYI

Wayne has agreed to keep "Subject/keywords" active as per our suggestion and given it had not been greyed out. "Rights" for the MVP, choice of CC0 and CC-BY is fine. Wayne may have misinterpreted the ‘only one license allowed’ comment and realised it refers to repeatability so makes absolute sense (and was probably added by Wayne originally). If there is a possibility/need for adding more licenses based on demand, we can look at this internally.