Re: [Archivesspace_Users_Group] How to display location information under Top Container field?

[Lora Woodford]

Hi Kyle,

That functionality was added in v2.8.1:
https://github.com/archivesspace/archivesspace/releases/tag/v2.8.1. See the
call out for PR #1891:
https://github.com/archivesspace/archivesspace/pull/1891

Best,

Lora

*Lora Woodford (she/her)*
*Software Engineer II *



On Tue, Feb 22, 2022 at 10:54 AM Kyle Breneman  wrote:

> In the ArchivesSpace sandbox, on the staff side of the interface, you can
> see location information for top containers (attached).  Is this simply a
> feature that was added in one of the more recent ArchivesSpace releases, or
> is it an option that we can configure or enable?  We are running version
> 2.8.0.
>
>
>
> *Kyle Breneman*
>
> Integrated Digital Services Librarian
>
> The University of Baltimore
>
> kbrene...@ubalt.edu
>
> *I believe in freedom of thought and *
>
> *freedom of speech. Do 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] Date concatenation

[Lora Woodford]

Hi Scott,

This was the result of a bugfix request that was implemented and delivered as 
part of the 2.8.0 release.  Here’s the JIRA ticket requesting that 
functionality be added to the core of ArchivesSpace: 
https://archivesspace.atlassian.net/browse/ANW-172

It was not implemented as a configurable feature as the ticket described it as 
a bug that should be remedied for all users.  Namely, it was deemed a 
mistake/oversight that only the first of multiple provided dates was being 
added to the display string.

As far as locally changing things on your end by writing a custom plugin, that 
would likely be a fairly major undertaking (that might not ultimately be 
successful) as the change to the display string was made at the model level.  I 
wonder whether anyone else has considered doing that?

Best,

Lora Woodford

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of RENTON 
Scott 
Date: Thursday, June 10, 2021 at 12:26 PM
To: archivesspace_users_group@lyralists.lyrasis.org 

Subject: [Archivesspace_Users_Group] Date concatenation
Hi folks, I posted this one to the Google Group, but nobody took the bait. I 
hope it's ok for me to send to the listserv.

I wondered if anyone knew about configuring the concatenation of dates to 
titles in the frontend and pui? We have noticed since moving to v2.8.1 that 
items with more than one date item are getting multiple dates appended, and the 
curators of these collections find it a bit unwieldy and are asking if we can 
turn it off. In v2.6, they were only getting the first one appended- has there 
been a change to the logic? I couldn't see anything in config which would help 
with this, but I know that if it's in the code any such change will affect the 
whole site, so those curators that like having one date appended may lose that 
functionality.


Thanks
Scott




==

Scott Renton

Digital Library Development & Systems

Floor F East

Argyle House

515219
The University of Edinburgh is a charitable body, registered in Scotland, with 
registration number SC005336. Is e buidheann carthannais a th’ ann an Oilthigh 
Dhùn Èideann, clàraichte an Alba, àireamh clàraidh SC005336.
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Small (?) annoying problem

[Lora Woodford]

Hi Jill,

On the first issue – having to re-search after editing a top container – 
there’s some good news.  The latest release (v2.8.1) includes this 
functionality (generously contributed by developers at Harvard): 
https://github.com/archivesspace/archivesspace/pull/1887  Feel free to test out 
your workflow in the ArchivesSpace sandbox (http://sandbox.archivesspace.org/) 
and, hopefully, it performs as you’d like.  Feedback welcome.

On the second issue, have you tried using the “Bulk Operations” dropdown 
located at the top of the page?  (It’s duplicated on both the top and bottom of 
the page).  I’m not able to replicate the problem you’re seeing here locally 
(v2.8.1, Mac, Chrome), but perhaps you’ll find using the top dropdown to be a 
decent enough work around as you’re completing this work.

Hope that helps.

Lora Woodford

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 

Date: Tuesday, December 1, 2020 at 3:27 PM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] FW: Small (?) annoying problem

Hello all,

I have found something that seems small. Until you are putting container and 
location profiles in for 160 boxes.
If you use the Manage Top Containers section and get your list of boxes, but 
choose to only edit only one, you have to re-search for all those boxes once 
the edit has been saved. My collection has 160 boxes, I find one that is on a 
shelf alone and choose just that one to update. Once I’ve saved, I cannot go 
backwards to my entire list, but must re-search to get it again.

My second small annoying problem is that my screen is not quite big enough 
vertically to see all the drop downs. I will attach an image where I tried to 
update a single location for a number of boxes. I only see the first two 
choices of the dropdown menu. I have done this enough to know to tab down once 
for single and twice for multiple. When I am putting in shelves, this can 
happen too. Say I want to put a box on shelf 6. I will be able to see 1-4 only. 
I use the magic tab down to guess, but sometimes it does not work and I have to 
re-do it several times to get the right shelf.

That was a lot of words. I am updating several hundred locations and 
containers, and I’m getting peeved. Also, I have been kicked out 4 times in the 
last 3 hours, which we haven’t figured out yet. Local IT has helped me check 
this end and I have turned off extensions, etc. But I keep getting kicked out.

Jill


Jill Sweetapple
Pronouns: She/Her/Hers
Head of Archives and Special Collections
American Baptist Historical Society
3001 Mercer University Dr.
Atlanta, GA  30341-4115

(01) 678/547-6680
www.abhsarchives.org<http://www.abhsarchives.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] language plugin implementation 2.7.1

[Lora Woodford]

Hi Ashley,

Wanted to follow up and see if you are still curious about this.  Yes, what 
you’re describing seems normal.  The database migration related to the new 
language/script of description fields in resource records was written to be 
very conservative in terms of deleting existing data from what was previously 
the free text “finding aid language” field.  Indeed, the software specification 
provided for the work (linked to from 
https://archivesspace.atlassian.net/browse/ANW-382) stated that: “REQ-6: The 
system shall migrate existing Language of Description content to the new 
Language of Description Note free-text note field during system migration.”  
The only time it removed/cleaned up data as part of the migration is when 
language/script of description codes were already encoded in the body of that 
free text field.  So, for example, a pre-2.7.1 finding aid language field like:

Description is in English.

Would become the following in 2.7.1+:

Description is in English.

with the appropriate enumeration values for English and Latin provided in the 
new finding_aid_language and finding_aid_script fields in 2.7.1.  The text, 
however, remains.

In your case, it sounds like you had the following in pre-2.7.1:

English

Which, post-migration, resulted in an identical string in the 
finding_aid_language_note:

English

Since no language CODE was provided, nothing was removed or altered and no 
enumeration_ids were added to finding_aid_language and finding_aid_script.  
Since you then went along and ran the plugin to assign languages and scripts to 
your resource records, the default language and script codes that were added 
from the 2.7.1 migration (codes for unknown language/script) were updated to 
the selections you made in the plugin.  The note (as migrated during the 2.7.1 
upgrade process) wouldn’t change from using the plugin.

My understanding is that keeping the former finding_aid_language content in the 
new finding_aid_language_note field is an intentional decision since it is the 
value of that finding_aid_language_note field that is exported into the 
 field in EAD 2002 exports.  (EAD3 exports are handled differently 
and details can be found int eh specification linked to in the ticket above).

If you did really want to wipe away all the “English” entries now in 
finding_aid_language_note that could be done directly in the database (after 
testing thoroughly on a non-production system first!), with a statement along 
the lines of:

UPDATE resource
SET
finding_aid_language_note = REPLACE(finding_aid_language_note,
'English',
null)
WHERE
finding_aid_language_note LIKE 'English';

Just be sure that you are comfortable with the fact that removing these notes 
will remove language information from your EAD 2002 exports (if you use them) 
since the mapping in the specification maps language of description note to 
.

Happy to answer any additional questions.

Best,

Lora

From:  on behalf of 
"Knox, Ashley M." 
Reply-To: Archivesspace Users Group 

Date: Tuesday, September 8, 2020 at 8:01 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] language plugin implementation 2.7.1

I’d like to clarify my earlier post. After migrating from 2.6.0 to 2.7.1, we 
saw the new ‘language of description note’ populated with a language, where it 
was not before the migration. We only had ‘language of description’ populated 
while in 2.6.0. So, my question is just that did anyone else experience this 
when they migrated. Initially, I thought it was purposeful and that one of the 
plugins would rectify it, but that was not the case. We now have ‘language of 
description’ and ‘Script of description’ populated correctly, thanks to the 
plugins. The new and unexpected/unwanted ‘language of description note’ 
remained the same after implementing the plugins.


--earlier post--
We implemented the first two of the three language plugins on a 2.7.1 dev 
instance and for the most part, we got what was expected. What was unexpected 
to us is that in the Finding Aid Data section, Language of description 
(English) became language of description/script of description (English/Latin) 
PLUS language of description note (English). The extra/new lang of desc. note 
feels a little redundant and we are at a loss as to why it appears? Did this 
happen for anyone else? Was this intentional?  Are we missing something obvious?

Ashley

Ashley Knox
Digital Initiatives Librarian
Randall Library
University of North Carolina Wilmington
kn...@uncw.edu
http://library.uncw.edu

Re: [Archivesspace_Users_Group] Dates display problem.

[Lora Woodford]

Just as an additional heads-up, the upgrade to 2.8.0 does *require* a full 
reindex for everything to work properly as noted in the “Configurations and 
Migrations” section of the v2.8.0 Release 
Notes.

Lora

From:  on behalf of 
Kirill Batyuk 
Reply-To: Archivesspace Users Group 

Date: Friday, September 11, 2020 at 3:20 PM
To: 'Archivesspace Users Group' 

Subject: Re: [Archivesspace_Users_Group] Dates display problem.

Thank you everyone. Deleting indexer_state and indexer_pui_state have solved 
the problem.

Kirill

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Blake 
Carver
Sent: Friday, September 11, 2020 3:18 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Dates display problem.

Here's a brief video on Indexing
https://www.youtube.com/watch?v=yFJ6yAaPa3A



From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of Kirill Batyuk mailto:kbat...@whoi.edu>>
Sent: Friday, September 11, 2020 3:07 PM
To: 'Archivesspace Users Group' 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Dates display problem.


Thank you Steven. I will try this solution.



Kirill.



From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 On Behalf Of Majewski, Steven Dennis (sdm7g)
Sent: Friday, September 11, 2020 3:03 PM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Dates display problem.





Saving the record is triggering a reindex of that record, so what you want to 
do is a complete reindex which you can trigger by deleting the files in 
indexer_state and indexer_pui_state.



Sent from my iPhone



On Sep 11, 2020, at 2:57 PM, Carbone, Maura 
mailto:maura.carb...@yale.edu>> wrote:

Hi,



So, I found if you go into a record and re-save it (so edit without changing 
and save), this gets fixed – you can try it on one of yours and see if that 
holds true for you as well. That’s obviously not a solution for thousands of 
records, but not sure if that helps with troubleshooting!



Best,

Maura



From: 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of Kirill Batyuk mailto:kbat...@whoi.edu>>
Reply-To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Date: Friday, September 11, 2020 at 2:45 PM
To: 
"archivesspace_users_group@lyralists.lyrasis.org"
 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] Dates display problem.



Hello,



We have updated to v.2.8.0 today and have run into a problem with the dates 
displayed in staff interface. Instead of the date we get what looks to be JSON 
code, e.g.

{"lock_version"=>0, "expression"=>"1996, 2013", "created_by"=>"bfreiburger", 
"last_modified_by"=>"bfreiburger", "create_time"=>"2019-10-23T15:14:07Z", 
"system_mtime"=>"2019-10-23T15:14:07Z", "user_mtime"=>"2019-10-23T15:14:07Z", 
"date_type"=>"inclusive", "label"=>"creation", "jsonmodel_type"=>"date"}



I’m also attaching a screenshot of what I am seeing.







Would anyone know of a solution to fix this problem?



Thank you,



Kirill Batyuk

Systems Librarian

MBLWHOI Library

Data Library and Archives

Woods Hole Oceanographic Institution

508-289-2850

kbat...@whoi.edu

mblwhoilibrary.org
 --- 
whoi.edu

ORCID



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

Re: [Archivesspace_Users_Group] Changes to PDF export in 2.8?

[Lora Woodford]

And, as soon as I sent this, I found where that repo variable is being set up 
at line 126 of your xsl.  If you move that down into the publicationstmt 
template starting on ln 358 you should be golden.

Lora

From:  on behalf of 
Lora Woodford 
Reply-To: Archivesspace Users Group 

Date: Tuesday, August 18, 2020 at 4:39 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Changes to PDF export in 2.8?

Hi Chris,

I took a quick look at this, and I do think Mark’s instinct is correct.  It 
seems an existing (custom to you folks) function in your xsl isn’t working with 
the recent updates/transition to saxon-rb.

My XSL is pretty rusty these days, but the following lines (ln 364-371) in your 
as-ead-pdf.xsl are the culprits:




Irish Music Archives






The error “The context item for axis step ./ead is absent. Found while 
atomizing the first argument of fn:substring()” points to the fact that the 
transformation no longer knows how to handle the $repo provided as the first 
argument in that substring function.  For what it’s worth, removing this 
customization from your stylesheet (only this customization) results in being 
able to successfully export/print pdfs over here.

I’ll keep poking, but wanted to give you this partial update sooner rather than 
later.

Lora

From:  on behalf of 
Chris Mayo 
Reply-To: Archivesspace Users Group 

Date: Monday, August 17, 2020 at 3:04 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Changes to PDF export in 2.8?

Hi Mark,

Thanks for the suggestion - I hadn't tried yet, but I can successfully run the 
transform outside of Aspace using Oxygen (I don't know how to run XSL from the 
command line). I'm not sure whether that obviates the question about the files, 
but I've attached a sample EAD and the stylesheet (plus a couple of sidecar 
files) here. It sounds like what's going on is that the version of saxon 
bundled into Aspace has gotten stricter, and I'm not sure what to do about 
that. It's fairly important for us to be able to output PDFs directly from the 
application.

Best,
Chris

On Mon, Aug 17, 2020 at 1:49 PM Custer, Mark 
mailto:mark.cus...@yale.edu>> wrote:
Chris,

No clue if it's related or not, but it looks like a gem that's utilized for 
XSLT transformations in ASpace was switched out recently (saxon-xslt -> 
saxon-rb).  I wonder if the new gem (and/or new version of saxon) is more 
strict, and only now throwing an error because of that?

In any event, have you tried running the transformations outside of ASpace?  
Either way, if you can share a sample EAD file that throws the error and a copy 
of the in-house ead-to-pdf stylesheet, I'd be curious to take a look. Not that 
I'm sure I can help, of course :)

Mark



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 Chris Mayo mailto:ma...@bc.edu>>
Sent: Monday, August 17, 2020 1:31 PM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] Changes to PDF export in 2.8?

Hi all,

We keep a modified in-house version of the ead-to-pdf stylesheet so that we can 
put out Finding Aids with our own branding and a few other changes. When we 
recently installed 2.8 on our test server, we discovered that the export to PDF 
job was failing with the following error info:

"The context item for axis step ./ead is absent. Found while atomizing the 
first argument of fn:subst"

Our production server is currently running on 2.6, and we had previously 
updated the test server to 2.7 without that upgrade breaking our stylesheet, so 
the issue appears to have been introduced between 2.7 and 2.8. As far as I can 
tell, the base code for the stylesheet didn't change between those versions, 
and while the error message looks like an Xpath problem, the EAD structure 
doesn't appear to have changed either.

Has anyone else encountered problems with modified finding aid stylesheets in 
2.8, or have any thoughts on what could be causing this error?

Chris

Chris Mayo
Digital Production Librarian
Boston College
chris.m...@bc.edu<mailto:chris.m...@bc.edu>
pronouns: they/them/theirs
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org<mailto:Archivesspace_Users_Group@lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


--
Chris Mayo
Digital Production Librarian
Boston College
chris.m...@bc.edu<mailto:chris.m...@bc.edu>
pronouns: they/them/theirs
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Changes to PDF export in 2.8?

[Lora Woodford]

Hi Chris,

I took a quick look at this, and I do think Mark’s instinct is correct.  It 
seems an existing (custom to you folks) function in your xsl isn’t working with 
the recent updates/transition to saxon-rb.

My XSL is pretty rusty these days, but the following lines (ln 364-371) in your 
as-ead-pdf.xsl are the culprits:



Irish Music Archives






The error “The context item for axis step ./ead is absent. Found while 
atomizing the first argument of fn:substring()” points to the fact that the 
transformation no longer knows how to handle the $repo provided as the first 
argument in that substring function.  For what it’s worth, removing this 
customization from your stylesheet (only this customization) results in being 
able to successfully export/print pdfs over here.

I’ll keep poking, but wanted to give you this partial update sooner rather than 
later.

Lora

From:  on behalf of 
Chris Mayo 
Reply-To: Archivesspace Users Group 

Date: Monday, August 17, 2020 at 3:04 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Changes to PDF export in 2.8?

Hi Mark,

Thanks for the suggestion - I hadn't tried yet, but I can successfully run the 
transform outside of Aspace using Oxygen (I don't know how to run XSL from the 
command line). I'm not sure whether that obviates the question about the files, 
but I've attached a sample EAD and the stylesheet (plus a couple of sidecar 
files) here. It sounds like what's going on is that the version of saxon 
bundled into Aspace has gotten stricter, and I'm not sure what to do about 
that. It's fairly important for us to be able to output PDFs directly from the 
application.

Best,
Chris

On Mon, Aug 17, 2020 at 1:49 PM Custer, Mark 
mailto:mark.cus...@yale.edu>> wrote:
Chris,

No clue if it's related or not, but it looks like a gem that's utilized for 
XSLT transformations in ASpace was switched out recently (saxon-xslt -> 
saxon-rb).  I wonder if the new gem (and/or new version of saxon) is more 
strict, and only now throwing an error because of that?

In any event, have you tried running the transformations outside of ASpace?  
Either way, if you can share a sample EAD file that throws the error and a copy 
of the in-house ead-to-pdf stylesheet, I'd be curious to take a look. Not that 
I'm sure I can help, of course :)

Mark



From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of Chris Mayo mailto:ma...@bc.edu>>
Sent: Monday, August 17, 2020 1:31 PM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] Changes to PDF export in 2.8?

Hi all,

We keep a modified in-house version of the ead-to-pdf stylesheet so that we can 
put out Finding Aids with our own branding and a few other changes. When we 
recently installed 2.8 on our test server, we discovered that the export to PDF 
job was failing with the following error info:

"The context item for axis step ./ead is absent. Found while atomizing the 
first argument of fn:subst"

Our production server is currently running on 2.6, and we had previously 
updated the test server to 2.7 without that upgrade breaking our stylesheet, so 
the issue appears to have been introduced between 2.7 and 2.8. As far as I can 
tell, the base code for the stylesheet didn't change between those versions, 
and while the error message looks like an Xpath problem, the EAD structure 
doesn't appear to have changed either.

Has anyone else encountered problems with modified finding aid stylesheets in 
2.8, or have any thoughts on what could be causing this error?

Chris

Chris Mayo
Digital Production Librarian
Boston College
chris.m...@bc.edu
pronouns: they/them/theirs
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


--
Chris Mayo
Digital Production Librarian
Boston College
chris.m...@bc.edu
pronouns: they/them/theirs
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] ASpace upgrade: "Connection to backend failed"

[Lora Woodford]

Hiya Mark!

So, if the issue were a db schema mismatch, you’d likely get an error message 
explaining that.  Something like “Schema Info Mismatch. Expected #{expected 
schema version}, received #{your schema version} for ASPACE version #{version 
you’re trying to run}.”

What version of mysql (if mysql?) are you using?  I’ve seen similar issues with 
folks attempting to run against MySql 8.  Can you try 5.7?

Lora

From:  on behalf of 
Mark Cyzyk 
Reply-To: "mcy...@jhu.edu" , Archivesspace Users Group 

Date: Monday, July 27, 2020 at 10:55 AM
To: "archivesspace_users_group@lyralists.lyrasis.org" 

Subject: [Archivesspace_Users_Group] ASpace upgrade: "Connection to backend 
failed"


All,

I'm trying to practice upgrading ASpace (2.5.1 --> 2.8.0) in a Vagrant box 
before upgrading for real.

I was having problems running the /scripts/database-setup.sh migration script 
via my Vagrant file, and, as with Vagrant, Ansible, etc. found myself spending 
lots of time troubleshooting the script I've written to install the software, 
when I could have just installed the software!

So now I have my Vagrant box up and running, I SSH in and run 
/scripts/database-setup.sh without any problem.

BUT now that I've kicked this can down the road, the next issue is:

When I go to boot up ASpace, I end up with the following error:
INFO: DEBUG: resetting rack response due exception
E, [2020-07-25T15:57:06.898049 #38438] ERROR -- : Thread-2004: Connection to 
backend failed (http://www.w3.org/TR/html4/loose.dtd;>

I read that if the schema in the DB does not match the schema in the ASpace 
codebase, the backend will not start.

And yet, the setup-database.sh migration script ran without error, so at this 
point the schemas should be in sync.

Any advice on how to get the backend up and running greatly appreciated,

Mark


--

<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>

Mark Cyzyk, M.A., M.L.S.

Library Applications Group

The Sheridan Libraries

The Johns Hopkins University

mcy...@jhu.edu



Verba volant, scripta manent.
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Need help with API advanced query

[Lora Woodford]

Hi Andy,

When you're sending a search query along as your request using the search 
endpoints you're actually hitting the SOLR index and need to pass along the 
SOLR document fields.  This can be somewhat confusing, because what is returned 
to you is the JSON representation of the object(s) you queried for, but the 
query itself utilizes the field names in the index.

So, you'll likely want the following for your example:

{
"query": {
"op": "AND",
"subqueries": [
{
"field": "primary_type",
"value": "top_container",
"comparator": "equals",
"jsonmodel_type": "field_query"
},
{
"field": "barcode_u_sstr",
"value": "BC98765",
"comparator": "equals",
"jsonmodel_type": "field_query"
}
],
"jsonmodel_type": "boolean_query"
},
"jsonmodel_type": "advanced_query"
}

By looking in indexer_common.rb in the source code 
(https://github.com/archivesspace/archivesspace/blob/master/indexer/app/lib/indexer_common.rb#L631)
 , you can see where the top container "barcode" field becomes the 
"barcode_u_sstr" field in the resulting SOLR document.

Hope that helps, and happy to follow up with additional questions.

Lora

 
On 5/28/20, 3:20 AM, "archivesspace_users_group-boun...@lyralists.lyrasis.org 
on behalf of Andy Boze" 
 wrote:

Dear all,

I'm using curl from the Windows 10 command line to retrieve JSON data 
from our instance of AS. For the most part it's working well. I followed 
some of the discussion from a few months ago which was very helpful in 
figuring out how to use the advanced query, but I've reached a point 
where I'm stuck.

I can successfully send a query with the following string to get a 
record for a resource with the identifier "ABC". I've formatted it here 
so it's easier to read.

{
"query": {
"op": "AND",
"subqueries": [
{
"field": "primary_type",
"value": "resource",
"comparator": "equals",
"jsonmodel_type": "field_query"
},
{
"field": "identifier",
"value": "ABC",
"comparator": "equals",
"jsonmodel_type": "field_query"
}
],
"jsonmodel_type": "boolean_query"
},
"jsonmodel_type": "advanced_query"
}

What I'm trying to do is get a record for a top_container with a barcode 
of BC98765 by sending a query with this string.

{
"query": {
"op": "AND",
"subqueries": [
{
"field": "jsonmodel_type",
"value": "top_container",
"comparator": "equals",
"jsonmodel_type": "field_query"
},
{
"field": "barcode",
"value": "BC98765",
"comparator": "equals",
"jsonmodel_type": "field_query"
}
],
"jsonmodel_type": "boolean_query"
},
"jsonmodel_type": "advanced_query"
}

When I send the above query, I get no response, not even an error 
message. I'm thinking jsonmodel_type is not a field that I should query, 
but when I requested the specific top_container record 
(/repositories/2/top_containers/56484) there was no other field with a 
value of top_container.

I'd appreciate any advice how to request a record for a top_container by 
barcode.

Thanks.

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

Re: [Archivesspace_Users_Group] API question about digital objects and components

[Lora Woodford]

Hi Wendy,

Something like this should get you what you’re after (this should return all 
digital object components linked to the digital_objects/1 in repository 2):

http://your.base.api.url/search?page=1={"query": {"jsonmodel_type": 
"boolean_query","op": "AND","subqueries": [{"field": "primary_type","value": 
"digital_object_component","jsonmodel_type": "field_query","negated": 
false,"literal": true}, {"field": "digital_object","value": 
"/repositories/2/digital_objects/1","jsonmodel_type": "field_query","negated": 
false,"literal": true}]}}

Best,

Lora Woodford


From:  on behalf of 
"Hagenmaier, Wendy L" 
Reply-To: Archivesspace Users Group 

Date: Friday, April 10, 2020 at 2:44 PM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] API question about digital objects and 
components

Hi ASpace community,

We're working on a project using the API and have a question about digital 
object components. We've looked through the API documentation on GitHub and 
can't quite find what we're after, but maybe we've missed it.

Can anyone help us with a method for getting digital object component fields 
using the parent digital object ID (and without knowing the digital object 
component ID)?

Thank you,
Wendy

Wendy Hagenmaier
Digital Collections Archivist
Archives & Records Management
Georgia Institute of Technology Library
Atlanta, GA 30332-0900
wendy.hagenma...@library.gatech.edu
(404) 894-4579
Pronouns: she/her/hers
library.gatech.edu/archives<http://library.gatech.edu/archives/>
<http://library.gatech.edu/retrotech>
library.gatech.edu/retrotech<http://library.gatech.edu/retrotech>
___
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 - unpublished check box

[Lora Woodford]

Hi Nancy,

I know of at least one existing plugin out there that modifies export behavior 
(and there may be others).  Take a look at: 
https://github.com/duke-libraries/archivesspace-duke-export-option-defaults  
You should be able to customize this to your wishes by adding/removing the 
checked attributes in the html template.

Best,

Lora

From:  on behalf of 
"Kennedy, Nancy" 
Reply-To: Archivesspace Users Group 

Date: Thursday, February 6, 2020 at 12:30 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Generate PDF - unpublished check box

Thanks, Andrew.  Figured that might be the case!  And, yes, internal notes are 
the main concern.


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Andrew 
Morrison
Sent: Thursday, February 6, 2020 6:05 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Generate PDF - unpublished check box

External Email - Exercise Caution
The  "Include unpublished" checkbox is hardcoded to always be selected.

It would be possible to create a plug-in to change that behaviour. But it seems 
like the sort of thing that ideally would be configurable via group 
permissions, and/or per repository, and that would be an enhancement to the 
core system.

Presumably your concern is over including unpublished notes, because entire 
archival objects and resources can be suppressed, and those are not supposed to 
be included when exporting, regardless of the status of the checkbox.

Andrew.


On Wed, 2020-02-05 at 21:49 +, Kennedy, Nancy wrote:
Hello all!
After upgrading to 2.6, we’ve noticed that the Generate PDF button has an 
“include unpublished” check box that is automatically opt-in.

Is there a way to configure our ArchivesSpace so that a staff member has to 
explicitly check the “include unpublished” check box?  We don’t want someone 
inadvertently skipping past that checkbox and printing out PDFs with internal 
information.


Thanks,
Nancy


Nancy Kennedy
Smithsonian Institution
kenne...@si.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] Suppressed record search bug

[Lora Woodford]

Heya Kevin,

Thanks for bringing this up.  I took a quick look at the code, and I see what’s 
going on here.  I’m going to put in a pull request later today to hopefully 
patch this in the upcoming release.  That “found in” column was one of the 
first feature enhancements I tackled, so I’m afraid there are some edge cases 
(such as what to do in instances of suppressed records) that I just didn’t 
consider/test out, and our pre-release testing didn’t catch it either.  If you 
have the ability/are able to test this out before it makes it to an official 
release, I’m happy to send you a build with this fix in it to test out locally. 
 Feel free to reach out off-list if you’d like.

Best,

Lora

From:  on behalf of 
Kevin Clair 
Reply-To: Archivesspace Users Group 

Date: Thursday, April 25, 2019 at 12:37 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Suppressed record search bug

We’re on 2.5.2 now. We upgraded because of that bug; that’s why I thought the 
problem could be with the event record instead of the resource.  -k

From:  on behalf of 
Blake Carver 
Reply-To: Archivesspace Group 
Date: Thursday, April 25, 2019 at 10:28 AM
To: Archivesspace Group 
Subject: Re: [Archivesspace_Users_Group] Suppressed record search bug

What version are you on? That looks similar to a bug that should've been fixed 
in 2.5.2.

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Kevin 
Clair 
Sent: Thursday, April 25, 2019 12:08 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Suppressed record search bug


I should also say that the search that prompted this also returns a 
component_transfer event of records that were moved from the suppressed 
Resource to another Resource. So it may be that it’s an issue with suppressed 
records appearing in the “Found In” column of another record’s result summary, 
rather than with the suppressed record itself…  -k



From:  on behalf of 
Kevin Clair 
Reply-To: Archivesspace Group 
Date: Thursday, April 25, 2019 at 10:00 AM
To: Archivesspace Group 
Subject: [Archivesspace_Users_Group] Suppressed record search bug



Hello,



We recently discovered an issue with searching for records that are suppressed 
in the staff interface. In our instance, administrative users are able to do 
known-item searches for suppressed records without incident; if a user without 
administrative permissions performs the same search, they get thrown an error 
with the following stack trace:



I, [2019-04-25T09:47:26.038804 #18125]  INFO -- : Completed 500 Internal Server 
Error in 1163ms

F, [2019-04-25T09:47:26.041948 #18125] FATAL -- :

F, [2019-04-25T09:47:26.042069 #18125] FATAL -- : ActionView::Template::Error 
(undefined method `[]' for nil:NilClass):

F, [2019-04-25T09:47:26.042263 #18125] FATAL -- : 1: <% ancestors = 
context_ancestor(result) %>

2: <% if ancestors != nil && ancestors != [''] %>

3:   <% ancestors.reverse.each_with_index do |ancestor, i| %>

4: <%= 
resolve_readonly_link_to((get_ancestor_title(ancestor).html_safe), ancestor) %>

5: <% if i < ancestors.length - 1 %>

6:   <%= context_separator(result) %>

7: <% end %>

F, [2019-04-25T09:47:26.042340 #18125] FATAL -- :

F, [2019-04-25T09:47:26.042413 #18125] FATAL -- : 
app/helpers/search_helper.rb:198:in `get_ancestor_title'

app/views/search/_context.html.erb:4:in `block in 
_app_views_search__context_html_erb___234296763_2752'

app/views/search/_context.html.erb:3:in 
`_app_views_search__context_html_erb___234296763_2752'

app/helpers/application_helper.rb:289:in `render_aspace_partial'

app/views/search/_listing.html.erb:90:in `block in 
_app_views_search__listing_html_erb___1981573825_2748'

app/views/search/_listing.html.erb:52:in 
`_app_views_search__listing_html_erb___1981573825_2748'

app/helpers/application_helper.rb:289:in `render_aspace_partial'

app/views/search/_results.html.erb:23:in 
`_app_views_search__results_html_erb___1135689531_2744'

app/helpers/application_helper.rb:289:in `render_aspace_partial'

app/views/search/do_search.html.erb:16:in 
`_app_views_search_do_search_html_erb__585907251_2742'



Checking in to see if anyone else has noticed similar behavior and if there’s a 
bug report for this in Jira already. I did a quick search just now but couldn’t 
find anything that looked similar to this. thanks!  -k
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Importing Accessions CSVs - linking agents and resources

[Lora Woodford]

Hi Carly,

The current accessions CSV import is limited to the columns that exist in the 
csv template, and, as such, does not support the type of workflow you describe. 
 Rightly or wrongly, it definitely assumes that you are using the CSV importer 
to import wholly new records and new linked/associated records (in the case of 
subjects and agents, at least).  It does not support importing classifications 
and links to related resources.

I’ve done very little with the csv imports so I’m not sure how difficult it 
would be to extend the functionality to accomplish what you want, but would 
encourage anyone to chime in here with advice if you have done so (or attempted 
to do so and scrapped the idea!).  Given the fact that I haven’t seen any 
examples of folks doing this work (correct me if I’m wrong!), I suspect it is 
rather tricky.

There are many more examples out there of folks associating existing linked 
records to one another using the ArchivesSpace API.  A great resource to start 
learning how this project might be accomplished using the API is the 
ArchivesSnake repository in GitHub (a readme begins after you scroll past that 
list of files):  https://github.com/archivesspace-labs/ArchivesSnake

 Hopefully others will chime in with additional advice.

Best,

Lora

From:  on behalf of 
"Bogen, Carly (Records)" 
Reply-To: Archivesspace Users Group 

Date: Saturday, November 17, 2018 at 12:13 PM
To: "archivesspace_users_group@lyralists.lyrasis.org" 

Subject: [Archivesspace_Users_Group] Importing Accessions CSVs - linking agents 
and resources

Hi all,

Is there a way to use the accessions CSV import to link the new accession being 
created to agents, resources and classifications that already exist in the 
repository?

We'd like to be able to add an existing agent uid to a field in the 
spreadsheet, include a role, and have that automatically link. Same for 
resources and classifications, only without the role.

I can't seem to figure out how to make this work.

Thanks for your help! And sorry for the cross-post – this list seems a bit more 
active than the Google group.

-Carly

Carly Bogen | Manager, Digital Programs
Department of Records and Information Services (DORIS)
31 Chambers Street, New York, NY 10007
P: 212-341-6029  | E-mail: cbo...@records.nyc.gov
[mailBanner]
Follow us on:
[acebook]  [witter] 
   [umblr] 
[outube] 


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

Re: [Archivesspace_Users_Group] Linking related accessions below collection level

[Lora Woodford]

I did this (when that granular level of linkage was warranted) at my former 
institution by creating a “processed” event record from the accession record 
that linked to the resulting archival object (which can be most easily found by 
typing the archival object’s URI into the type ahead box under linked records). 
 We did this infrequently, but it was helpful when we wanted to find just that 
one particular copy of a circular (of which we may have had many copies in an 
artificial collection) that was donated by a VIP.  But, yes, events do allow 
you to link from accession records to archival object records, and vice versa.

Lora

--
Lora J. Woodford
The Sheridan Libraries
Johns Hopkins University
3400 North Charles Street
Baltimore, MD 21228
(410) 516-5898
lwoodf...@jhu.edu

From:  on behalf of 
Kevin Clair 
Reply-To: Archivesspace Users Group 

Date: Tuesday, November 28, 2017 at 12:14 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Linking related accessions below 
collection level

Hello,

We would also be interested in this; it’s one of the features we lost in 
migrating from our last system (besides batch editing) that gets requested the 
most. We’re currently capturing this information in the Disposition Note of 
each Accession record, but we would definitely like to link to accessioned 
materials more directly than just at the Resource level.  -k

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Jordon Steele
Sent: Tuesday, November 28, 2017 9:57 AM
To: Archivesspace Users Group
Subject: [Archivesspace_Users_Group] Linking related accessions below 
collection level

Hi all,

We have an interest in linking archival objects (i.e. the levels below 
collection level) in resource records back to the accessions they came from. 
The situation that precipitated discussion about this possibility was that we 
have one series of materials that is associated with multiple accession records.

Unless I’m missing something, the only way one can currently link to accessions 
from resource records is at the collection level. There is no “Related 
accessions” feature at levels below that.

The way we’re doing this now is creating an accruals note at the appropriate 
level and typing the accession number into the free text field, but having a 
direct link between the two would be handy. For born-digital collections, we 
are also linking the original containers from which the digital content came to 
the appropriate level in the resource record using the instance module.

I’m wondering if others in the community have discussed or considered this 
before.

Thanks!

Best,

Jordon

Jordon Steele
Hodson Curator of the University Archives
Special Collections
The Sheridan Libraries
Johns Hopkins University
3400 N Charles St
Baltimore, MD 21218
410-516-5493
jste...@jhu.edu

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

Re: [Archivesspace_Users_Group] batch delete dates saga continues

[Lora Woodford]

Hey and thanks for the plug, Patrick!

My co-workshop lead, Valerie Addonizio, and I tried to make the resources we 
put up in that GitHub stand on their own without the in-person part of the 
workshop.  It was really important to us that everyone – not just those able to 
get to and pay for a 1-day workshop – be able to tinker about.  As Patrick has 
said, tinkering is the BEST way to learn.  It’s certainly how I did.  If anyone 
wants assistance in working through these workshop materials, definitely give a 
shout.  Like all of the rest of you, I have a super busy day job, but I’m happy 
to help as time allows!

Regarding the time to do this, everyone’s situation is going to be different, 
but if your institution supports the idea of professional development 
time/personal goals, it can be a good idea to talk about this with supervisors 
and make it an articulated part of your job.  Last year my “personal goal” was 
to increase my proficiency with Rails, so I tried to set aside an hour or so 
every couple weeks to dedicate myself to that, in the same way that I try to 
stay on top of the literature in ours and allied fields. Your learning style 
may vary, but I find it is best to just set aside a little bit of time over a 
long period, rather than trying to “cram” everything at once. Approach it as 
you would approach learning a foreign language. You aren’t going to do it in 
one weekend, one month, or, even, one year. It will grow naturally over time as 
you expose yourself to it. There are SO MANY wonderful resources out there 
(most for free), and you’ve got a community of folks who can help connect you 
to them. I won’t go too much into specifics as my answers will vary depending 
on what you want to do/what your specific setup looks like, but Code Academy, 
Lynda.com, the Hitchhiker’s Guide to Python 
(http://docs.python-guide.org/en/latest/), and some of the “better” coding boot 
camps (https://www.switchup.org/research/best-coding-bootcamps) offer free 
online courses (but, be forewarned, if you sign up with one of them they WILL 
hound you to apply to their programs and actively try and recruit you to their 
school ;-) ).

Good luck, all,

Lora

--
Lora J. Woodford
The Sheridan Libraries
Johns Hopkins University
3400 North Charles Street
Baltimore, MD 21228
(410) 516-5898
lwoodf...@jhu.edu<mailto:lwoodf...@jhu.edu>

From: <archivesspace_users_group-boun...@lyralists.lyrasis.org> on behalf of 
"Galligan, Patrick" <pgalli...@rockarch.org>
Reply-To: Archivesspace Users Group 
<archivesspace_users_group@lyralists.lyrasis.org>
Date: Monday, November 13, 2017 at 9:52 AM
To: Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] batch delete dates saga continues

Hey all,

I think a great place to get started learning about Python, APIs, and 
ArchivesSpace would be some of the API tutorials that members of the 
ArchivesSpace community have taught.

Lora Woodford from JHU taught a workshop about 4 months ago and made the 
materials available on Github: 
https://github.com/jhu-archives-and-manuscripts/ASpace_API_Workshop.

Personally, I’ve found that I learn best by doing. So I learned what I did 
about the AS JSON responses by downloading Postman 
(https://www.getpostman.com/) and performing a few API calls against our 
development database. Also, back in 2014, Maureen Callahan and a few other 
archivists ran a blog about dealing with legacy data. They have some posts 
about AS API work. I personally liked this post as a beginner: 
https://icantiemyownshoes.wordpress.com/2014/08/01/a-very-brief-guide-to-deleting-records-with-the-archivesspace-api-from-a-total-tyro/.

This is a great resource for learning python: 
https://automatetheboringstuff.com/.

I’m sure there are a ton of other resources out there, but those are the few 
off the top of my head. I’m willing to jump in and give some more 
recommendations as needed.

-Patrick Galligan

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Margaret Kidd
Sent: Friday, November 10, 2017 5:31 PM
To: Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] batch delete dates saga continues

I second that last part of Lydia's remarks about where to begin learning more 
about XML, JSON, python, ruby, etc. and applying it to ArchivesSpace. I want to 
learn, but it is overwhelming to know where to begin and my time to devote to 
it is rather limited. Every time I start trying to teach myself I have other 
work priorities that take up all my time and soon forget whatever progress I 
have made.

Thanks,

Margaret




Margaret T. Kidd

Project Archivist, Special Collections & Archives

VCU Libraries | Tompkins-McCaw Library for the Health Sciences

509 N. 12th Street / B

Re: [Archivesspace_Users_Group] Python ArchivesSpace scripting library

[Lora Woodford]

+1 here.  And I can confirm that Greg said out loud in Portland, “I have the 
time and freedom to do this, so I’m happy to spend some time on it.”  :-p

Lora (with less time and freedom, but eager to help how she can)


Lora J. Woodford
Digital Archivist
The Sheridan Libraries
Johns Hopkins University
3400 North Charles Street
Baltimore, MD 21228
(410) 516-5898
lwoodf...@jhu.edu



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Mayo, Dave
Sent: Thursday, August 03, 2017 9:48 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Python ArchivesSpace scripting library

One thing I think might be useful, especially in planning stages, is collecting 
the “prior art” in one place to look at – because there are a lot of scripts 
people have built around the API, and they probably capture at least a fair bit 
of “what people want to do most with the API.”

So, whenever the github is set up, we should do this.

- Dave

From: 
>
 on behalf of "rsdo...@caltech.edu" 
>
Reply-To: "rsdo...@caltech.edu" 
>, Archivesspace Users Group 
>
Date: Thursday, August 3, 2017 at 9:21 AM
To: Archivesspace Users Group 
>
Subject: Re: [Archivesspace_Users_Group] Python ArchivesSpace scripting library

Hello Patrick,

I have written some tools in go and mocked up functionaity in Python a few 
years ago I'd be interested in the project.

Robert Doiel
Caltech Library
rsdo...@caltech.edu

On Aug 3, 2017 6:10 AM, "Galligan, Patrick" 
> wrote:
Hi all,

For a while now the RAC has been bouncing around the idea of developing an AS 
Python library that would hold a lot of the functions we find ourselves working 
with a lot when scripting against the AS API. I know Greg Wiedeman at U Albany 
has done some work to this end, but I wanted to send a blast out to the list to 
see who else might be interested. We’d love to make this as collaborative and 
exhaustive as possible so that we can cover the most bases.

I’m thinking of setting up a Github project that we can collaboratively work 
in. Anyone have better ideas?

Let me know.

Thanks,
Patrick Galligan
Rockefeller Archive Center

___
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