Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request]: Add option to make "FossilSpecimen" a default value for basisOfRecord #560

Open
ljwalker opened this issue Jun 25, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@ljwalker
Copy link
Collaborator

ljwalker commented Jun 25, 2024

Symbiota Portal Name

No response

Is your feature/tool request related to a problem? Please describe.

At present, for fossil datasets, correctly populating basisOfRecord requires manual data import, e.g. a bulk CSV ingestion, or manual updating using the Batch Editing tool. There is no option for "FossilSpecimen" to be the default record value when cataloging directly in the portal. This can easily lead to numerous records with erroneous basisOfRecord values, especially for live managed collections, leading to problematic data aggregation and reduced data visibility to researchers downstream.

Describe the solution you'd like.

Proposed solution is to create a new collection type (collType) selected from within a collection's metadata that will enable the Occurrence Editor to use "FossilSpecimen" as a default value for basisOfRecord for all occurrence records cataloged within that profile. Preliminary investigation by @ljwalker and @GregPost-ASU suggests this feature has already been partially developed and would be relatively straightforward to complete. This feature could potentially be included in 3.2.

Who else has expressed a desire for this feature/tool?

No response

When and how would this feature be used? What are some use cases?

This feature should be an option made available to Symbiota portals that accommodate fossil specimen data, e.g. Pteridoportal, Guatemala Biodiversity, MAD Paleo, PDP, etc., but it does not need to be visible in portals that do not include fossil data. For example, collections that have requested activation of the Paleo Module would be likely to use of this feature, but it would not be useful to portals that do not contain (or have the capacity to manage) fossil specimen data.

Additional context

Current configuration in Collections Profile Metadata Editor (3.1):
341867720-04d34af0-30a2-4d69-936e-178a6edfef12

@ljwalker ljwalker added the enhancement New feature or request label Jun 25, 2024
@ljwalker
Copy link
Collaborator Author

See also: #198

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants