search

inbo / collective-access

CollectiveAccess is free, open-source software for cataloguing and publishing museum and archival collections. We are currently evaluating and configuring the application for the INBO collections, in the context of the DiSSCo Flanders project (https://dissco-flanders.be/).
3 stars 0 forks source link

Identification & sex: pull through object hierarchy? #122

Open Eveltjen00 opened 4 months ago

Eveltjen00 commented 4 months ago

Have the option to bring the identification of the sampling point and its objects to it's parents and children in the hierarchy? For example vuursalamander -> tissue vuursalamander -> DNA vuursalamander

Maar opgelet boom -> hybride child van boom X

Maybe use a checkbox: link taxonomy with parent/child? Uit te zoeken

Eveltjen00 commented 4 months ago

Same issue with sex: it might be relevant to see this in all the child-records of the sampling point. Can this be pulled through?

Eveltjen00 commented 4 months ago

https://manual.collectiveaccess.org/providence/user/configuration/otherCommon/prepopulate.html?highlight=list%20setting

Eveltjen00 commented 4 months ago

image

Same issue with genotype and with identification. All "characteristics" and properties. Maybe have it the other way around: automatically have it linked, and action necessary to unlink it for the case of parent-child relationships that come forth of sexual reproduction.

Eveltjen00 commented 4 months ago

Similarily, it would be interesting to be able to push through the taxon of a plantation to all of its objects.

Eveltjen00 commented 3 months ago

Similar to https://github.com/inbo/collective-access/issues/78

Eveltjen00 commented 3 months ago

This is related to comment: https://github.com/inbo/collective-access/issues/105 The sampling date of the first sampling point -> object, should be fixed for all subsequent objects created.

Eveltjen00 commented 2 months ago

Maybe instead of prepopulate work more with the code? For example

ca_places.parent.preferred_labels.name
<unit relativeTo="ca_list_items.hierarchy"><p>^ca_list_items.preferred_labels.name_plural (ca_list_items.idno)</p></unit>
Object is ^ca_objects.preferred_labels.name;
Entities are: <unit relativeTo="ca_entities">^ca_entities.preferred_labels.displayname
(Birthplace: <unit relativeTo="ca_places">^ca_places.preferred_labels.name</unit></unit>
relativeTo='ca_objects.parent'
The descendant modifier returns all records below a given record. The branch modifier is similar to descendants but includes the given record along with its descendants.