: archivesspace_users_group-boun...@lyralists.lyrasis.org
On Behalf Of Custer,
Mark
Sent: Monday, September 28, 2020 10:41 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Agent/Subject record merging in
multi-repository setting
Betts,
Exactly what Karen and Dan said!
I would caution you
merge process.
Mark
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of
Karen Miller
Sent: Monday, 28 September, 2020 10:52 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Agent
...@northwestern.edu
874.467.3462
From: archivesspace_users_group-boun...@lyralists.lyrasis.org
On Behalf Of Daniel
Michelson
Sent: Monday, September 28, 2020 9:20 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Agent/Subject record merging in
multi-repository setting
Hi
Sorry for misspelling your name!
Dan
On Mon, Sep 28, 2020 at 10:19 AM Daniel Michelson
wrote:
> Hi Betty,
>
> Agents and subjects are not specific to repositories, so it shouldn't
> matter whether it is linked to records in multiple repositories. We have
> not encountered any problems
Hi Betty,
Agents and subjects are not specific to repositories, so it shouldn't
matter whether it is linked to records in multiple repositories. We have
not encountered any problems relating to multiple repositories when merging
agents or subjects.
All the best,
Dan
On Mon, Sep 28, 2020 at
Greetings all,
The ArchivesSpace Subject and Agent Taskforce at Harvard Library is working to
develop best practices for subject and agent record creation, editing, and
merging, and we're wondering if anyone might have experience with merging agent
and subject records in a multi-repository
sts.lyrasis.org
on behalf of
Joshua D. Shaw
*Sent:* Tuesday, September 8, 2020 8:39 AM
*To:* Archivesspace Users Group
*Subject:* Re: [Archivesspace_Users_Group] (no subject)
I've seen this as well. I *thought* it was a bot crawling the site for
indexing, since that URL is the constructed URL
org
on behalf of Joshua
D. Shaw
Sent: Tuesday, September 8, 2020 8:39 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] (no subject)
I've seen this as well. I *thought* it was a bot crawling the site for
indexing, since that URL is the constructed URL for a request, but i
on behalf of Ludwig
Possie
Sent: Friday, September 4, 2020 7:52 PM
To: Archivesspace Users Group
Subject: [Archivesspace_Users_Group] (no subject)
We're currently hosting a copy of Archivesspace 2.6.0. Recently we noticed
that Archivesspace is running with a very high cpu load. I checked
We're currently hosting a copy of Archivesspace 2.6.0. Recently we noticed
that Archivesspace is running with a very high cpu load. I checked the log
files and got the following message. I'm not sure if this has anything to
do with the CPU cycles, but the fatal messages have me concerned. This
We recently upgraded to the newest version of ArchivesSpace and we're now
having a problem with resources, subjects, agents, etc. not showing up in the
public interface until after they've been edited in the admin interface.
Anyone else have this problem?
Thank you!
Alyssa
Alyssa Pacy
11 matches
Mail list logo
