[Archivesspace_Users_Group] Sub-subseries custom usage?

[Majewski, Steven Dennis (sdm7g)]

You could add “sub-subseries” to as an enumeration value  Controlled Value List: Archival Record Level (archival_record_level), and it would show up in the dropdown menu, however as the current enumeration values are the allowed values for the EAD c/@level attribute, you would then export invalid and non-standard EAD. 

If you choose ‘otherlevel’ from the dropdown, ArchivesSpace will display another form field where you can enter value for @otherlevel, and it should encode properly. 

https://eadiva.com/c/ <https://eadiva.com/c/>

@level – not required. The values of this attribute may be: class, collection, file, fonds, item, otherlevel, recordgrp, series, subfonds, subgrp, and subseries. For any other value of @level (such as from a locally-assigned vocabulary) choose “otherlevel” as the value, and specify name in @otherlevel attribute. Assigning an attribute to the highest-level <c> is highly-recommended.
@otherlevel – not required. If the designated value options for @level do not fit the repository needs, “otherlevel” should be used as the value for @level and the alternate term should be specified here.

If the additional keystrokes required are an issue, maybe @otherlevel can be set with an initial value in preferences, or else assigned with a plugin that adds a little javascript to the edit page. 


— Steve. 



> On Oct 20, 2020, at 12:25 PM, Earle, Lev <learle at library.rochester.edu> wrote:
> 
> Hello everyone, 
>  
> I’m wondering if anyone out there has configured their instance to make sub-subseries level designations available.
>  
> I’m currently working with some very large collection imports where sub-subseries would be useful, and know that EAD allows for I think a maximum of twelve levels (or something faintly ridiculous), but also know that the out-of-the-box AS doesn’t include a sub-subseries level designation. I know you can technically nest subseries as children under each other, but this feels like bad form and plays havoc with our display code. We could probably figure out something ourselves to hack in a sub-subseries designation, but I wanted to see what/if anyone else was doing, as we’d like to try and build consistently with other institutions to make future inter-institutional collaboration go more smoothly.
>  
> Many thanks for any help! I’m new to this listserv and have been learning a lot following conversations but still have a long ways to go.
>  
> Cheers, 
> -Lev.
>  
> ___________________________
> Lev Earle
> Special Collections Processing Archivist – RBSCP
> University of Rochester River Campus Libraries
> they/them pronouns
>  
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org <mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group <http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20201020/6ac58d4a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3342 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20201020/6ac58d4a/attachment.bin>