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

econservation: Topic 8: Parent/Child catalogue records: which to use and when? #1244

Open
rondlg opened this issue Jan 6, 2025 · 1 comment
Labels
Dept:Anthropology This issue was either submitted by or refers Anthropology Dept:Botany This issue was either submitted by or refers to Botany Dept:Conservation Dept:Exhibitions This issue was either submitted by or refers to Exhibitions Dept:Geology This issue was either submitted by or refers to Geology Dept:Zoology This issue was either submitted by or refers to Zoology ecatalogue This issue relates or refers to the catalog/catalogue module econservation This issue relates or refers to the conservation module eexhibitobjects This issue relates or refers to the exhibitions object module workflow This issue generated either a change to an existing workflow or created a new one

Comments

@rondlg
Copy link
Member

rondlg commented Jan 6, 2025

DISCUSSION POINTS: What to do for parent/child catalogue records?

  • When the subbed-out Catalogue record versus parent Catalogue record be attached to a Conservation record?
  • Conservation dept needs/wants to keep & use “Sub Number” field on Objects tab (affects workflow &/or reports)
  • BUT attaching the parent record wouldn’t tie back to a child record’s ExObj record
@rondlg rondlg added Dept:Exhibitions This issue was either submitted by or refers to Exhibitions eexhibitobjects This issue relates or refers to the exhibitions object module econservation This issue relates or refers to the conservation module Dept:Conservation labels Jan 6, 2025
@rondlg
Copy link
Member Author

rondlg commented Jan 6, 2025

DECISION(S):

  • Geology, Zoology, Library and Botany. If conservation records are created for a “part” of specimen or lot, an “uncataloged” catalogue record will be created to link to the conservation record.
  • Anthropology: Link Conservation record to the Single and Parent Catalogue records since not all records are fully split out into their component sub parts as child records. For example, if a single record represents components that are marked subs .1-3 that needs to be split out into child/sub records so the components can be tracked separately, then this Single record becomes the Parent preserving any links to the Conservation module. Child records are then created as dittos of the former single record.

DATA CHANGES:
Data Changes Doc
Pre new development: None
Post development

@rondlg rondlg added Dept:Anthropology This issue was either submitted by or refers Anthropology Dept:Botany This issue was either submitted by or refers to Botany Dept:Geology This issue was either submitted by or refers to Geology workflow This issue generated either a change to an existing workflow or created a new one Dept:Zoology This issue was either submitted by or refers to Zoology ecatalogue This issue relates or refers to the catalog/catalogue module labels Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Dept:Anthropology This issue was either submitted by or refers Anthropology Dept:Botany This issue was either submitted by or refers to Botany Dept:Conservation Dept:Exhibitions This issue was either submitted by or refers to Exhibitions Dept:Geology This issue was either submitted by or refers to Geology Dept:Zoology This issue was either submitted by or refers to Zoology ecatalogue This issue relates or refers to the catalog/catalogue module econservation This issue relates or refers to the conservation module eexhibitobjects This issue relates or refers to the exhibitions object module workflow This issue generated either a change to an existing workflow or created a new one
Projects
None yet
Development

No branches or pull requests

1 participant