Thanks, Andrew! Appreciate the info! I've created a feature request: ANW-1695 Edit required fields for archival objects <https://archivesspace.atlassian.net/browse/ANW-1695>. In case anyone is interested in upvoting it. 😬
Paige Monlux *(she/her)* Digital Archivist Multnomah County (Or.) Archives <https://www.multco.us/records> On Fri, Feb 17, 2023 at 2:38 AM Andrew Morrison < andrew.morri...@bodleian.ox.ac.uk> wrote: > External - > [image: External Sender] > > 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 > type. However, as the original request was for agents, only that has been > given a UI to set them in the staff interface. You could request it be > extended: > > > https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/19202060/How+to+Request+a+New+Feature > > But I don't think either method will allow you to specify certain types of > notes be created. I could be wrong, but I think you can only make > single-instance text fields mandatory. Possibly an experienced developer > could write a plug-in to analyze the entire JSON representation of a > record, and reject it on any basis you choose, but it wouldn't be able to > highlight precisely what is missing in red in the staff interface. > > Andrew. > > > On 16/02/2023 19:39, Paige Monlux wrote: > > Thank you, Kevin! We will look into that! > > > Paige Monlux *(she/her)* > Digital Archivist > Multnomah County (Or.) Archives <https://www.multco.us/records> > > > On Thu, Feb 16, 2023 at 10:37 AM Clair, Kevin <km...@psu.edu> wrote: > >> External - >> [image: External Sender] >> 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: >> https://github.com/duspeccoll/plugins_local/blob/master/schemas/archival_object_ext.rb >> >> -kevin >> ------------------------------ >> *From:* archivesspace_users_group-boun...@lyralists.lyrasis.org < >> archivesspace_users_group-boun...@lyralists.lyrasis.org> on behalf of >> Paige Monlux <pai...@multco.us> >> *Sent:* Thursday, February 16, 2023 1:14 PM >> *To:* archivesspace_users_group@lyralists.lyrasis.org < >> archivesspace_users_group@lyralists.lyrasis.org> >> *Subject:* [Archivesspace_Users_Group] Required fields for archival and >> digital objects? >> >> >> You don't often get email from pai...@multco.us. Learn why this is >> important <https://aka.ms/LearnAboutSenderIdentification> >> >> Hi all, >> >> Is there a way to edit the Required Fields for resource, archival object, >> and digital object records? Similar to how you can with Agent records. >> >> Our guidelines require certain sub-records and notes that aren't by >> default required by ASpace. I've set up default values in some of these >> required fields, for example our Conditions Governing Use note. The default >> value appears when the CGU note is added, but we'd like it so the CGU note >> itself is by default present when the record is first created. >> >> Appreciate your help! >> Paige >> >> *Paige Monlux (she/her)* >> *Digital Archivist* >> Records Management & Archives >> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmultco.us%2Frecords&data=05%7C01%7Ckmc35%40psu.edu%7Cc6f07d6cb712417597b308db1049cc3a%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C638121681375259881%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=riYLrWEA5QI%2FrBVLZlg%2BL4Xx5pI36779YWbSlrATpP8%3D&reserved=0> >> Department of County Assets | Multnomah County >> 503.988.3741 | interoffice: 425/Archives >> >> Hours: Mon-Thu 6:30a-4p, Fri 6:30a-3p >> Note: I am out of the office every other Friday. >> >> *Explore Multnomah County's Digital Archives >> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmultco.access.preservica.com%2F&data=05%7C01%7Ckmc35%40psu.edu%7Cc6f07d6cb712417597b308db1049cc3a%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C638121681375259881%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=U0dLvtnsi5xeSdTTt9lJ9bEfUut8sCrDrH8BinbAN80%3D&reserved=0>!* >> >> >> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmultco.access.preservica.com%2F&data=05%7C01%7Ckmc35%40psu.edu%7Cc6f07d6cb712417597b308db1049cc3a%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C638121681375259881%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=U0dLvtnsi5xeSdTTt9lJ9bEfUut8sCrDrH8BinbAN80%3D&reserved=0> >> _______________________________________________ >> Archivesspace_Users_Group mailing list >> Archivesspace_Users_Group@lyralists.lyrasis.org >> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >> > > _______________________________________________ > Archivesspace_Users_Group mailing > listArchivesspace_Users_Group@lyralists.lyrasis.orghttp://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > _______________________________________________ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group@lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group >
_______________________________________________ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group