List view
## Background and Description While the collection descriptors above aim to help taxonomists discover where specimens of a particular species are preserved, institutional surveys are concerned with assessment and comparison across institutions. There are many approaches to assess the composition and size of collections held by institutions, with a view to generate aggregate views at higher scales (e.g. nationally) and to draw comparisons across them. These are often in the form of a survey or structured database and in many cases use a different set of categories than how the institution has registered its collections within GRSciColl. The application of consistent categories across collections are necessary to draw consistent comparisons across them. The survey results would be clearly labeled as such and not be editable as they represent a particular assessment in a defined context. We intend to explore adding the ability to archive the outputs of such surveys when they have produced data that can be expressed within the framework of Latimer Core. As an example, the [Global Collection Survey](https://doi.org/10.1126/science.adf6434) assessed institutions against a survey scheme that included: * The type of the collections categorised to a specific list (Amphibians, birds, molluscs, human biology etc) * The geographic region categorised to a specific list (Australasia, Pacific, Europe etc) * The number of objects held for the combination of the collection type and region grouped by ranges (1-10, 11-100 etc) * The number of staff years of experience per region and separately per collection type The outputs of these data can likely be structured as Latimer Core, and held as a survey response against the specific survey protocol for the institution. We foresee that archiving these may bring benefits: 1. GRSciColl can help provide services that drive dashboards and reports 2. Survey protocols may be shared with other initiatives, helping increase the range of institutions that can be compared in a consistent manner 3. The results of previous surveys become more visible and may reduce effort spent, or the need for more surveys to be conducted. Given the feedback received, we will also explore how to make GRSciColl a place where surveys can converge and be updated. For example, we will try to answers questions like: * Can we make GRSciColl a place to collect survey results by combining the data schema review and the upload of collection descriptors? * Should/can we and how to make surveys editable? Answering those questions will help shape the roadmap for the following year. ## Notes based on feedback There were several arguments in favor of making survey results shared on GRSciColl editable in some ways. For example: * Having the survey forms in GRSciColl could be an opportunity for convergence of institutional surveys. Editing in one place for several surveys. * We could have dynamic metrics by allowing institutions to update the information regularly. We decided that when it comes to implementation this year, we will focus on the upload and storage of static surveys (with possibilities for version). The item has been updated based on the feedback.
Overdue by 1 year(s)•Due by June 30, 2024## Background and Description Currently GRSciColl is not structured to allow discovery of collections or individual specimens that could be critical for researchers. Support for describing a registered collection in GRSciColl is currently limited to single fields that capture broad statements of taxonomic coverage, geographic coverage and e.g. important collectors. With this enhancement, we intend to support richer, structured descriptions, such as the ability to upload an inventory of the species represented or e.g. a table representing the “species, sex, object count”. This is intended to both facilitate discovery of collections (“who holds preserved material of a specific species”) and to allow a more accurate description of a collections holding, whether digitized or not. We anticipate supporting multiple descriptors for a collection, with a descriptor containing a title, textual explanation and a table of data edited inline or uploaded as e.g. a spreadsheet. A simple example is illustrated. <img width="609" alt="image" src="https://github.com/gbif/registry/assets/7677271/538389cc-05e6-4bb3-8f97-bcee561f6bee"> We envisage the system would be flexible enough to accommodate differing levels of detail from simple lists, to detailed representations of the collection which we anticipate exist for some collections. By supporting multiple descriptors for a collection, the system would support different aspects of the collection to be documented at different detail levels. The contents will be indexed to help discoverability of collections. For example, we aim to index scientific names using the GBIF Backbone taxonomy in order to facilitate collection discovery by taxa. It should be noted that this approach would mean that one may not be able to aggregate counts across descriptors as objects may be included in multiple places and thus double counted. However, the primary focus of this is to support the needs of taxonomists looking to discover collections of interest or where individual specimens may reside. The Index Herbariorum has descriptor tables ([example](https://sweetgum.nybg.org/science/ih/herbarium-details/?irn=125525)) which would be automatically incorporated during the synchronization process. An API that exposes the descriptors as a Latimer Core document representing the collection will be available (likely in JSON format). ## Notes based on feedback * This item needs to be scoped before implementation. We will keep in mind the following comments: * We still don’t know how/if the search based on those descriptors could be integrated with the occurrence searches. * The breath of information that could possibly be shared this way might make the data confusing. We will need to define which descriptors/standards can supported. * During implementation, we will keep in mind that some institutions might need to upload multiple description tables for multiple collections. * The descriptors uploaded would have to follow standards (likely Darwin Core terms) * We won’t be able to infer complex metrics across tables, but the information will be available to users. * The collections without such collection descriptors will still be findable with the current search filters.
Overdue by 1 year(s)•Due by June 30, 2024•2/2 issues closed## Background and Description The data model for GRSciColl has evolved over time to accommodate the data sources being connected, such as iDigBio, Index Herbariorum and the original databases that were integrated. At the same time, there has been extensive work by the [TDWG Collections Descriptions Interest Group](https://github.com/tdwg/cd) to standardise approaches and vocabularies that are of relevance - this is emerging as a framework called Latimer Core. We will review all the fields in the data schema and their content to ensure they are intuitive, documented and where possible, aligned to [Latimer Core](https://doi.org/10.3897/biss.6.91159). As examples of what this might entail, GRSciColl currently has: * “ContentType” uses a controlled vocabulary that has caused confusion for editors. This should be reviewed and aligned to Latimer Core. * “Discipline” with a controlled vocabulary that could be aligned to the [Latimer Core Discipline](https://github.com/tdwg/cd/issues/320) * It is sometimes unclear when and how the fields “inactive”, and “isHerbarium” should be used and might ## Notes based on feedback * To facilitate this review work, we will make sure all the fields and vocabularies are available in one place. * The reviewed terms and vocabularies will be translatable. * This review will be an opportunity to outline the differences between the institutions and collections entities. * I noted specific suggestions for terms and vocabularies to use (will be translated into other GitHub issues)
Overdue by 1 year(s)•Due by March 29, 2024•11/11 issues closed