Open pbuttigieg opened 2 years ago
So we chose from https://schema.org/CreativeWork the sub-specification for Methodological Documents (keeping all from your Document pattern of course) Is there a working template we can use for this work?
@cmunozmas tagged for our hack session(s)
dspace collection dspace community adoption type method type discipline EOVs SDGs Maturity levels record title record handle record abstract record date submitted record doi obps record doi original record submitter record publishing place record last modified record year created record authors record citation record language record license record version keywords ???
I assume there will be a mapping exercise to ensure DC fields covered by the schema (generic) label I have made suggestions below but please keep me in the loop on this. Thanks
dspace collection
dspace community include sub-community
Is the document type of interest?
adoption type
method type to include old BP Type field as well as new Methodological ..
discipline - subject.parameterDiscipline EOVs do you want to include EBV and ECV? SDGs Maturity levels
record spatial
record title include alternative title
record handle
record abstract all abstract languages if more than one
record date submitted NOT NECESSARY?
record doi obps record doi original
record submitter NOT NECESARY ? this metadata is not publicly displayed in the system (only admin can view) should not be migrated into any other public system
record publishing place
record publisher
record last modified NOT NECESSARY?
record year created publication date
record authors ensure this covers editors and corporate authors as well as personal
record citation record language record license
record series
record version - not a separate metadata field but the system records the version control
keywords ??? instrumenttype; DM and Others. I have often wondered if we could capture the vocabulary terms allocated in EDS into the DSpace metadata record
—
Pauline Pauline SIMPSON Ocean Best Practices System Project Manager https://www.oceanbestpractices.org/
UNESCO /IOC Project Office for IODE, InnovOcean Campus – Jacobsenstraat 1 8400 Oostende, Belgium Email: @.**@.>; Alternate email: @.**@.>; Skype: Pauline Simpson ORCID: 0000-0003-2551-5740
From: Cristian @.> Sent: 19 January 2023 09:13 To: iodepo/odis-arch @.> Cc: Simpson, Pauline @.>; Comment @.> Subject: Re: [iodepo/odis-arch] New sub-pattern: Methodological Documents (Issue #131)
CAUTION: This email is external from UNESCO. Please be vigilant on its sender and content. ATTENTION : Cet e-mail est externe à l'UNESCO. Soyez vigilant sur son expéditeur et contenu.
dspace collection dspace community
adoption type method type discipline EOVs SDGs Maturity levels record title record handle record abstract record date submitted record doi obps record doi original record submitter record publishing place record last modified record year created record authors record citation record language record license record version keywords ???
— Reply to this email directly, view it on GitHubhttps://github.com/iodepo/odis-arch/issues/131#issuecomment-1397043201, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFZQUQ5GGPSEMKPDPW6R2LDWTFDY7ANCNFSM6AAAAAARTHX67U. You are receiving this because you commented.Message ID: @.***>
I hope it is because our emails crossed that nothing that I contributed some few minutes ago is acknowledged :)
The ticked boxes are the only ones that schema can accommodate?
Pauline Pauline SIMPSON Ocean Best Practices System Project Manager https://www.oceanbestpractices.org/
UNESCO /IOC Project Office for IODE, InnovOcean Campus – Jacobsenstraat 1 8400 Oostende, Belgium Email: @.**@.>; Alternate email: @.**@.>; Skype: Pauline Simpson ORCID: 0000-0003-2551-5740
From: Pier Luigi Buttigieg @.> Sent: 19 January 2023 09:59 To: iodepo/odis-arch @.> Cc: Simpson, Pauline @.>; Comment @.> Subject: Re: [iodepo/odis-arch] New sub-pattern: Methodological Documents (Issue #131)
CAUTION: This email is external from UNESCO. Please be vigilant on its sender and content. ATTENTION : Cet e-mail est externe à l'UNESCO. Soyez vigilant sur son expéditeur et contenu.
— Reply to this email directly, view it on GitHubhttps://github.com/iodepo/odis-arch/issues/131#issuecomment-1397108170, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFZQUQZFTZPOVAU7Y2I7323WTFJDZANCNFSM6AAAAAARTHX67U. You are receiving this because you commented.Message ID: @.***>
Hi @paulineobps - we didn't see that message during the hack session, but covered quite a few of those fields.
The ticked boxes are the only ones that schema can accommodate?
Those are the fields we would add to ODIS-Arch, with some too specific to the OBPS to be generically useful / understandable. We can add other fields as needed, even if they're not a defined class in schema.org, using additonalProperty
with good descriptions.
From the list you shared, I'm flagging these for consideration in the next round of pattern development. You can see the current status of the pattern here.
Responses to questions:
record date submitted NOT NECESSARY?
This is very specific to the hosting repository, and not so important for ODIS. As ODIS would point users to the repository, they could get that metadata there. The main date of interest would be the date created or updated.
record submitter NOT NECESARY ? this metadata is not publicly displayed in the system (only admin can view) should not be migrated into any other public system
Not so much for ODIS-level sharing. We'd want to know who authored the document, rather than who submitted it.
record last modified NOT NECESSARY?
this should be covered by dateModified
record series
Is there a Dublin Core class for this?
record version - not a separate metadata field but the system records the version control
I don't quite understand the comment here.
keywords ??? instrumenttype; DM and Others. I have often wondered if we could capture the vocabulary terms allocated in EDS into the DSpace metadata record
Keywords are supported, and can be linked to PIDs/IRIs for ontology terms etc. Opportunity to add instruments noted above. The EDS<->DSpace exchange of semantic tags is an OBPS issue, not for discussion here.
I really would appreciate seeing a crosswalk betwen the schema.org fields you intend to use to accommodate the DC/OBPS fields - at the moment it has a feel of shoehorning. We must of course first agree what DC fields are essential ' to be shoehorned' This is a comment after working through You can see the current status of the pattern [here](https://github.com/iodepo/odis-arch/blob/131-new-sub-pattern-methodological-documents/book/thematics/docs/graphs/methodology.json).
@arnounesco FYI
As a sub-specification of our Documents pattern, the Ocean Best Practices System and other methodology-focused asset management systems would benefit from a pattern dedicated to methods.
This could also be more generic, under CreativeWork, as many methods can be shared in forms other than Documents.
We'll start thinking / brainstorming here to (co-)develop a pattern with any other ODIS nodes or partners.