[Archivesspace_Users_Group] Problem linking multiple top containers to single component

[Rachel Aileen Searcy]

Hi Christine,

Thanks so much for looking into this issue to confirm that you're seeing
what I'm seeing as well as offer some suggestions. Your path for dismissing
changes and then returning to the component are working for me as well;
I've also found that simply closing the Errors and Warnings message at the
top of the record allows me to save the record as I was intending. A few of
my colleagues and I have noticed this error when adding as few as four
containers to an archival object, which seems to still be a relatively
reasonable amount in some circumstances, so we'll probably submit a bug
report/feature request for this.

Thanks again,
Rachel

On Tue, Sep 6, 2016 at 12:29 PM, Christine Di Bella <
christine.dibella at lyrasis.org> wrote:

> I am able to replicate this in part in test, but the circumstances are
> fairly complicated.
>
>
>
> ·         I am able to add the larger number of instances and top
> containers to a component without difficulty.
>
> ·         When I try to save a first edit I make to the component
> (doesn’t matter if it’s in the basic information area or a sub-record like
> a note) with a larger number of top containers that triggers this message
> about missing information, which appears to be caused by the top container
> (but not the instance) information being cleared from the record. All the
> instances I created are still attached, but no longer display their linked
> top container information.
>
> ·         If I dismiss that edit (by clicking out of it), return to the
> component and make the edit again, everything works as expected.
>
> ·         If I only have a few instances/containers attached to a
> component, everything works as expected.
>
>
>
> Rachel, is this what you’re seeing as well? I’m just trying to get a sense
> of if the issue is consistent, or if multiple things are happening here.
>
>
>
> (If this is what is happening, the short term solution would appear to be
> either to limit the number of container instances you add to a resource
> component, or to click out of the first edit in order to preserve the top
> containers when you have greater than 10. But obviously in the long run
> this is something we’d want to resolve, or at least have behave in a
> predictable way based on reasonable limitations.)
>
>
>
> Christine
>
>
>
> Christine Di Bella
>
> Community Outreach Manager
>
> christine.dibella at lyrasis.org
>
> 800.999.8558 x2905
>
> 678-235-2905
>
> cdibella13 (Skype)
>
> [image: cid:image003.png at 01CE734E.FD759D30]
>
>
>
>
>
>
>
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:
> archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Rachel
> Aileen Searcy
> *Sent:* Friday, September 2, 2016 10:44 AM
> *To:* archivesspace_users_group at lyralists.lyrasis.org
> *Subject:* [Archivesspace_Users_Group] Problem linking multiple top
> containers to single component
>
>
>
> Hello list,
>
>
>
> I'm running into an issue adding a large number of top container records
> to a single component in a resource record. After having added over 10
> containers a series, I tried to edit a note but received the following
> error message upon saving: "Top Container - Property is required but was
> missing." All of my top containers have Type, Indicator, and Container
> Profile fields filled in. I was able to replicate this is
> test.archivesspace.org and there seems to be a tipping point after adding
> around 10 container instances to a single AO. Tabling descriptive and
> access considerations that might suggest that's too large of a range to
> describe in a single component, does anyone happen to know if there is a
> limit to how many containers can be associated with a single component? It
> appears as though accession records are not exhibiting this problem as far
> as I can tell.
>
>
>
> Thanks very much in advance - any insight would be appreciated.
>
>
>
> Rachel Searcy
> Accessioning Archivist, Archival Collections Management
>
> New York University Libraries
>
> 212.998.2539 | rachel.searcy at nyu.edu
>
>
>
>
>
> The error:
>
>
> ​
>
>
>
> But my containers look fine?
>
>
>
>
>
>
>
> And when I open up the record again the Instances sub-record appears
> blank, even though I can locate those containers via the Manage Top
> Containers and they appear to be linked to the record:
>
>
>
>
> ​
> ​
>
>
>
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>


-- 
Rachel Searcy
Accessioning Archivist, Archival Collections Management
New York University Libraries
212.998.2539 | rachel.searcy at nyu.edu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20160912/e3fbb98a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.png
Type: image/png
Size: 7645 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20160912/e3fbb98a/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image008.png
Type: image/png
Size: 106847 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20160912/e3fbb98a/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image010.png
Type: image/png
Size: 16543 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20160912/e3fbb98a/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image009.png
Type: image/png
Size: 20695 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20160912/e3fbb98a/attachment-0003.png>