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.

Sign up for GitHub

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

Jump to bottom

econservation: Topic 9: Attaching to Deaccession events in conservation #1245

Open
rondlg opened this issue Jan 6, 2025 · 1 comment
Open

econservation: Topic 9: Attaching to Deaccession events in conservation #1245

rondlg opened this issue Jan 6, 2025 · 1 comment
Labels
econservation This issue relates or refers to the conservation module eevents This issue relates or refers to the events module efmnhtransactions This issue relates or refers to the transactions 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: Should deaccession events be attached in conservation?
@rondlg
Copy link
Member Author

rondlg commented Jan 6, 2025 •
edited
Loading

DECISION(S): No, Deaccession will no longer be recorded in Events (see Events documents.) Deaccession information will be recorded in Transaction and Catalog Module and linked accordingly

DATA CHANGES:
Data Changes Doc
Pre new development
Post development see # 5

@rondlg rondlg added workflow This issue generated either a change to an existing workflow or created a new one efmnhtransactions This issue relates or refers to the transactions module econservation This issue relates or refers to the conservation module eevents This issue relates or refers to the events module labels Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
econservation This issue relates or refers to the conservation module eevents This issue relates or refers to the events module efmnhtransactions This issue relates or refers to the transactions module workflow This issue generated either a change to an existing workflow or created a new one
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rondlg