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.) Archives 


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 
>
>
> 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 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 
>> *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 
>>
>> 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
>> 
>> 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
>> !*
>>
>>
>> 
>> ___
>> Archivesspace_Users_Group mailing list
>> Archivesspace_Users_Group@lyralists.lyrasis.org
>>

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 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 


On Thu, Feb 16, 2023 at 10:37 AM Clair, Kevin  wrote:

External -
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
 on
behalf of Paige Monlux 
*Sent:* Thursday, February 16, 2023 1:14 PM
*To:* 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 


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


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

!*
*
*


___
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___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

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 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 
> *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 
> 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
> 
> 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
> !*
>
>
> 
> ___
> 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

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: 
https://github.com/duspeccoll/plugins_local/blob/master/schemas/archival_object_ext.rb

-kevin

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Paige 
Monlux 
Sent: Thursday, February 16, 2023 1:14 PM
To: 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
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
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://multco.us/sites/default/files/styles/small/public/AllAreWelcome_email-signature_PRIDE_ENGLISH.jpg]

[https://multco.access.preservica.com/wp-content/uploads/sites/3/2021/06/2021-06-11_6-36-08.png]
 

___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group