tdwg / cd Goto Github PK
View Code? Open in Web Editor NEWCollection Descriptions
License: Creative Commons Attribution 4.0 International
Collection Descriptions
License: Creative Commons Attribution 4.0 International
This class has not yet any properties. Needs to be elaborated more.
I want to collect specimens in another country. I do not know the regulations regarding scientific collection and export of material in that country and I want advice and help. I want to find people in a local herbarium who will know what regulations exist and can give me advise.
I might also look for a herbarium in that country to deposit duplicate specimens. This can be to conform to regulations, as a courtesy or just as a safety measure.
Label | |
Definition | Date on which the resource was changed. |
Usage | Date on which the Collection Description record was changed. |
Existing property | dc:modified |
Existing class | |
Existing property identifier | http://purl.org/dc/terms/modified |
Format | Date |
Required | yes |
Repeatable | no |
Constraints | ISO 8601 |
Examples | 1998-02-16 1998-02 1998 2019-12-16T09:49:51Z |
Notes | Date may be used to express temporal information at any level of granularity. Recommended practice is to express the date, date/time, or period of time according to ISO 8601-1 [ISO 8601-1] or a published profile of the ISO standard, such as the W3C Note on Date and Time Formats [W3CDTF] or the Extended Date/Time Format Specification [EDTF]. If the full date is unknown, month and year (YYYY-MM) or just year (YYYY) may be used. Date ranges may be specified using ISO 8601 period of time specification in which start and end dates are separated by a '/' (slash) character. Either the start or end date may be missing. |
Persistent identifiers (PIDs) will be an important feature of any registry of collections and collection-holding institutions. If the CD metadata standard for descriptions of collections applies to the exchange of information between collection registries, a single PID system, or a well-defined coordination of multiple PID systems, will be essential. We should develop a plan that will enable us to recommend the adoption and deployment of one or more PID systems as part of CD.
(moved from tdwg/ncd#20)
from the @tdwg/dwc-qa group see tdwg/dwc-qa#84 for possible concept needed in NCD
What to do about updating this entry https://fairsharing.org/bsg-s000202/ about NCD?
Definition | Unique persistent identifier for the CollectionDescription |
Existing property | |
Existing class | |
Existing property identifier | |
Format | Text |
Required | Yes |
Repeatable | |
Constraints | GUID? |
Examples | |
Notes |
Label | Conditions of Access |
Definition | Information about who can access the collection being described or an indication of its security status. |
Usage | |
Existing property | |
Existing class | |
Existing property identifier | |
Format | |
Required | No |
Repeatable | Yes |
Constraints | |
Examples | Open to the public |
Notes | If available, this should be a URL to a stable policy page. For example, https://www.fieldmuseum.org/science/research/area/fossils-meteorites/fossils-meteorites-policies. |
Label | Record Source |
Definition | Source of the record if not created by the author named in Author. |
Usage | Source of the collection description record if not created by the entity/person/group named as "Author" or "Creator". |
Existing property | dc:source |
Existing class | |
Existing property identifier | http://purl.org/dc/terms/source |
Format | Text |
Required | No |
Repeatable | No |
Constraints | |
Examples | Index Herbariorum , Diment, J. A., & Wheeler, A. (1984). Catalogue of the natural history manuscripts and letters by Daniel Solander (1733โ1782), or attributed to him, in British collections. Archives of Natural History, 11(3), 457-488. |
Notes | The system from which the record was generated. Use the Person class instead of this property to record the name of the entity/person/group who had the role of "Creator" or "Author" for the metadata for the record. |
(Moved from tdwg/ncd#10)
Though David Shorthouse proposed it as a new term for Darwin Core, the idea might have merit at the data set level. See tdwg/dwc#180.
Parent | |
Label | Object Group |
Definition | An intentionally grouped set of objects with one or more common characteristics. |
Usage | |
Required | Yes |
Repeatable | Yes |
Relationships | Range: RecordLevel | Class-level properties: Reference, Identifier, CollectionStatusHistory, ResourceRelationship, GeographicOrigin, GeologicalContext, ChronometricAge, Taxon, StorageLocation, Event, ObjectClassification, OrganisationalUnit, MeasurementOrFact, PersonRole |
Potential standards/vocabularies/ontologies to adopt | Potential alignment with https://www.w3.org/TR/prov-o/#Collection |
Notes |
Label | Collection Name |
Definition | A short title that summarises the collection objects contained within the ObjectGroup. |
Usage | |
Existing property | |
Existing class | |
Existing property identifier | |
Format | Text |
Required | Yes |
Repeatable | No |
Constraints | |
Examples | The Leslie Hubricht Molluscan Collection , NHM Algae, Fungi and Plants collection , Crustacea โ Cirripedes, Decapoda , Global Mesozoic and Paleozoic mollusc faunas/samples |
Notes |
Perhaps we need to
Label | Record Rights |
Definition | Information about rights held in and over the resource. |
Usage | A statement of any rights held in/over the collection description record. |
Existing property | dc:rights |
Existing class | |
Existing property identifier | http://purl.org/dc/terms/rights |
Format | Text |
Required | No |
Repeatable | No |
Constraints | |
Examples | http://scratchpads.eu/about/policies/termsandconditions , All rights reserved by DataOwner Ltd. |
Notes | Typically, rights information includes a statement about various property rights associated with the resource, including intellectual property rights. Recommended practice is to refer to a rights statement with a URI. If this is not possible or feasible, a literal value (name, label, or short text) may be provided. |
Label | |
Definition | An entity responsible for making the resource. |
Usage | An entity responsible for making the collection description record. |
Existing property | dc:creator |
Existing class | |
Existing property identifier | http://purl.org/dc/terms/creator |
Format | URI |
Required | no |
Repeatable | yes |
Constraints | |
Examples | Smith, Clare Natural History Museum, London https://orcid.org/XXXX-XXXX-XXXX-XXXX https://ror.org/XXaaaXXXX |
Notes | Recommended practice is to identify the creator with a URI. If this is not possible or feasible, a literal value that identifies the creator may be provided. Equivalent property: http://xmlns.com/foaf/0.1/maker. This value would not change. Record the entity that updated the record in the Editor field. |
Label | |
Definition | An entity responsible for making contributions to the resource. |
Usage | An entity responsible for making contributions to the collection description record. |
Existing property | dc:contributor |
Existing class | |
Existing property identifier | http://purl.org/dc/terms/contributor |
Format | URI |
Required | yes |
Repeatable | yes |
Constraints | |
Examples | Smith, Clare Natural History Museum, London https://orcid.org/XXXX-XXXX-XXXX-XXXX https://ror.org/XXaaaXXXX |
Notes | Recommended practice is to identify the editor with a URI. If this is not possible or feasible, a literal value that identifies the editor may be provided. In the context of the CD data standard it is the last entity that edited the record. The entity that originally created the record should be recorded in the Creator field. |
Add to repo as markdown files rather than wiki pages
Please provide link to the BioCASE project website and an expansion and/or link to RLG Programs and link to RAVNS.
Article 40.7 of the International Code of Nomenclature for algae, fungi, and plants specifically mentions Index Herbariorum as the source of abbreviations to identify collections were types are deposited.
From 1 January 1990 all types for a new name must state where the type is deposited
40.7. For the name of a new species or infraspecific taxon published on or after 1 January 1990 of which the type is a specimen or unpublished illustration, the single herbarium, collection, or institution in which the type is conserved must be specified (see also Rec. 40A.5 and 40A.6).
Note 4. Specification of the herbarium, collection, or institution may be made in an abbreviated form, e.g. as given in Index Herbariorum (http://sweetgum.nybg.org/science/ih/) or in the World directory of collections of cultures of microorganisms.
This is done. Contributors: @debpaul @mswoodburn @WUlate
Title: Exposing the Dark Data of Undigitized Collections: a TDWG Global Standard for Collection Descriptions
Label | Rights Holder |
Definition | A person or organization owning or managing rights over the resource. |
Usage | A person or organization owning or managing rights held in/over the collection description record. |
Existing property | dc:rightsHolder |
Existing class | |
Existing property identifier | http://purl.org/dc/terms/rightsHolder |
Format | |
Required | No |
Repeatable | No |
Constraints | |
Examples | Smith, Clare , Natural History Museum, London , https://orcid.org/XXXX-XXXX-XXXX-XXXX , https://ror.org/XXaaaXXXX |
Notes | Recommended practice is to refer to the rights holder with a URI. If this is not possible or feasible, a literal value that identifies the rights holder may be provided. |
I want to use github to submit a new use case.
Covering the repo structure and conventions, and project management setup
Label | Collection Description PID |
Definition | An unambiguous reference to the collection description record. |
Usage | The contents of this field must be an instance of ltc:Identifier |
Existing property | |
Existing class | |
Existing property identifier | |
Format | Text |
Required | yes |
Repeatable | no |
Constraints | |
Examples | 10.5072/example-full |
Notes | Recommended practice is to identify the resource by means of a string conforming to an identification system. Examples include International Standard Book Number (ISBN), Digital Object Identifier (DOI), and Uniform Resource Name (URN). Persistent identifiers should be provided as HTTP URIs. |
Parent | ObjectGroup |
Label | Record Level |
Definition | The machine-actionable information profile for the collection description digital object. |
Usage | |
Required | Yes |
Repeatable | Yes |
Relationships | Range: NA | Class-level properties: ObjectGroup, OrganisationalUnit, CollectionDescriptionScheme, PersonRole, Reference, Identifier |
Potential standards/vocabularies/ontologies to adopt | |
Notes | Linked to the RDA PID Kernel recommendation (https://www.rd-alliance.org/system/files/RDA%20Recommendation%20on%20PID%20Kernel%20Information_final.pdf) |
(moved from tdwg/ncd#6)
Potential stakeholders include funding agencies (like conservation companies, and foundations) who are looking for certain data that are needed for addressing their missions. This metadata has the potential to expose what's available and help with prioritizing funding.
Label | Language |
Definition | A language of the resource. |
Usage | A language of the collection description record. |
Existing property | dc:language |
Existing class | |
Existing property identifier | http://purl.org/dc/terms/language |
Format | Text |
Required | |
Repeatable | Yes |
Constraints | |
Examples | es-419 nan-Hant-TW en Primarily English, with some text also in French. |
Notes | Recommended practice is to use either a non-literal value representing a language from a controlled vocabulary such as ISO 639-2 or ISO 639-3, or a literal value consisting of an IETF Best Current Practice 47 [IETF-BCP47] language tag. |
Includes reflecting changes to:
We need to identify the dimensions, before in each case considering what is required to incorporate them into the model / standard. The majority will already be described by existing standards (although potentially multiple options), so will be a case of hooking into the model rather than designing from scratch.
This class has not yet any properties and need to be elaborated more
Label | |
Definition | Date of creation of the resource. |
Usage | A date or range of dates over which the collection description record was created. |
Existing property | dcterms:created |
Existing class | |
Existing property identifier | http://purl.org/dc/terms/created |
Format | Text |
Required | yes |
Repeatable | no |
Constraints | |
Examples | 1998-02-16 1998-02 1998 2019-12-16T09:49:51Z |
Notes | Date may be used to express temporal information at any level of granularity. Recommended practice is to express the date, date/time, or period of time according to ISO 8601-1 [ISO 8601-1] or a published profile of the ISO standard, such as the W3C Note on Date and Time Formats [W3CDTF] or the Extended Date/Time Format Specification [EDTF]. If the full date is unknown, month and year (YYYY-MM) or just year (YYYY) may be used. Date ranges may be specified using ISO 8601 period of time specification in which start and end dates are separated by a '/' (slash) character. Either the start or end date may be missing. |
Label | License |
Definition | A legal document giving official permission to do something with the resource. |
Usage | A legal document giving official permission to do something with the collection description record. |
Existing property | dc:license |
Existing class | Rights (http://purl.org/dc/elements/1.1/rights), Rights (http://purl.org/dc/terms/rights) |
Existing property identifier | http://purl.org/dc/terms/license |
Format | Text |
Required | Yes |
Repeatable | No |
Constraints | |
Examples | https://creativecommons.org/licenses/by/4.0/ , https://creativecommons.org/publicdomain/zero/1.0/ , https://creativecommons.org/licenses/by/4.0/legalcode , https://opendatacommons.org/licenses/by/1.0/ , http://unlicense.org/ |
Notes | Recommended practice is to identify the license document with a URI. If this is not possible or feasible, a literal value that identifies the license may be provided. |
Hello @tdwg/cd
GOAL: to create an agreed format, before analyzing use-cases, in order to support CD data model development and testing. Once we agree on the format, we will begin breaking down the use cases. Thanks for your review.
This method was used by Olaf Banki at a recent ICEDIG Meeting to develop a vision for a collections digitization dashboard (CDD) model for SYNTHESYS+ to use to build a CDD for DiSSCo.
Note, for example, we decided we should add a dimensions column
For your reference, here is a much more complicated use case breakdown model from RDA. It incorporates many more levels of information (e.g. "concepts of operations" - or imagining the requirements dictated by the data, say, for how to move the data around, or keep it up-to-date, or how to share it).
Scope: note too that scope for CD is at the collections-level (not individual specimens). So only use cases in the ICEDIG example relevant to collections are pertinent to consider for this effort.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.