Re: [Archivesspace_Users_Group] Archon to AS migration data issue
Hi Brian, Following up. I re-migrated with all Archon containers set to Intellectual and it did the same thing as with all containers set to Physical. Is there something else I can do to solve this issue? Thank you, Josh Tillman PHP Programmer and Database Administrator Library Information Technologies & Digital Initiatives San Diego State University 5500 Campanile Drive San Diego, CA 92182-8050 619.594.1811 jdtill...@sdsu.edu On Mon, Nov 18, 2019 at 9:17 AM Josh Tillman wrote: > Hi Brian, > > Thanks for your help. > > I re-migrated after changing all containers to both Intellectual and > Physical. That made the problem worse. Each folder also duplicated for each > item in the folder (i.e. I have 30-40 instances of each folder). > > I re-migrated again after changing all containers to just Physical. That > created all the empty boxes from before but with none of the actual content. > > I have not rerun the migration with all containers set to just > Intellectual yet. > > Is there something I'm missing? > > Thank you, > > Josh Tillman > PHP Programmer and Database Administrator > > Library Information Technologies & Digital Initiatives > San Diego State University > 5500 Campanile Drive > San Diego, CA 92182-8050 > 619.594.1811 > jdtill...@sdsu.edu > > > On Wed, Nov 6, 2019 at 10:47 AM Brian Harrington < > brian.harring...@lyrasis.org> wrote: > >> Hi Josh, >> >> I’m wondering if there might be a problem with Intellectual vs. Physical >> containers. Take a look at the Level/Container Manager section in this >> document >> https://github.com/archivesspace/tech-docs/blob/master/migrations/migrate_from_archon.md >> and see if that helps. If that doesn’t fix things, let us know. >> >> Thanks, >> >> Brian >> >> > On Oct 31, 2019, at 3:26 PM, Josh Tillman wrote: >> > >> > Hello, >> > >> > I'm having an issue with the Archon to AS migration. After the >> migration tool runs, there are empty duplicate boxes showing up at the >> collection-level. Is there a way to remove them all at once or prevent them >> from duplicating in the first place? Or does each one have to be deleted >> manually? >> > >> > Thank you, >> > >> > Josh Tillman >> > PHP Programmer and Database Administrator >> > >> > Library Information Technologies & Digital Initiatives >> > San Diego State University >> > 5500 Campanile Drive >> > San Diego, CA 92182-8050 >> > 619.594.1811 >> > jdtill...@sdsu.edu >> > ___ >> > 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] Agent Relationship Associative Relator
Hi Peter, A few years ago I wrote a script for this purpose: https://gist.github.com/jambun/553434b0e81644a53229 May be useful. A couple of caveats: - The uneditable enumerations are generally uneditable for good reason. - Things may have changed. Cheers, James > On Nov 26, 2019, at 4:03 PM, Collopy, Peter S. wrote: > > Hi all. Here at Caltech we’re experimenting with using ArchivesSpace agent > records in order to link together our information and holdings related to > Caltech people across several digital and tangible repositories. One key > piece of information is what relationship each individual had to Caltech > (typically one or more of faculty, student, staff, trustee). It makes sense > to us to do this using Related Agents subrecords of the agent, with an > associative relationship between each individual and a Corporate Entity agent > record representing Caltech as an organization. It also makes sense to us to > use the Relationship Type field as a controlled vocabulary of these specific > relationships individuals have with Caltech. > > The agent_relationship_associative_relator controlled value list, though, is > one of the ones which is configured to be uneditable in ArchivesSpace. I > understand from past emails in this list (specifically Adam Jazairi and > Alexander Duryee’s emails on March 8, 2018) that it’s possible to make these > uneditable lists editable. I have two questions I’d appreciate help with from > anyone knowledgable, then: > > 1. How does one make these lists editable? I don’t see anything in config.rb. > Does it require more direct interaction with the database? Am I overlooking > something? > > 2. Would extending this particular controlled value list cause any problems > for exports to standard formats? Agents only export to EAC-CPF. It looks like > the exporter puts the relator (currently the default, “is_associative_with”) > in cpfRelationType, which doesn’t look right from the EAC-CPF spec to me, but > it doesn’t seem like it would cause problems to put “is_faculty_of” or the > link there instead—if we even have a reason to export EAC-CPF. > > Thanks for any thoughts! > > Peter > ___ > Archivesspace_Users_Group mailing list > Archivesspace_Users_Group@lyralists.lyrasis.org > http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group > > > !DSPAM:5ddd9318170751320666540! ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
[Archivesspace_Users_Group] Agent Relationship Associative Relator
Hi all. Here at Caltech we’re experimenting with using ArchivesSpace agent records in order to link together our information and holdings related to Caltech people across several digital and tangible repositories. One key piece of information is what relationship each individual had to Caltech (typically one or more of faculty, student, staff, trustee). It makes sense to us to do this using Related Agents subrecords of the agent, with an associative relationship between each individual and a Corporate Entity agent record representing Caltech as an organization. It also makes sense to us to use the Relationship Type field as a controlled vocabulary of these specific relationships individuals have with Caltech. The agent_relationship_associative_relator controlled value list, though, is one of the ones which is configured to be uneditable in ArchivesSpace. I understand from past emails in this list (specifically Adam Jazairi and Alexander Duryee’s emails on March 8, 2018) that it’s possible to make these uneditable lists editable. I have two questions I’d appreciate help with from anyone knowledgable, then: 1. How does one make these lists editable? I don’t see anything in config.rb. Does it require more direct interaction with the database? Am I overlooking something? 2. Would extending this particular controlled value list cause any problems for exports to standard formats? Agents only export to EAC-CPF. It looks like the exporter puts the relator (currently the default, “is_associative_with”) in cpfRelationType, which doesn’t look right from the EAC-CPF spec to me, but it doesn’t seem like it would cause problems to put “is_faculty_of” or the link there instead—if we even have a reason to export EAC-CPF. Thanks for any thoughts! Peter ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
