Re: [Archivesspace_Users_Group] Required fields for archival and digital objects?

2023-02-21 Thread Paige Monlux
Thanks, Andrew! Appreciate the info! I've created a feature request: ANW-1695 Edit required fields for archival objects . In case anyone is interested in upvoting it.  Paige Monlux *(she/her)* Digital Archivist Multnomah County (Or.)

Re: [Archivesspace_Users_Group] Required fields for archival and digital objects?

2023-02-17 Thread Andrew Morrison
There is a backend API for setting required fields: https://archivesspace.github.io/archivesspace/api/?shell#require-fields-for-a-record-type That appears to have been created to enable required fields to be set for agent records, but written in such a way as to be possible for any record

Re: [Archivesspace_Users_Group] Required fields for archival and digital objects?

2023-02-16 Thread Paige Monlux
Thank you, Kevin! We will look into that! Paige Monlux *(she/her)* Digital Archivist Multnomah County (Or.) Archives On Thu, Feb 16, 2023 at 10:37 AM Clair, Kevin wrote: > External - > [image: External Sender] > > Hi Paige, > > You can do this with plugins, by

Re: [Archivesspace_Users_Group] Required fields for archival and digital objects?

2023-02-16 Thread Clair, Kevin
Hi Paige, You can do this with plugins, by adding extensions in the "schemas" directory to add to the default behavior for a data model. Here's an example from my previous institution that extends archival objects so that component_ids are required: