Class:ObjectClassification

[mtrekels]

Parent	ObjectGroup
Label	Object Classification
Definition	An informal classification of the type of objects within the ObjectGroup, using a hierarchical structure.
Usage
Required	No
Repeatable	Yes
Relationships	Range: ObjectGroup, ObjectClassification | Class-level properties: Reference, Identifier, MeasurementOrFact, ObjectClassification
Potential standards/vocabularies/ontologies to adopt
Notes	This class is used to categorise the ObjectGroup according to an informal, self-referential hierarchy. For example, this can be used to create a hierarchy encompassing biological, geological and anthropological collections, where a single formal taxonomy isn't appropriate.

[qgroom]

This class does not seem very well scoped. Do we need it? We already have preservationMethod in the CollectionDescription class

[ramonawalls]

This does seem redundant with objectType. I don't see the use for a separate class here.

[wouteraddink]

if objectType are things like bark, blood, bones, eggs then I guess ObjectClassification is ment to have discipline specific classification, matching with DwC BasisOfRecord like PreservedSpecimens, FossilSpecimens etc?

[mswoodburn]

There's been a bit of confusion over this... I've updated the definition and notes to better represent the original intention, moved the taxonomic properties into a new Taxon class, and added some properties to enable the construction of hierarchies. An example of the intended us of this can be found in the SYNTHESYS+ Collection Digitisation Dashboard (https://rebrand.ly/synth-cdd), where it's used for organising the collections into 'discipline' and 'category' levels.

[jbstatgen]

Could somebody (@mswoodburn ?) describe and delimit ObjectClassification in relation to CollectionDescriptionScheme?

1) Is ObjectClassification a "simple" form of CollectionDescriptionScheme? Is the intention to use it if there is only a single (or one main) classification hierarchy for the collection that in addition doesn't involve overlapping classes? Eg. based on museum departments ObjectGroups are defined and hierarchically structured by this ObjectClassification: {{{Invertebrates}Zoology}{{Ferns}{Mosses}Botany}{Fungi}{Lichens}Natural Science Collection}. As soon as a second classification is needed (eg. with a class "Cryptogams", or based on important collectors, the second classification is defined and described as CollectionDescriptionScheme. The first classification might be moved now to CollectionDescriptionScheme, too.

2) And/or do you use ObjectClassification to add a label (factor) that can be used for automatic approaches that are based on SchemeDimension? In that case the class ObjectClassification should be repeatable, or?

Sorry, I am completely lost. Intuitively, the three "Scheme" classes and this class seem to belong together somehow.