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

Topic 32: Is there a need for a deaccession Tool? #1118

Open
rondlg opened this issue Jun 11, 2024 · 1 comment
Open

Topic 32: Is there a need for a deaccession Tool? #1118

rondlg opened this issue Jun 11, 2024 · 1 comment
Labels
ecatalogue This issue relates or refers to the catalog/catalogue module efmnhtransactions This issue relates or refers to the transactions module structural changes This issue requires structural changes to be made to EMu

Comments

@rondlg
Copy link
Member

rondlg commented Jun 11, 2024

DISCUSSION POINTS: Conversation/Discussion was had with AMNH about the utility of having a tool that allows a user to automatically deaccession catalogue records.

@rondlg
Copy link
Member Author

rondlg commented Jun 11, 2024

DECISION(S): Whilst this was not indicated as an issue by Field Museum staff, Admins agreed that this would be a useful addition and is included in the structural changes.

Data Changes Doc :
Pre new development:
Post development:

@rondlg rondlg added structural changes This issue requires structural changes to be made to EMu efmnhtransactions This issue relates or refers to the transactions module labels Jun 11, 2024
@rondlg rondlg added ecatalogue This issue relates or refers to the catalog/catalogue module DECISION:DEVELOPMENT REQUEST and removed DECISION:DEVELOPMENT REQUEST labels Jul 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ecatalogue This issue relates or refers to the catalog/catalogue module efmnhtransactions This issue relates or refers to the transactions module structural changes This issue requires structural changes to be made to EMu
Projects
None yet
Development

No branches or pull requests

1 participant