Re: [Archivesspace_Users_Group] Related accession and resource links on agent records

[Rachel Donahue]

Do you by any chance have multiple repositories? Agents will only show
related resources and accessions of the repository you currently have
selected.


--Rachel
--

Please note that I currently *do not have access to ARS email*. If you need
to contact me, use my LAC address: rachel.dona...@lac-group.com

The information contained in this e-mail message is confidential. If you
are not the intended recipient, any dissemination or copying is strictly
prohibited. If you think that you have received this e-mail message in
error, please contact the sender.


On Thu, Oct 17, 2019 at 10:29 AM Lucas, Dawne Howard 
wrote:

> Hi all,
>
>
>
> We recently migrated into ASpace from AT. I’ve been cleaning up agent
> records, and have noticed that some agent records don’t show which
> accession and resource records they are linked to. The resource and
> accession records indicate the link to the agent record, but not vice
> versa. Some of the agent records do display the links though, so I’m not
> sure why they appear on some records and not others.
>
>
>
> Have other people noticed this inconsistency, and is there an explanation
> for it?
>
>
>
> Thanks!
>
> -Dawne
>
>
>
> --
>
> Dawne Howard Lucas, MA, MSLS
>
> she/her/hers
>
> Technical Services Archivist
>
> Wilson Special Collections Library
>
> University of North Carolina at Chapel Hill
>
> 200 South Road, CB# 3926
>
> Chapel Hill, NC 27515
>
> T: 919-966-1776
>
> E: dawne_lu...@unc.edu
>
> Web: http://guides.lib.unc.edu/health-history
>
> ORCID:  orcid.org/ -0001-9657-8509
>
>
> ___
> 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] Related accession and resource links on agent records

[Lucas, Dawne Howard]

Hi all,

We recently migrated into ASpace from AT. I’ve been cleaning up agent records, 
and have noticed that some agent records don’t show which accession and 
resource records they are linked to. The resource and accession records 
indicate the link to the agent record, but not vice versa. Some of the agent 
records do display the links though, so I’m not sure why they appear on some 
records and not others.

Have other people noticed this inconsistency, and is there an explanation for 
it?

Thanks!

-Dawne

--
Dawne Howard Lucas, MA, MSLS
she/her/hers
Technical Services Archivist
Wilson Special Collections Library
University of North Carolina at Chapel Hill
200 South Road, CB# 3926
Chapel Hill, NC 27515
T: 919-966-1776
E: dawne_lu...@unc.edu
Web: http://guides.lib.unc.edu/health-history
ORCID:  orcid.org/ -0001-9657-8509

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

Re: [Archivesspace_Users_Group] Error? - Stanford upgrade from 1.5.4 to 2.6.0

[Joshua D. Shaw]

Are there any children for this tree - ie any archival objects underneath? If 
not, this may be related to this issue: 
https://archivesspace.atlassian.net/browse/ANW-782

Joshua


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Blake 
Carver 
Sent: Wednesday, October 16, 2019 9:35 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Error? - Stanford upgrade from 1.5.4 
to 2.6.0

If you brought over the /data/ directory, try getting rid of everything in 
there and restarting. Could just be an index issue.

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Michael 
G Olson 
Sent: Wednesday, October 16, 2019 6:17 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Error? - Stanford upgrade from 1.5.4 
to 2.6.0

Hi Alex,

Great ideas, thank you!  We didn’t get any errors when we ran the upgrade.  I 
just took a look at this resource in the Java console.  I didn’t see any 
obvious errors in the Java script consul but I was able to see the logic that 
should be generating the tree view.  My best guess is that what is going on is 
that we were using extents on the collection resource in a way that was not 
actually intended.  We also have a few examples where our archivist correctly 
encoded constituent parts as proper child objects and in these particular 
examples we don’t get a tree view error.

Thanks for your help!

Michael

On Oct 16, 2019, at 2:39 PM, Alexander Duryee 
mailto:alexanderdur...@nypl.org>> wrote:

Michael,

Do you see anything interesting in the system logs or your browser's Javascript 
console when you try to open the collection?  I don't see anything in the 
Extent record that you attached that would cause the Resource record to throw 
an error like that.

Thanks,
--Alex

On Wed, Oct 16, 2019 at 3:25 PM Michael G Olson 
mailto:mgol...@stanford.edu>> wrote:
Hi Steve, all,

Sorry about that… the error message we’re receiving when we click on the 
Collection tree is, "Oops! We're having trouble fetching this tree. Please try 
refreshing the page.”

If you open the image titled extent you'll see how our archivist entered the 
extent for this particular collection.  It looks like this isn't really defined 
as a true child of the collection.

thanks,

Michael



From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of Majewski, Steven Dennis (sdm7g) 
mailto:sd...@virginia.edu>>
Sent: Wednesday, October 16, 2019 12:15 PM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Error? - Stanford upgrade from 1.5.4 
to 2.6.0


Error messages/images are too compressed or small to read. Just a blur.  Can 
you resend or else transcribe ?  — Steve M.


On Oct 16, 2019, at 2:52 PM, Michael G Olson 
mailto:mgol...@stanford.edu>> wrote:

Hi everyone,

Here at Stanford Libraries we just ran an upgrade from 1.5.4 to version 2.6.0 
and noticed some odd behavior we’d like to validate with our peers.  We 
received no error messages while running the upgrade.  That said, for one of 
our repositories (we have many) we’ve noticed that by clicking on the resource 
tree we get an error message.  I’m speculating here but my guess is that the 
extent for this resources were not defined in such a way the application knows 
the relationship between parent and child.  Here is the error message we’re 
seeing.

.

For this particular example here is how our extents had been entered in 
application.



My questions are has anyone seen this sort of behavior before?  Is this 
something we can fix in the upgraded application or do we need to implement a 
fix before the upgrade.  Any insights anyone has on this issue would be much 
appreciated!

Michael


___
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