Re: [Archivesspace_Users_Group] Quick Question about Migrating from Archon 3.21

2017-07-07 Thread Brian Harrington
Hi Rob,

It looks like the manual is out of date.  The latest version of the 
ArchonMigrator tool https://github.com/archivesspace/ArchonMigrator supports 
1.4.2 (the last release before the container management features were added).  
Other than that, I would say you have the right approach.  Archon -> ASpace 
1.4.2 -> the current version of ASpace.  I do this semi-regularly, and it works 
well.

Now for the geeky questions. :-)

Brian


— 
Brian Harrington
Migration Specialist
LYRASIS
brian.harring...@lyrasis.org
Skype: abbistani


> On Jul 7, 2017, at 9:47 AM, Rob Green  wrote:
> 
> Hi!  No difficult geeky questions, I promise!   
> 
> I'm leading my University's effort to bring Archon content into 
> ArchivesSpace, and see that the migration manual is intended for moving from 
> Archon 3.21-rev2  to ArchivesSpace 1.0.4.   I'm thinking the most prudent 
> approach will be to install ASpace 1.0.4 on our servers, do the migration, 
> and then update to ASpace 2.0.x.   
> 
> From your guys' experience, is there anything dumb / misguided / foolhardy / 
> horrifying about that approach?  Just want to cover my bases before 
> committing to this approach...
> 
> Thanks!
> Rob
> 
> a.k.a. The New Guy
> 
> 
> 
> Rob Green   rob.gr...@uni.edu
> Web Developer III
> Chair, Library Organizational Development Committee
> UNI P&S Council: At-Large Rep & Employee Relations Chair 
> Rod Library, University of Northern Iowa (Room 231)
> Cedar Falls, Iowa 50613-3675   | (319) 273-6273 
> about.me/robgreeniowa  | "Campaigner" (ENFP)
> 
> * Report web problems via https://servicehub.uni.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] EAD Importer and DAOs

2018-05-23 Thread Brian Harrington
Currently when importing an EAD, s are used to create digital objects.  As 
part of this process, the @title attribute is used for both the digital object 
title, and the caption under file versions.  I've recently run into a fun issue 
with s with @titles longer than 255 characters.  These titles are OK for 
digital_object:title, which is VARCHAR(8704) but too long for 
file_version:caption, which is VARCHAR(255).  So the import fails.

Should this be considered a bug?  If it is, and if one were theoretically 
considering a PR, would it make more sense to harmonize the length of the title 
and caption, or truncate the caption to 255 characters?  My inclination is just 
to increase the maximum length of captions, and rely on people to show 
restraint, but I know that other people might have different opinions.

Thanks,

Brian 

-- 
Brian Harrington
Migration Specialist
LYRASIS
brian.harring...@lyrasis.org
skype: abbistani


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


Re: [Archivesspace_Users_Group] EAD Importer and DAOs

2018-05-25 Thread Brian Harrington
Hi Tim,

I agree it seems a bit backwards to change the data model to suit the importer, 
which is one of the reasons I decided to pose the question to the list.  There 
could be valid reasons (display issues?) for limiting the length of the 
caption, but these things are often assigned somewhat arbitrarily, so I thought 
I would ask.  If there are reasons for keeping  for keeping the caption at 255, 
then I think it makes sense to truncate it in the importer, rather than just 
having things die on a database error.

I currently use a modified version of Mark Custer’s schematron 
<https://github.com/fordmadox/schematrons/blob/master/ArchivesSpace-EAD-validator.sch>
 to check EADs prior to import, and can certainly add code to check  
@titles.  The problem with doing that is the double use of @title for both 
digital_object:title and file_version:caption.  Since ASpace supports long 
titles, and the archivist presumably assigned a long title for a reason, I 
would hate to shorten it before import just to make sure that it fits when 
re-used as a caption.

Thanks,

Brian

> On May 24, 2018, at 5:25 PM, Timothy Dilauro  wrote:
> 
> Hi Brian,
> 
> I don't think it's a good idea to change the data model just to avoid imports 
> failing, though there may be other rationales that result in such a change.
> 
> In the mean time, it might be useful to write some XSLT or some other custom 
> code to perform sanity checks relative to ASpace restrictions ahead of EAD 
> import attempts. In that manner, those non-conformant captions (and anything 
> else you check on) could be tweaked before import.
> 
> Cheers,
> ~Tim
> 
>> On May 23, 2018, at 2:39 PM, Brian Harrington  
>> wrote:
>> 
>> 
>> Currently when importing an EAD, s are used to create digital objects.  
>> As part of this process, the @title attribute is used for both the digital 
>> object title, and the caption under file versions.  I've recently run into a 
>> fun issue with s with @titles longer than 255 characters.  These titles 
>> are OK for digital_object:title, which is VARCHAR(8704) but too long for 
>> file_version:caption, which is VARCHAR(255).  So the import fails.
>> 
>> Should this be considered a bug?  If it is, and if one were theoretically 
>> considering a PR, would it make more sense to harmonize the length of the 
>> title and caption, or truncate the caption to 255 characters?  My 
>> inclination is just to increase the maximum length of captions, and rely on 
>> people to show restraint, but I know that other people might have different 
>> opinions.
>> 
>> Thanks,
>> 
>> Brian
>> 
>> --
>> Brian Harrington
>> Migration Specialist
>> LYRASIS
>> brian.harring...@lyrasis.org
>> skype: abbistani
>> 
>> 
>> ___
>> 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] [External] Auto formatting with dates on Accession CSV import template

2023-05-04 Thread Brian Harrington
Hi Sarah,

I think that what you’re seeing is Excel reformatting the date when you reopen 
the CSV file.  CSV doesn’t store dates the same way that Excel does.  So if you 
set the format so that date shows as 2023-05-04 it will be saved that way in 
the CSV.  (You can open it in a text editor and check.) But the next time you 
open the CSV in Excel, Excel will cheerfully convert any dates that it finds 
(and sometimes other things) into Excel formatted dates.  So the key is to not 
reopen the file after you save as CSV.

The UTF-8 errors you’re seeing are something completely different.  There are 
two ways to get around them.  The first is to save from Excel with the file 
type set to CSV UTF-8 rather than regular CSV.  The second is to look non-UTF-8 
characters in your CSV and change them.  These are usually curly quotes and 
em-dashes.

I hope this helps.

Brian

--
Brian Harrington (he/him)
Data Migration Specialist
LYRASIS
brian.harring...@lyrasis.org


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Sarah 
Shepherd 
Date: Thursday, May 4, 2023 at 3:19 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] [External] Auto formatting with dates 
on Accession CSV import template
Hi Bri,

Thanks for the advice! I wish I had seen this video earlier. Unfortunately, I 
am passed that stage and understand the issues with the formatting and dates, 
the csv file is just not letting me reformat the dates. It keeps reverting 
automatically to the date format when I switch it to the text or general 
format. It’s a never-ending circle! I’ll keep fiddling with it.
Best,
Sarah

Sarah H. Shepherd
(she/her/hers)
Archivist
Scottish Rite Masonic Museum and Library
33 Marrett Road | Lexington, MA 02421
Phone: 781-457-4129 | Email: ssheph...@srmml.org


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of 
McLaughlin, Brianna Jean
Sent: Tuesday, May 2, 2023 11:18 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] [External] Auto formatting with dates 
on Accession CSV import template


 CAUTION: This email originated outside of the organization. Do not click links 
or open attachments unless you recognize the sender and know the content is 
safe.
Hi Sarah,

I think you may be encountering similar issues that I ran into with the 
accession csv template. I don’t have the process I used written out in a way 
that’s decipherable by anyone but me, but my colleague, Jeremy, and I talked 
about the errors I ran into with dates during this year’s ArchivesSpace Member 
Forum. The Youtube video is here: 
https://www.youtube.com/watch?v=XRAUu58-Lgs&t=980s. The information between 
11:46-18:23 is probably most relevant to you.

It feels weird to direct you to my own presentation, but I hope it’s helpful! 
Feel free to follow up with me if you have questions.

Bri McLaughlin, she/her/hers
Digital Collections Librarian
Indiana University
812-856-3321

From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 On Behalf Of Sarah Shepherd
Sent: Tuesday, May 2, 2023 9:10 AM
To: 
archivesspace_users_group@lyralists.lyrasis.org<mailto:archivesspace_users_group@lyralists.lyrasis.org>
Subject: [External] [Archivesspace_Users_Group] Auto formatting with dates on 
Accession CSV import template

You don't often get email from ssheph...@srmml.org<mailto:ssheph...@srmml.org>. 
Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
This message was sent from a non-IU address. Please exercise caution when 
clicking links or opening attachments from external sources.

Hello,

I’m having some difficulty with the Accession CSV template autoformatting my 
dates into the incorrect format for ArchivesSpace. It is only a problem with a 
single date. For example, I will put in 1920-04-29 which is the proper 
ArchivesSpace format for date_1_begin. The Accession CSV template then 
autocorrects it to be 4/29/1920 turning the cell format into a Date format 
instead of the standard General format. When I switch the cell format back to 
General it turns the number into 7425. When I put the correct date (1920-04-29) 
back in, it again auto formats the cell to a Date format, so it goes back to 
4/29/1920. Bizarrely, it does not do the same for another record which has 
1865-11-27 as date_1_begin.

I tried to look up how to stop this auto formatting but have not found 
anything. I even tried setting the date format to English (South Africa) which 
has a date format of 1920-04-29, but when I save the document, it got rid of 
all the formatting and reverts to 4/29/1920. I have tried importing the 
template without saving so that it keeps the 1920-04-29 date format (set to the 
English (South Africa)) and it gives an error (#<ArgumentError: invalid byte 
sequence in UTF-8>

Re: [Archivesspace_Users_Group] migration question:

2018-06-08 Thread Brian Harrington
Hi Matthew,

The URL the Archon Migrator requires is for the ArchivesSpace backend.  Try 
https://archivesspace.library.uni.edu:8089

Brian

— 
Brian Harrington
Migration Specialist
LYRASIS
brian.harring...@lyrasis.org
Skype: abbistani


> On Jun 8, 2018, at 11:46 AM, Matthew Lawson  wrote:
> 
> I am trying to migrate from Archon v3.21 rev3 to ArchivesSpace 2.3.2 using 
> the 11-2017 Archon Data Migrator Jar
> 
> I think the error log indicates a wrong URL, but I tried to enter the URL 
> where I log on and later tried it without the staff portion:  
> https://archivesspace.library.uni.edu/staff
> 
> 
> RECORD CONVERSION ERRORS/WARNINGS ( 0 ) ::
>  
>  
>  
>  
> RECORD SAVE ERRORS ( 0 ) ::
>  
> Endpoint: https://archivesspace.library.uni.edu/staff/users/admin/login
> AR Identifier:N/A
> Status code: 404
> Status text: Not Found
> 
> 
> 
>   The page you were looking for doesn't exist (404)
>   
> body { background-color: #fff; color: #666; text-align: center; 
> font-family: arial, sans-serif; }
> div.dialog {
>   width: 25em;
>   padding: 0 4em;
>   margin: 4em auto 0 auto;
>   border: 1px solid #ccc;
>   border-right-color: #999;
>   border-bottom-color: #999;
> }
> h1 { font-size: 100%; color: #f00; line-height: 1.5em; }
>   
> 
>  
> 
>   
>   
> The page you were looking for doesn't exist.
> You may have mistyped the address or the page may have moved.
>   
> 
> 
>  
>  
>  
>  
> Running for: 2 min 25.79 sec
>  
> Current # of Records Copied:
> 
> ___
> 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] Problems with Accessions CSV upload

2018-12-20 Thread Brian Harrington
If you open a CSV in Excel, it always helpfully reformats the date.  Sigh.

I think the specific error you were getting was due to the lack of an 
agent_type.  Try adding “agent_person” there.  You will also need to fill in 
agent_name_name_order (“indirect”), move the name to agent_name_primary_name, 
and then add either an agent_name_source or and agent_name_rules.  (I used 
“dacs” in agent_name_rules).  Then the csv should load.  :-)

I’d say this needs to be better documented somewhere, but then I’d feel guilty 
for not having written it up myself.

Brian

— 
Brian Harrington
Migration Specialist
LYRASIS
brian.harring...@lyrasis.org
Skype: abbistani


> On Dec 20, 2018, at 2:58 PM, Caitlin Wells  wrote:
> 
> Yes, it should be, and was when I saved the document. Is it not displaying as 
> -MM-DD?
> 
> On Thu, Dec 20, 2018 at 2:53 PM Busch, Ed  wrote:
> Does the date need to be -MM-DD rather than MM-DD-?
> 
>  
> 
> Ed Busch, MLIS
> 
> Electronic Records Archivist
> 
> Michigan State University Archives
> 
> Conrad Hall
> 
> 943 Conrad Road, Room 101
> 
> East Lansing, MI 48824
> 
> 517-884-6438
> 
> busch...@msu.edu
> 
>  
> 
>  
> 
>  
> 
> From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
>  On Behalf Of 
> Caitlin Wells
> Sent: Thursday, December 20, 2018 2:45 PM
> To: Archivesspace Users Group 
> 
> Subject: Re: [Archivesspace_Users_Group] Problems with Accessions CSV upload
> 
>  
> 
> Spreadsheet attached! It only has one record, but that one record is giving 
> me the same error message as the full sheet. 
> 
> 
> Caitlin
> 
>  
> 
> On Thu, Dec 20, 2018 at 2:09 PM Custer, Mark  wrote:
> 
> Caitlin,
> 
>  
> 
> It looks like that error means that the conversion process is trying to 
> replace some text (using “sub”), but there’s no text there at the point that 
> it’s trying to do the replacement (hence the “nil” part).  Hard to say 
> exactly what would be causing that without seeing the CSV file, though.  
> Looking at the code, it seems likely that it could be caused by a date or an 
> agent link, perhaps.  The dates are transformed a bit during the process, so 
> I’d review those first (the accession dates, and any event-related dates)
> 
>  
> 
> If it’s completely unclear what could be causing the issue when reviewing the 
> file, one strategy is just to delete half of the rows, and then try the 
> import again.  If it fails, delete half and try again.  Of course, that’s 
> hoping that not every row has the same issue, but that’s good to know, too 😊
> 
>  
> 
> Mark
> 
>  
> 
>  
> 
>  
> 
> From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
> [mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
> Hughes, Maggie
> Sent: Thursday, 20 December, 2018 11:22 AM
> To: Archivesspace Users Group 
> 
> Subject: Re: [Archivesspace_Users_Group] Problems with Accessions CSV upload
> 
>  
> 
> Hi Caitlin,
> 
>  
> 
> I never know what the error messages mean, but it is probably something 
> within the spreadsheet. Are you able to send the CSV (or a sample of it, esp. 
> if it contains sensitive data)?
> 
>  
> 
> Maggie
> 
>  
> 
> From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
>  On Behalf Of 
> Caitlin Wells
> Sent: Thursday, December 20, 2018 7:54 AM
> To: Archivesspace Users Group 
> 
> Subject: [Archivesspace_Users_Group] Problems with Accessions CSV upload
> 
>  
> 
> Hi all,
> 
>  
> 
> I'm trying to upload accessions via the CSV and keep getting the same error. 
> Every time I try to run the background job, it fails and I get the following 
> message:
> 
>  
> 
> Error: #<NoMethodError: undefined method `sub' for nil:NilClass> 
> 
>  
> 
> What does this error message mean? Is there an easy fix for this that I can 
> do within the spreadsheet and without a programmer? 
> 
>  
> 
> Best,
> Caitlin
> 
>  
> 
> --
> 
> Caitlin R. Wells
> 
> Collection Services Librarian, Special Collections Research Center
> 
> University of Michigan, Ann Arbor 48109
> 
> P: (734) 763-7901
> 
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
> 
> 
> 
>  
> 
> --
> 
> Caitlin R. Wells
> 
> Collection Services Librarian, Special Collections Research Center
> 
> University of Michigan, Ann Arbor 48109
> 
> P: (734) 763-7901
> 
> ___

Re: [Archivesspace_Users_Group] Migration from Archon - login Endpoint not found

2019-05-15 Thread Brian Harrington
Hi Bill,

You need to point the migration tool at the API endpoint, rather than either of 
the public or staff user interfaces.  It normally lives on port 8089, but your 
IT folks probably mapped it to a third URL.   I would check with them and see 
what they say.

I hope this helps.

Brian

— 
Brian Harrington
Migration Specialist
LYRASIS
brian.harring...@lyrasis.org
Skype: abbistani

> On May 15, 2019, at 3:55 PM, Bill Bellon  wrote:
> 
> I’m trying to migrate from Archon (3.21 rev-3) to Archives Space (2.5.2) 
> using the Java desktop migration tool after having followed all of the 
> instructions.
>  
> I filled out the tool with the following values:
>  
> --
> Archon Source:https://SRC-ARCHON-WEBSITE.COM  
>   (this is a placeholder as I don’t want to publicly share the actual URLs 
> yet)
>  
> Archon User:THE_USER_NAME 
>(tested on the website)
>  
> Password: THE_PASSWORD
>   (tested on the website)
>  
> Download Digital Object Files:  unchecked
>  
> Set Default Repository:  unchecked
>  
> Host:  
> https://DEST-ARCHIVESSPACE-ADMIN.COM(this is a placeholder as I don’t 
> want to publicly share the actual URLs yet)
>  
> A Space admin: THE_USER_NAME  
>(tested on the website)
>  
> Password:  THE_PASSWORD   
> (tested on the website)
>  
> Reset Password:   Left blank
>  
> Migration Options:  -bbcode_html  
>   (left the default value as is)
> --
>  
> When I click on the “Copy to Archives Space” button, I get the following in 
> the Error Log:
>  
> RECORD CONVERSION ERRORS/WARNINGS ( 0 ) ::
>  
> RECORD SAVE ERRORS ( 0 ) ::
>  
> Endpoint: https://DEST-ARCHIVESSPACE-ADMIN.COM//users/admin/login
> AR Identifier:N/A
> Status code: 404
> Status text: Not Found
> 
> 
> 
>   The page you were looking for doesn't exist (404)
>   
> body { background-color: #fff; color: #666; text-align: center; 
> font-family: arial, sans-serif; }
> div.dialog {
>   width: 25em;
>   padding: 0 4em;
>   margin: 4em auto 0 auto;
>   border: 1px solid #ccc;
>   border-right-color: #999;
>   border-bottom-color: #999;
> }
> h1 { font-size: 100%; color: #f00; line-height: 1.5em; }
>   
> 
> 
> 
>   
> The page you were looking for doesn't exist.
> You may have mistyped the address or the page may have moved.
>   
> 
> 
> 
> Running for: 5.09 sec
> 
> Current # of Records Copied:
>  
> My IT department set up Archives Space with two URLs – a public facing one 
> (let’s call that https://DEST-ARCHIVESSPACE.COM) and
> a separate URL for the backend admin interface 
> (https://DEST-ARCHIVESSPACE-ADMIN.COM). 
>  
> I tried the tool using the public URL for host and got the same results.
>  
> It looks like the Java desktop migration tool is trying to login to my 
> Archives Space website via a URL path that doesn’t exist
> (which I’ve copied the URL into my browser and confirmed the URL path doesn’t 
> exist).
>  
> Suggestions?  
>  
> Bill
> --
> Bill Bellon
> SSEC Webmaster
> Space Science and Engineering Center
> University of Wisconsin - Madison
>  
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

— 
Brian Harrington
Migration Specialist
LYRASIS
brian.harring...@lyrasis.org
Skype: abbistani



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


Re: [Archivesspace_Users_Group] ID [Archivists Toolkit Database::RESOURCE]

2019-08-05 Thread Brian Harrington
Hi Ed,

That’s an external ID.  They are usually hidden from view, but if you add 
"AppConfig[:show_external_ids] = true” to your config.rb, they should show up 
on the staff side.

I hope this helps,

Brian

— 
Brian Harrington
Migration Specialist
LYRASIS
brian.harring...@lyrasis.org
Skype: abbistani

> On Aug 5, 2019, at 3:00 PM, Busch, Ed  wrote:
> 
> With the latest release of ASpace, we’ve started noticing that if we forget 
> to uncheck “include unpublished” when exporting a PDF of a Resource, we get a 
> line added to the Summary Information underneath ID.
>  
> For example :
> ID:   
>c.00665
> ID [Archivists Toolkit Database::RESOURCE] 585032
>  
> This information is from Archivists Toolkit but has not been previously 
> viewable nor shown anywhere in the window. Why?
> See attached.
>  
>  
> Ed Busch, MLIS
> Acting Director and Electronic Records Archivist
> Michigan State University Archives
> Conrad Hall
> 943 Conrad Road, Room 101
> East Lansing, MI 48824
> 517-884-6438
> busch...@msu.edu
>  
> <4210_001.jpg>___
> 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] Harvard Excel Upload plugin working on AS 2.6.0?

2019-08-19 Thread Brian Harrington
Hi Kara,

Did you add it to your config.rb?  For example:

AppConfig[:plugins] = ['local',  'lcnaf', 'aspace-import-excel’]

Brian

> On Aug 19, 2019, at 3:28 PM, Kara Hart  wrote:
> 
> I installed the new version of Harvard aspace-import-excel 2.1.20.  I wasn't 
> sure exactly how to do that.  I stopped AS, deleted the directory for the 
> plugin, unzipped and uploaded the new 2.1.20 version and ran the 
> initialized-plugin.sh again.  It installed the gems and then I restarted AS.  
> However the button "upload via spreadsheet" is still not showing up on the 
> page when I am editing an Archival Object.  
> 
> I'm not sure what to do about this. Any suggestions?
> Kara
> 
> ~~~ Kara S. Hart 
> Systems Librarian - Library & Technology Services - Wellesley College
> 
> 
> 
> On Mon, Aug 19, 2019 at 2:53 PM Kara Hart  wrote:
> Oops, I just found a newer version of the plugin on GitHub that is for 2.6.0. 
>  I will try installing that. 
> Sorry to post unneeded, 
> Kara
> 
> ~~~ Kara S. Hart 
> Systems Librarian - Library & Technology Services - Wellesley College
> 
> 
> On Mon, Aug 19, 2019 at 2:06 PM Kara Hart  wrote:
> We are building a new server with AS 2.6.0 on CentOS 7.  I installed the 
> Harvard Excel Upload plugin, but when I go to edit a resource record, the 
> "load via spreadsheet" button is not appearing at the top like it is in our 
> 2.5.1 version.  I installed the plugin and initialized the plugin and it 
> installed all the gemfiles just as on 2.5.1.  
> Has anyone successfully installed the plugin on 2.6.0?  Is something missing 
> or blocking the plugin from adding the button on the resource edit page?  
> Thanks for any help, this plugin is very valuable and I'm not sure we can 
> upgrade without it. 
> Thanks, 
> Kara
> 
> ~~~ Kara S. Hart 
> Systems Librarian - Library & Technology Services - Wellesley College
> 
> ___
> 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] Archon to AS migration data issue

2019-11-06 Thread Brian Harrington
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


Re: [Archivesspace_Users_Group] Using the API from perl - "Must be a JSONModel(:resource) uri (you provided a Hash)"

2019-11-25 Thread Brian Harrington
Hi Alan,

You ought to be able to add the resource reference to your archival object hash 
as another hash, like:

resource => {ref => "/repositories/3/resources/391”}

If that’s not working, I’d be happy to take a look at your code if you want to 
send it to me directly.

Brian


> On Nov 25, 2019, at 10:12 PM, Alan Manifold  wrote:
> 
> Hi all,
> I'm trying to create a perl program to add archival_objects and 
> digital_objects into our ArchivesSpace system. I can query the database fine, 
> and I seem to be able to get to the right API, but I can't seem to find any 
> combination that allows me to embed a "resource" reference into my JSON for 
> the post call.
> 
> I have gotten a variety of errors, but they are all telling me that the way I 
> have specified the "resource/ref" is invalid, for example:
> 
> 'resource/ref' => 'Must be a JSONModel(:resource) uri (you provided a Hash) 
> (malformed or invalid uri? check if referenced object exists.)'
> ​
> I am assuming the real problem is that I "provided a Hash", not the 
> "malformed or invalid uri", but in case it's relevant, the uri looks like 
> this: "/repositories/3/resources/391".
> 
> I am defining the archival_object as a perl hash, with the various JSON 
> elements as hash entries, e.g.:
> 
> my %archival_object =
> (
> jsonmodel_type  =>  "archival_object",
> subjects=>  [],
> linked_events   =>  [],
> extents =>  [],
> lang_materials  =>  [],
> ...
> );
> 
> I was able to specify the "dates", "notes", and "external_ids" sections as 
> arrays with a hash as their only value, and that seems to work:
> 
> dates   =>
> [
> {
> expression  =>  $rosDate,
> date_type   =>  "inclusive",
> label   =>  "creation",
> jsonmodel_type  =>  "date"
> }
> ],
> 
> But I haven't been able to find any way to specify the "resource" section in 
> such a way that the API recognises my "ref" value. I have tried lots of ways, 
> but always get one of these errors:
> ​
> 'resource' => 'Property is required but was missing'
> 'resource' => 'Must be a object (you provided a String)'​
> 'resource/ref' => 'Must be a JSONModel(:resource) uri (you provided a Hash) 
> (malformed or invalid uri? check if referenced object exists.)'​​​
> 'resource/ref' => 'Must be a JSONModel(:resource) uri (you provided a String) 
> (malformed or invalid uri? check if referenced object exists.)'​
> 'resource/ref' => 'Must be a JSONModel(:resource) uri (you provided a Array) 
> (malformed or invalid uri? check if referenced object exists.)'​​
> ​
> I can't think of any other data types, pointers, or combinations that I can 
> try, and I don't know what the API is looking for. I even tried doing a 
> search to get a Resource record and plugging the result directly into my 
> archival_object structure, but that didn't change anything.
> 
> How can I define my archival_object structure so that it will validate? 
> Unfortunately, using python or ruby in place of perl probably isn't an 
> option. I'm happy to provide more information, including more of my code, but 
> didn't want to spam everybody with it.
> 
> Regards,
> Alan Manifold
> State Library Victoria
> 
> Alan Manifold | Library Systems & Digital Preservation Manager | Collection 
> Development & Description 
> State Library Victoria | 328 Swanston Street | Melbourne VIC 3000 
> T +61 3 8664 7122 | amanif...@slv.vic.gov.au 
> slv.vic.gov.au
> 
>   
> 
>   
> This message and any attachment is intended only for the use of the Addressee 
> and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are 
> not the intended recipient, you are hereby notified that any dissemination of 
> this communication is strictly prohibited. If you have received this 
> communication in error, please delete all copies of the message and its 
> attachments and notify the sender immediately. Thank you. 
> ___
> 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] Trouble transferring resource

2020-01-07 Thread Brian Harrington
Hi Don,

We saw this error recently with a resource that shared a top container with 
another resource.  Since top containers are scoped to repositories, when you 
transfer a resource ASpace moves its top containers to the new repository.  But 
if a top container is linked to another resource in the old repo, ASpace can’t 
move it.  I suspect you would get this same message with any repo-scoped item 
that is linked to multiple resources.

Could this be your issue?

Brian

— 
Brian Harrington
Migration Specialist
LYRASIS
brian.harring...@lyrasis.org

> On Jan 7, 2020, at 2:09 PM, Donald Mennerich  wrote:
> 
> Laney, et al.
> 
> Has there been anything done with this situation? A user here was attempting 
> to transfer resource from repo 2 to repo 8, but we're getting an assertion 
> failed error in the log.
> 
> {
>   
> "error": "ASSERTION FAILED: {SNIP} has a repo_id of 8 but the active 
> repository is 2"
> 
> }
> 
> This transfer is working on some resources, but not others, it does not seem 
> to be related to the size of the resources. We are getting the same error in 
> the log if this is done either through the frontend or via the api. Could 
> this be the same problem that Trevor reported in this thread in 2017. We are 
> on v2.7.0.
> 
> Thanks, 
> 
> Don
> 
> Donald R. Mennerich, digital archivist
> New York University Libraries
> don.menner...@nyu.edu (212) 992-6264
> 
> 
> 
> On Mon, Jun 26, 2017 at 9:23 AM Laney McGlohon  
> wrote:
> Hey Trevor,
> 
>  
> 
> We need to change and use sessions instead of cookies for transferring large 
> resources.
> 
> I have added comment from StackOverflow (my favorite source) to the JIRA 
> ticket,
> 
>  
> 
> Here it is again:
> 
>  
> 
> Rails cookies are limited to 4KB. Note that the sessions is also stored in 
> the cookie in the default configuration. See: 
> http://guides.rubyonrails.org/security.html#session-storage
> 
> The only thing you can do about that: Do not store big objects in the cookie. 
> Store them in the database and then only store the object's id in the cookie.
> 
> This answer might also be interesting to you: 
> https://stackoverflow.com/a/4604212/2483313
> 
>  
> 
> Laney
> 
>  
> 
>  
> 
> Laney McGlohon
> 
> ArchivesSpace Tech Lead
> 
> laney.mcglo...@lyrasis.org
> 
> 800.999.8558 x2927
> 
> laneymcglohon Skype
> 
>  
> 
>  
> 
>  
> 
> From:  on behalf of 
> Trevor Thornton 
> Reply-To: Archivesspace Users Group 
> 
> Date: Friday, June 23, 2017 at 10:21 AM
> To: Archivesspace Users Group 
> 
> Subject: [Archivesspace_Users_Group] Trouble transferring resource
> 
>  
> 
> Hi-
> 
>  
> 
> We're trying to transfer a relatively large resource to a different 
> repository and the transfer keeps failing with a CookieOverflow exception 
> (the most delicious exception of all).
> 
>  
> 
> The exception response HTML is attached. We're on v. 1.5.1.
> 
>  
> 
> Anybody every experience this? Is there a cure?
> 
>  
> 
> Thanks,
> 
> Trevor Thornton
> 
>  
> 
> --
> 
> Trevor Thornton
> 
> Applications Developer, Digital Library Initiatives
> 
> North Carolina State University Libraries
> 
> ___
> 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] Unprocessed Accessions Report

2020-10-01 Thread Brian Harrington
Hi Linda,

I think adding the event records is the only thing that’s going to work with 
that report.  Fortunately, it’s not too hard to do with the API.  Depending on 
your familiarity with the API, you might find Bria Parker’s wonderful blog post 
here:  
https://icantiemyownshoes.wordpress.com/2015/11/20/how-i-learned-to-stop-worrying-and-love-the-api/
 useful.   She describes how she  used OpenRefine and a little bit of shell 
scripting to add processing status events to all of her accessions.

I hope this helps,

Brian

--
Brian Harrington
Data Migration Specialist
LYRASIS
brian.harring...@lyrasis.org

From:  on behalf of 
Linda Hocking 
Reply-To: Archivesspace Users Group 

Date: Thursday, October 1, 2020 at 12:23 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Unprocessed Accessions Report

Kate,

Thank you. We have marked them complete, but they still appear in the report. 
The total count of collections and the total unprocessed show the same number. 
I was just hoping someone else might have already figured out a more efficient 
way to remedy this than to enter 1000 or so event records without having any 
useful data to put in them. We can sort the report by the Linked Resource Title 
field to determine which ones have no linked resource records, but of course 
some of the collections with resource records are unprocessed.

Thanks for sharing your modifications to the processing status list. I know we 
have several partially processed as well, so I may make that one of our options.

Linda

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Bowers, 
Kate A.
Sent: Wednesday, September 30, 2020 4:03 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Unprocessed Accessions Report

There is “processing status” in accession records. I don’t think there is a way 
to update processing statuses in bulk through the user interface, but it is a 
good place to indicate whether an accession has been processed or not or 
something in between.

Processing statuses can be the default or can be edited using Controlled Value 
List and selecting Collection Management Processing Status
A selection of ours are as follows:

  *   Completed
  *   In progress
  *   Partially processed
  *   Unknown
  *   Unprocessed


(For the very curious: “In progress” means we’re working on it. “Partially 
processed” means it’s not completed, but we’re not working on it.)

Kate


Kate Bowers
Collections Services Archivist for Metadata, Standards, and Systems
Harvard University Archives
kate_bow...@harvard.edu<mailto:kate_bow...@harvard.edu>
https://archives.harvard.edu
617-998-5238

From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 On Behalf Of Linda Hocking
Sent: Wednesday, September 30, 2020 3:43 PM
To: 
archivesspace_users_group@lyralists.lyrasis.org<mailto:archivesspace_users_group@lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Unprocessed Accessions Report

Good afternoon,

One of our work from home data cleanup projects has been dealing with the 
accession records that weren’t linked to resources. When we finished 
re-linking, we attempted to find a list of all unprocessed accessions. 
Unfortunately, the Unprocessed Accessions report shows all of our collections 
because there aren’t events for each accession record noting they have been 
processed. Many of these were processed quite some time ago and imported from 
Archon, we don’t have dates or really any notes to add that aren’t already in 
the finding aid processing notes fields. I’m sure there’s a really good 
database reason why this can’t just be a check box, but I wonder if anyone has 
had this problem and whether you figured out an quick and easy way to 
create/import the events rather than adding one at a time.

Many thanks in advance for help and advice!

Linda


Linda M. Hocking, CA
Curator of Library & Archives
Litchfield Historical Society
P.O. Box 385
Litchfield, CT 06759
860-567-4501
https://www.litchfieldhistoricalsociety.org

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


Re: [Archivesspace_Users_Group] Appraisal information database location

2020-11-19 Thread Brian Harrington
Hi Bryan,

Appraisal is just a note, so it should be in the “note” table.  The JSON for 
each note is stored in the notes field.  You’ll need to use the MySQL JSON 
functions to extract the information you want 
https://dev.mysql.com/doc/refman/5.7/en/json-search-functions.html .

I hope this helps.

Brian

--
Brian Harrington (he/him)
Data Migration Specialist
LYRASIS
brian.harring...@lyrasis.org


From:  on behalf of 
Bryan W Sutherland 
Reply-To: Archivesspace Users Group 

Date: Thursday, November 19, 2020 at 1:50 PM
To: "archivesspace_users_group@lyralists.lyrasis.org" 

Subject: [Archivesspace_Users_Group] Appraisal information database location

Hello,

I’m trying to locate where in the ASpace database the information within the 
item-level appraisal tag is located. There is date information within this tag 
that I would like to extract. My colleagues in technical support and I have 
been unable to find it and there doesn’t seems to be a report with that 
information either.

Any help would be greatly appreciated, thanks!

Bryan Sutherland
Collections Management Archivist
The MITRE Corporation
Bedford, MA
781-271-8941

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


Re: [Archivesspace_Users_Group] Strange indexing issue v2.81

2020-11-19 Thread Brian Harrington
Hi Zach,

Try truncating the deleted_records table and reindexing.  That usually seems to 
solve issues with resources disappearing from the search.

Brian

--
Brian Harrington (he/him)
Data Migration Specialist
LYRASIS
brian.harring...@lyrasis.org

From:  on behalf of 
Zachary L Pelli 
Reply-To: Archivesspace Users Group 

Date: Thursday, November 19, 2020 at 4:11 PM
To: "ArchivesSpace List (archivesspace_users_group@lyralists.lyrasis.org)" 

Subject: [Archivesspace_Users_Group] Strange indexing issue v2.81

Hey all,

After installing v2.81 we're having a strange issue, seemingly related to the 
index. Some collections cannot be found via search as they were before. I 
deleted the index in order to force a reindex and the collections were then 
searchable for a time. But coming back later, the issue had manifested once 
again and those collections would not appear in searches. Is this something 
that anyone has experienced before? I can provide logs and examples if you need 
more information.

Regards,

Zach Pelli
Seton Hall University Libraries
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


Re: [Archivesspace_Users_Group] Unpublished and suppressed records

2021-02-23 Thread Brian Harrington
Hi Jennifer,

The built-in “Resources List Report” includes a column for published status.  
Would that work for your purposes?

And I’m 99% certain suppressed records aren’t included in OAI.  If they are, 
it’s a bug.

I hope this helps.

Brian

--
Brian Harrington (he/him)
Data Migration Specialist
LYRASIS
brian.harring...@lyrasis.org


From:  on behalf of 
"Waxman, Jennifer" 
Reply-To: Archivesspace Users Group 

Date: Monday, February 22, 2021 at 7:38 PM
To: "archivesspace_users_group@lyralists.lyrasis.org" 

Subject: [Archivesspace_Users_Group] Unpublished and suppressed records

Hello ASpaceland,

Does anyone have a trick to identifying all unpublished resource records in 
their repository? Any way to see a list or even export one? Also, do you know 
if suppressing a record will keep it hidden from an OAI harvest?

Thanks!
Jennifer


Jennifer Waxman
Head, Collection Management
Tulane University Special Collections
Howard-Tilton Memorial Library, Jones Hall
6801 Freret Street
New Orleans LA 70118
504.247.1806
jwaxm...@tulane.edu
[cid:image001.jpg@01D709D4.72A03E20]

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


Re: [Archivesspace_Users_Group] Generate PDF Staff side failing - Preservica added content?

2021-04-01 Thread Brian Harrington
Hi Ed,

It looks like the problem is with s (or anything else) that have an 
@href attribute that has anything other than the bare URL in it.  For example, 
this one:


  https://us.preservica.com/explorer/explorer.html#prop:7&6e734ad9-75bc-4f06-a5a0-7aa458e39746">Preservica
 Internal"
xlink:role="Digital Preservation Staff System" 
xlink:type="locator"/>

The as-ead-pdf.xsl copies the contents of the @href directly into the 
@external-destination of an fo:basic-link element, and then the FOP processor 
is choking on it.

And as a data point for everyone, this should have just started breaking in 
2.8.1.  The included FOP was upgraded to the current version in that release 
(blame me!) and that appears to have better validation of URIs.  It looks like 
older versions simply included in the PDF.

I hope this helps.

Brian


From:  on behalf of 
"Busch, Ed" 
Reply-To: Archivesspace Users Group 

Date: Thursday, April 1, 2021 at 11:43 AM
To: Archivesspace Users Group 
, Benn Joseph 

Subject: Re: [Archivesspace_Users_Group] Generate PDF Staff side failing - 
Preservica added content?

Sure. I just put a ticket in with my local IT for some help.

Ed Busch, MLIS
Interim Head of University Archives and Historical Collections
Electronic Records Archivist
Conrad Hall, 943 Conrad Road, Room 101
East Lansing, MI 48824
517-884-6438
busch...@msu.edu
he/him/his


From:  on behalf of 
Benn Joseph 
Reply-To: "archivesspace_users_group@lyralists.lyrasis.org" 

Date: Thursday, April 1, 2021 at 11:35 AM
To: "archivesspace_users_group@lyralists.lyrasis.org" 

Subject: Re: [Archivesspace_Users_Group] Generate PDF Staff side failing - 
Preservica added content?

Hey Ed—can you share the EAD export for one that isn’t working?
--Benn

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Busch, Ed
Sent: Thursday, April 01, 2021 8:55 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Generate PDF Staff side failing - 
Preservica added content?

Thanks, Steve. Time to dig into this deeper.
Some of my Preservica ones work fine.

Ed Busch, MLIS
Interim Head of University Archives and Historical Collections
Electronic Records Archivist
Conrad Hall, 943 Conrad Road, Room 101
East Lansing, MI 48824
517-884-6438
busch...@msu.edu
he/him/his


From: 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of "Majewski, Steven Dennis (sdm7g)" 
mailto:sd...@virginia.edu>>
Reply-To: 
"archivesspace_users_group@lyralists.lyrasis.org"
 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Date: Wednesday, March 31, 2021 at 4:06 PM
To: 
"archivesspace_users_group@lyralists.lyrasis.org"
 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Generate PDF Staff side failing - 
Preservica added content?

It definitely doesn’t like those Preservica URLs.

The staff PDF production goes thru 3 steps, and you can do them separately and 
manually to debug.

[1] export EAD XML
[2] Run XSLT processor on EAD with /stylesheets/as-ead-pdf.xsl xsl-fo stylesheet
$ saxon -xsl:archivesspace/stylesheets/as-ead-pdf.xsl 
-s:UA.15.9_20210331_175003_UTC__ead.xml -o:fop.fo
[3] Run FOP processor on output of xsl-fo stylesheet.
$ fop fop.fo -pdf fop.pdf

After an error on logo image (because I’m not in the right directory and didn’t 
pass a param so it can find it)
And a bunch of warning in info messages that can be ignored, I get a whole 
series of errors like this:

SEVERE: Error while rendering page 19
java.lang.IllegalStateException: java.net.URISyntaxException: Illegal character 
in scheme name at index 0: 
%3Ca%20href=%22https://us.preservica.com/explorer/explorer.html%23prop:7&de6cbfd3-5bdf-41d1-a313-e323698859f2%22%3EPreservica%20Internal%3C/a%3E
at org.apache.fop.pdf.PDFFactory.getFileUri(PDFFactory.java:688)
at org.apache.fop.pdf.PDFFactory.getTargetUri(PDFFactory.java:646)
at org.apache.fop.pdf.PDFFactory.getExternalAction(PDFFactory.java:585)
at 
org.apache.fop.render.pdf.PDFDocumentNavigationHandler.getAction(PDFDocumentNavigationHandler.java:173)
at 
org.apache.fop.render.pdf.PDFDocumentNavigationHandler.renderLink(PDFDocumentNavigationHandler.java:107)
at org.apache.fop.render.intermediate.IFRenderer.renderPage(IFRenderer.java:597)
at org.apache.fop.area.RenderPagesModel.addPage(RenderPagesModel.java:123)
at 
org.apache.fop.layoutmgr.AbstractPageSequenceLayoutManager.finishPage(AbstractPageSequenceLayoutManager.java:316)
at 
org.apache.fop.layoutmgr.PageSequenceLayoutManager.finish

Re: [Archivesspace_Users_Group] Generate PDF Staff side failing - Preservica added content?

2021-04-01 Thread Brian Harrington
And looking more closely, I see that Steve already identified the problematic 
links for you.  Sorry about the duplication.

Brian

From:  on behalf of 
Brian Harrington 
Reply-To: Archivesspace Users Group 

Date: Thursday, April 1, 2021 at 12:37 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Generate PDF Staff side failing - 
Preservica added content?

Hi Ed,

It looks like the problem is with s (or anything else) that have an 
@href attribute that has anything other than the bare URL in it.  For example, 
this one:


  https://us.preservica.com/explorer/explorer.html#prop:7&6e734ad9-75bc-4f06-a5a0-7aa458e39746">Preservica
 Internal</a>"
xlink:role="Digital Preservation Staff System" 
xlink:type="locator"/>

The as-ead-pdf.xsl copies the contents of the @href directly into the 
@external-destination of an fo:basic-link element, and then the FOP processor 
is choking on it.

And as a data point for everyone, this should have just started breaking in 
2.8.1.  The included FOP was upgraded to the current version in that release 
(blame me!) and that appears to have better validation of URIs.  It looks like 
older versions simply included in the PDF.

I hope this helps.

Brian


From:  on behalf of 
"Busch, Ed" 
Reply-To: Archivesspace Users Group 

Date: Thursday, April 1, 2021 at 11:43 AM
To: Archivesspace Users Group 
, Benn Joseph 

Subject: Re: [Archivesspace_Users_Group] Generate PDF Staff side failing - 
Preservica added content?

Sure. I just put a ticket in with my local IT for some help.

Ed Busch, MLIS
Interim Head of University Archives and Historical Collections
Electronic Records Archivist
Conrad Hall, 943 Conrad Road, Room 101
East Lansing, MI 48824
517-884-6438
busch...@msu.edu<mailto:busch...@msu.edu>
he/him/his


From:  on behalf of 
Benn Joseph 
Reply-To: "archivesspace_users_group@lyralists.lyrasis.org" 

Date: Thursday, April 1, 2021 at 11:35 AM
To: "archivesspace_users_group@lyralists.lyrasis.org" 

Subject: Re: [Archivesspace_Users_Group] Generate PDF Staff side failing - 
Preservica added content?

Hey Ed—can you share the EAD export for one that isn’t working?
--Benn

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Busch, Ed
Sent: Thursday, April 01, 2021 8:55 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Generate PDF Staff side failing - 
Preservica added content?

Thanks, Steve. Time to dig into this deeper.
Some of my Preservica ones work fine.

Ed Busch, MLIS
Interim Head of University Archives and Historical Collections
Electronic Records Archivist
Conrad Hall, 943 Conrad Road, Room 101
East Lansing, MI 48824
517-884-6438
busch...@msu.edu<mailto:busch...@msu.edu>
he/him/his


From: 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of "Majewski, Steven Dennis (sdm7g)" 
mailto:sd...@virginia.edu>>
Reply-To: 
"archivesspace_users_group@lyralists.lyrasis.org<mailto:archivesspace_users_group@lyralists.lyrasis.org>"
 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Date: Wednesday, March 31, 2021 at 4:06 PM
To: 
"archivesspace_users_group@lyralists.lyrasis.org<mailto:archivesspace_users_group@lyralists.lyrasis.org>"
 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Generate PDF Staff side failing - 
Preservica added content?

It definitely doesn’t like those Preservica URLs.

The staff PDF production goes thru 3 steps, and you can do them separately and 
manually to debug.

[1] export EAD XML
[2] Run XSLT processor on EAD with /stylesheets/as-ead-pdf.xsl xsl-fo stylesheet
$ saxon -xsl:archivesspace/stylesheets/as-ead-pdf.xsl 
-s:UA.15.9_20210331_175003_UTC__ead.xml -o:fop.fo
[3] Run FOP processor on output of xsl-fo stylesheet.
$ fop fop.fo -pdf fop.pdf

After an error on logo image (because I’m not in the right directory and didn’t 
pass a param so it can find it)
And a bunch of warning in info messages that can be ignored, I get a whole 
series of errors like this:

SEVERE: Error while rendering page 19
java.lang.IllegalStateException: java.net.URISyntaxException: Illegal character 
in scheme name at index 0: 
%3Ca%20href=%22https://us.preservica.com/explorer/explorer.html%23prop:7&de6cbfd3-5bdf-41d1-a313-e323698859f2%22%3EPreservica%20Internal%3C/a%3E<https://urldefense.com/v3/__http:/us.preservica.com/explorer/explorer.html*23prop:7&de6cbfd3-5bdf-41d1-a313-e323698859f2*22*3EPreservica*20Internal*3C/a*3E__;JSUlJSUl!!Dq0X2DkFhyF93HkjWTBQKhk!Hsw2gQN-eCPFzzZjeib5S9arCzVMsBmBkrg8hTQhxrGU3eJZL3c_bBWC8WLwWbMb5NPCl5pt$>
at org.apache.fop.pdf.PDFFactory.getFileUri(PDFFactory.java:688)
at org.apache.fop.pdf.PDFFactory.getTargetUri(PDFFactory.java:646)
at org.apache.

Re: [Archivesspace_Users_Group] API output - extra unicode

2021-09-03 Thread Brian Harrington
Hi Tom,

In my experience \u00c3 appearing in anything is almost always a sign of 
encoding issues.  I would make sure that everything is UTF-8 all the way 
through.

Brian

From:  on behalf of 
Tom Hanstra 
Reply-To: Archivesspace Users Group 

Date: Friday, September 3, 2021 at 11:06 AM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] API output - extra unicode

On our local version of ArchivesSpace, we are testing API output and are 
finding that we are getting extra Unicode characters on export. It looks like 
the data is right in the database, but doesn't quite come out right from the 
API extract. It looks like there is an extra unicode character added (in some 
of the code we reviewed, this was either \u00c3 or \u00a2).


Where might we have something set incorrectly?  Where might the extra data be 
coming from or have been introduced along the way?


Thanks,
Tom


--
Tom Hanstra
Sr. Systems Administrator
hans...@nd.edu

[Image removed by sender.]
___
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 generating PDF export for a finding aid.

2022-03-15 Thread Brian Harrington
Hi Kirill,

Usually this error means that you have a  or  with a target that 
doesn’t exist.  If you have trouble finding it, and want to post an EAD export 
from the collection here, we can help you track it down.

Brian

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Kirill 
Batyuk 
Date: Tuesday, March 15, 2022 at 9:15 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Error generating PDF export for a 
finding aid.
Thank you,

I found an ampersand that was causing this problem, Now I’m getting another 
error:

Generating PDF for Titanic Discovery collection
org.apache.fop.fo.ValidationException: Missing attribute on fo:basic-link: 
Either external-destination or internal-destination must be specified. (See 
position 1107:86)
net.sf.saxon.s9api.Xslt30Transformer.applyTemplates(net/sf/saxon/s9api/Xslt30Transformer.java:451)
java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498)
org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:426)
org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:293)
org.jruby.RubyClass.finvokeWithRefinements(org/jruby/RubyClass.java:514)
org.jruby.RubyBasicObject.send(org/jruby/RubyBasicObject.java:1755)
org.jruby.RubyKernel.send(org/jruby/RubyKernel.java:2200)
org.jruby.RubyKernel$INVOKER$s$send.call(org/jruby/RubyKernel$INVOKER$s$send.gen)
RUBY.invocation_lambda(/data/archivesspace/gems/gems/saxon-rb-0.8.3-java/lib/saxon/xslt/executable.rb:270)
org.jruby.RubyProc.call(org/jruby/RubyProc.java:291)
org.jruby.RubyProc$INVOKER$i$call.call(org/jruby/RubyProc$INVOKER$i$call.gen)
RUBY.to_destination(/data/archivesspace/gems/gems/saxon-rb-0.8.3-java/lib/saxon/xslt/invocation.rb:73)
RUBY.to_fo(/data/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:44)


Kirill.


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Dan 
Michelson
Sent: Tuesday, March 15, 2022 8:44 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Error generating PDF export for a 
finding aid.

Hi Kirill,

The relevant line in your error message is this:
org.xml.sax.SAXParseException; lineNumber: 139; columnNumber: 16002; The 
reference to entity "G" must end with the ';' delimiter.

I have not seen that specific error before, but I find it's often easiest to 
export the resource as EAD and look at the XML for the issue.

Also, the staff interface and PUI use different PDF exporters.  Sometimes you 
can generate a PDF from one and not the other.

All the best,

Dan

P. S. Minor qualification to Jim's note about ampersands.  In our experience, 
ampersands work fine if there are spaces after them.  It's ampersands 
immediately followed by a character that throws errors.

On Tue, Mar 15, 2022 at 8:34 AM James E. Cross 
mailto:jcr...@clemson.edu>> wrote:
I am wondering if this is the “&” problem. A PDF cannot be generated if there 
is an “&” anywhere in the description. We ran into that problem here at Clemson.

Jim Cross
Manuscripts Archivist



James Edward Cross, C.A. CLEMSON UNIVERSITY
Manuscripts Archivist
Special Collections and Archives
Clemson University Libraries
Box 343001
Clemson, SC  29634-3001
Phone: (864) 656-5182
Website: 
http://library.clemson.edu/depts/specialcollections/
Pronouns: he/him/his
Traditional Cherokee Lands | Site of Fort Hill Plantation
Please do not feel obligated to respond to this message outside of your normal 
working hours.


From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 On Behalf Of Kirill Batyuk
Sent: Tuesday, March 15, 2022 8:25 AM
To: 
archivesspace_users_group@lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Error generating PDF export for a finding 
aid.

Hi,

Our Archivist is running into a problem with generating PDF for a finding aid. 
The job fails with the following log:

Generating PDF for Titanic Discovery collection
org.xml.sax.SAXParseException; lineNumber: 139; columnNumber: 16002; The 
reference to entity "G" must end with the ';' delimiter.
net.sf.saxon.s9api.DocumentBuilder.build(net/sf/saxon/s9api/DocumentBuilder.java:360)
java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498)
org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:456)
or

Re: [Archivesspace_Users_Group] Rights statements not showing up in the public interface

2022-03-25 Thread Brian Harrington
I’ve gotten the impression that rights statements were created for people who 
wanted more structure than a mixed content note can provide.  Some of the specs 
even refer to them as “machine-actionable rights statements.”

I would love to hear from folks that have implemented systems based on the data 
in the rights statements. I can think of examples where they would be useful, 
but I don’t think I’ve run across instances of them being used this way in 
practice.

Brian

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Bowers, 
Kate A. 
Date: Friday, March 25, 2022 at 10:03 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Rights statements not showing up in 
the public interface
Thanks for the links, Christine!

To everyone:

I’m looking for a direct statement of ***why***  you would use a rights 
statement rather than a conditions governing use note.

The manual makes them seem redundant. If they are not redundant, what is their 
relationship? The manual’s suggestion that a conditions on use note can 
“supplement” a rights statement makes it seem as if the element that isn’t 
mentioned in DACS is needed and the one that is in DACS is secondary.

If anyone can offer an explanation and elucidate when a rights statement is 
appropriate and when a conditions on use statement is appropriate, I’d be 
grateful.

Thanks,

Kate

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of 
Christine Di Bella
Sent: Friday, March 25, 2022 9:18 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Rights statements not showing up in 
the public interface

Hello everyone,

I took note of this discussion and wanted to call out a few things that may be 
helpful for those not as steeped the history and lore of ArchivesSpace as I am. 
😊

Rights Statements is a sub-record that was included in the original vision for 
ArchivesSpace, and was in Archivists’ Toolkit before it. The historical 
functional requirements, specifications, and technical architecture report are 
linked from our website: 
https://archivesspace.org/application/technical-documentation.

There is a section on Rights Statements in the User Manual (which lives at 
https://archivesspace.atlassian.net/wiki/spaces/ArchivesSpaceUserManual/pages/909934631/ArchivesSpace+User+Manual).
 Please note that the instructions for rights statements there suggest that 
people supplement them with Conditions Governing Access or Conditions Governing 
Use notes.
Rights Statements were significantly expanded in 2017 (for version 
2.1.0)
 courtesy of a community-authored and vetted specification (attached to 
https://archivesspace.atlassian.net/browse/ANW-123).
 There are some user stories included with it. That specification did not 
include a request for rights statements to appear in the public interface 
(possibly because it preceded the “new” public interface).

(Dean’s issue seems separate, and Joshua has a good suggestion.)

As Dan Michelson noted in this thread, Development Prioritization asked for a 
community specification in order to make a decision about including them in the 
public interface (the associated JIRA - 
https://archivesspace.atlassian.net/browse/ANW-934
 - has been mentioned a few times here).

If folks are interested, the energy here might be well harnessed into working 
on hammering out those details. It would be wonderful to

Re: [Archivesspace_Users_Group] Problem attaching digital objects to resources in ArchivesSpace 3.1.1

2022-06-19 Thread Brian Harrington
Hi Scott,

Double-check your “instance_instance_type” controlled value list, and make sure 
that you have “digital_object” as an option.  ASpace has that hard-coded as the 
instance type for digital objects, but it sometimes gets deleted.  I’m pretty 
sure that’s what happened in your case.

Brian

--
Brian Harrington (he/him)
Data Migration Specialist
LYRASIS
brian.harring...@lyrasis.org


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Scott 
Prater 
Date: Friday, June 17, 2022 at 6:15 PM
To: archivesspace_users_group@lyralists.lyrasis.org 

Subject: [Archivesspace_Users_Group] Problem attaching digital objects to 
resources in ArchivesSpace 3.1.1
Hello,

We have recently begun testing out attaching digital object Instances to our 
resources in ArchivesSpace, version 3.1.1.  So far we have no success:  we can 
create a digital objects, and we can select one and add it to a resource in the 
Resource edit view, but when we then attempt to save the resource, we get the 
unhelpful "Validation Error" message with no other information.  The resource 
is not updated.

I poked around the code, and temporarily disabled the frontend code where 
validation error exceptions are swallowed 
(https://github.com/archivesspace/archivesspace/blob/v3.1.1/frontend/app/controllers/application_controller.rb#L366-L388).
  I then tried to save the resource with the attached digital object again, and 
this time saw the swallowed error:

translation missing: 
validation_errors.protected_read-only_list_#/instances/0/instance_type._invalid_value__digital_object_.__must_be_one_of__box__volume__oversize_folder__reel__audio__disc__film__video__computer_disk__box-folder__reel-frame__side__sc__package__wcftr__roll__map_case__drawer__aa__ab__ac__ad__ae__baa__ca__cb__cc__cd__da__db__dc__dd__de__df__dg__ea__fe__ff__fg__fh__ga__hb__hc__vbb__vbc__vea__vfa__vha__vhb__vhc__oversize_box__folder__fa__electronic__microfilm__ph_box__video_box__dvd__fb__fc__fd__fi__gb__ha__hd__vpa__vta__box__album__ph_box__disc__video__oversize_folder__box-folder__tape__film_box__tape_box__box/folder__audio__vha

It looks like somehow a type is not getting set, or the backend is mistakenly 
requiring a type on the digital object.  There is no place I could see in the 
digital object edit interface where I can select any of those types.  I did 
select a "Moving image" type on my test digital object, but that did not change 
the error.

We've upgraded over the years from ArchivesSpace 2.5.1 to 3.1.1, following the 
upgrade steps for each new release.  Up to now, we haven't had any problems, 
but perhaps something has been left behind from previous versions?  Or a table 
is missing in our latest version?  We are running ArchivesSpace locally on our 
own server;  we have not made any changes to default distributions.

Any help or insight is appreciated (and yes, we did run a full reindex, to no 
avail).

Thanks in advance,

-- Scott

--
Scott Prater
Digital Library Architect
UW Digital Collections Center
University of Wisconsin - Madison


___
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] Issue with searching by identifier in PUI

2022-12-16 Thread Brian Harrington
Hi Jesse,

Just FYI, there’s a JIRA for this issue here:  
https://archivesspace.atlassian.net/browse/ANW-1556

Brian

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Jesse 
Griffis 
Date: Thursday, December 15, 2022 at 2:53 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Issue with searching by identifier in 
PUI
Thanks for the idea. From a quick test it appears that searching by identifier 
requires an exact match and doesn't work with wildcards in 3.3.1. Strangely 
partial matches and wildcards do work in 2.8.0.

Jesse Griffis
Prof. Tech. 2
Systems Development
WVU Libraries

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Joshua 
D. Shaw 
Sent: Thursday, December 15, 2022 2:33 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Issue with searching by identifier in 
PUI

A potential test/workaround would be to replace the ampersand with a wildcard 
'*' in your searches. If that wildcard search works, I think it would confirm 
your idea about the ampersand translation.

jds

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Jesse 
Griffis 
Sent: Thursday, December 15, 2022 2:23 PM
To: archivesspace_users_group@lyralists.lyrasis.org 

Subject: Re: [Archivesspace_Users_Group] Issue with searching by identifier in 
PUI

You don't often get email from jagrif...@mail.wvu.edu. Learn why this is 
important

Thank you for the advice. I believe we waited for the index to finish 
completely, but I will double check that. We are able to find the record 
through regular keyword searches, and in the staff UI we can find it using the 
exact same identifier search term. I have a theory that it may have something 
to do with input sanitization on the PUI side as well as the issue with 
identifier truncation mentioned in 
https://archivesspace.atlassian.net/browse/ANW-1556
 . The identifier in question has an ampersand which gets translated to "&" 
in the PUI search and since that isn't an exact match to the identifier it 
doesn't get returned. I've been trying to figure out a way to fix the ampersand 
issue and test this theory.
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


Re: [Archivesspace_Users_Group] MARC XML import

2023-01-24 Thread Brian Harrington
Hi Sarah,


  1.  The MARCXML importer gets the language from 008/35-37.  I’m not sure what 
happened to it, but the 008 in your record looks short.  Looking at the code, 
if the language positions are blank the language is set to undefined.  But that 
would only work if there are actual blanks in those positions.
  2.  Underneath the error messages, you can see a representation of the JSON 
record that ASpace is trying to load.  If you look at “notes”=>, the first one 
(position 0) has an empty "subnotes"=>[{"jsonmodel_type"=>"note_text"}].  You 
can see this is an odd note with a label of “Publication date”.  In this case, 
ASpace is trying to create a date note from the 260$c, which is blank in your 
case, so the it creates a bad note.  However, it’s only trying to create that 
note because it can’t get the date from the 008.  ASpace only recognizes 008 
dates if 008/06 is an i, k, or s, and you have a q there.  It probably should 
recognize the q, but the quick fix would be to change that to an i or an s.

I hope this helps.

Brian

--
Brian Harrington (he/him)
Data Migration Specialist
LYRASIS
brian.harring...@lyrasis.org


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of 
Newhouse, Sarah 
Date: Monday, January 23, 2023 at 5:05 PM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] MARC XML import
Hi all,

I would really appreciate another set of eyes on these two errors I’m getting 
while testing ingest of MARC XML (resource records) from our library catalog 
into 3.2:


  1.  lang_materials/0/language_and_script/language : Property is required but 
was missing
I’ve tried a few different things here and can’t pinpoint the problem. There 
isn’t a MARC field that maps to this ASpace field in the most recent import 
map<https://docs.google.com/spreadsheets/d/1jU6MYF7UI7a-UKdd5XhYCV6W1UyrMMCzYDFlgb8iNW8/edit#gid=1527709562>
 (unless I’m misreading it, which is entirely possible – it’s been a long day), 
but native ASpace resource records exported as MARCXML will import back in with 
language and script data, so I can tell there is a MARC field that maps to 
this. Based on MARC XML from resource records created in ASpace, I tried adding 
language info in 040$a or 041$b, but neither resulted in a successful import, 
just the same error message. Is there a MARC field I’m missing in the import 
map and/or the ASpace-generated MARC? The Help 
Center<https://archivesspace.atlassian.net/wiki/spaces/ArchivesSpaceUserManual/pages/917405730/Languages+Sub-Record+as+of+v2.7.0>
 does say this field can be imported as MARC XML, but doesn’t say how.
  2.  notes/0/subnotes/0/content : Property is required but was missing

I see that other folks have encountered this error with an index number to 
point them to the note that’s missing content, but lacking one here I’m not 
sure where to start. And looking at my sample files with my fallible human eyes 
I don’t see any empty fields. Has anyone run into this before? Is this just 
pointing at my missing language field?

If there’s a resource or guide I’ve missed – especially for interpreting import 
job errors -- please point me to it! MARC XML is attached (with the added 040 
and 041 fields) in case it’s helpful.

Thank you!

__

Sarah Newhouse   (she, her, hers)
Digital Preservation Archivist
Othmer Library of Chemical History
t. +1.215.873.8249

Science History Institute
Chemistry • Engineering • Life Sciences
315 Chestnut Street • Philadelphia, PA 19106 • U.S.A.
Learn about the scientific discoveries that changed our world at 
sciencehistory.org/learn<https://www.sciencehistory.org/learn>
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


Re: [Archivesspace_Users_Group] Question about OAI harvest of MARCXML records

2023-03-10 Thread Brian Harrington
Hi Andy,

Try set=collection, with no “s”.  I think that’s your problem.

Brian

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Andy 
Boze 
Date: Friday, March 10, 2023 at 2:45 PM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] Question about OAI harvest of MARCXML 
records
Hi, all.

Before I get to the question, let me give some background. We've been
successfully harvesting EAD records from ASpace. We're currently running
v2.8.1 and when we test the harvest on v3.3 we consistently get timeout
problems where sometimes ASpace will simply stop responding or return
some error. Some of our records are very large, but this happens when we
request even relatively small records.

As a work-around, we wanted to try harvesting records in MARCXML format.
It doesn't provide all of the data that are included in the EAD record,
but it's good enough for our purposes.

The problem we have with harvesting records in MARCXML format is that
ASpace returns not only resource records (which are the only records
returned by EAD) but also records for archival objects, which we don't
want. That is, we want records with an identifier of

oai:und//repositories/2/resources/1301

but not

oai:und//repositories/2/archival_objects/673199

When I add set=fonds to the OAI URL, I do get just resources (plus
deleted records), which is pretty much what I would expect, but not all
of our resources are fonds. When I add set=collections, I start getting
archival objects as well as resources. And without specifying a set, I
get a mix of resources and archival objects. (Our harvester also doesn't
allow us to request specific records, just a set and a beginning/ending
date.)

So, my question is: Is there a way to harvest MARCXML records only for
resources?

I hope this makes sense. I've not an archivist, so I hope I'm stating
things adequately.

Andy

--
Andy Boze, Associate Librarian
University of Notre Dame
271H Hesburgh Library
(574) 631-8708
___
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