Property:status

[mtrekels]

Label	Status
Definition	The development status of the collection during a specified period.
Usage
Existing property
Existing class
Existing property identifier
Format	Text
Required	Yes
Repeatable	No
Constraints
Examples	Complete, In part, Developing, Closed, Active growth, Consumable, Decreasing, Lost, Missing, Passive growth, Static
Notes	The values/vocabularies for a status are predicated by the statusType. The in the examples mentioned terms are a cumulative list of terms associated with several different statusTypes.

[szucsichnikolaus]

Not 100% clear whether https://terms.tdwg.org/wiki/Natural_Collections_Description#Development_Status_Type or https://terms.tdwg.org/wiki/Natural_Collections_Description#Conservation_Status_Type is addressed I understood conservation Status in the first place

Format: text

[rondlg]

This similar to Stev's comment elsewhere about more literal term labels. Development status is the intent for this field. Conservation status therefore would be a separate term.

[mswoodburn]

So shall we prepend 'development' in front of 'Status' for each of the properties in the CollectionHistory class?

[qgroom]

This class is about the history of the collection not its development nor conservation.

[qgroom]

Therefore, it should details events, such as founded, destroyed, split, merged etc

[jbstatgen]

I'm looking for a home for GBIF's "accession_status", and if merged (see last week's discussion) in consequence also for GBIF's "personal_collection". CollectionHistory seems to be the fitting class.

GBIF's "accession_status" has the vocabulary ['Institutional', 'Project']. After merging with "personal_collection" this might form the expanded vocabulary ['Institutional', 'Project', 'Personal"].

Should this fit with @qgroom 's type of vocabulary ['accessioned', 'destroyed', 'bought', 'sold', 'split', 'distributed', ...] "status" will be the property. Otherwise, maybe 2+ properties are needed, since legal, management and practical (access) considerations seem to get intermingled.

Descriptions of the status of a collection's history involve information otherwise associated with Institutions (Governance /Funding: institutional (=accessioned) vs. private), PersonRole (Owner), and prov:Activity (transactions: buying, selling, destroying, distributing).

Edit: also GBIF's "active" property with ['inactive', 'active'] seems to map somewhere here.

[qgroom]

This sounds as if LC's Event is more in line with ABCD's Dataset(s). I don't know, but that sounds unlikely. An event has a specific time and place, I wouldn't not have thought a dataset would.

However, with properties "samplingProtocol" and "habitat", those sounded to me more like ABCD's Unit/Gathering/Method: > "The method (including technical means) used to make the collection or observation or to describe the capture event." and Unit/Gathering/Biotope: "An element for citing biotope type terms (e.g. classification terms) and measurements (e.g. vegetation height, salinity, slope) related to the unit's gathering site". Sounds reasonable

Does a mapping exist between abcd:Unit/Gathering and dwc term(s)? I don't know. It would be best to ask someone from Berlin Botanic Garden, maybe @DavidFichtmueller

[jbstatgen]

@qgroom 's above comment needs to be moved to the Event issue, https://github.com/tdwg/cd/issues/362

[magpiedin]

To clarify the examples here, we need to make them hierarchical with corresponding statusType values -- e.g.

• statusType = Organizational

  • status = open

• statusType = Organizational

  • status = closed

[rondlg]

This is now implemented as a 2-level hierarchy. -- For including status at the Institutional level then you would attach an ObjectGroup to the institution and then this CollectionStatusHistory attaches to that,