From bobbi_fox at harvard.edu  Mon Oct  2 16:03:57 2017
From: bobbi_fox at harvard.edu (Fox, Bobbi)
Date: Mon, 2 Oct 2017 20:03:57 +0000
Subject: [Archivesspace_Users_Group] Running the
	(development)	PUI	on	a	separate server?
In-Reply-To: <DM5PR13MB172104BD3FEAA9095C2DDA378F7E0@DM5PR13MB1721.namprd13.prod.outlook.com>
References: <BN6PR07MB3492917B4DDF0FDB1345DB03907E0@BN6PR07MB3492.namprd07.prod.outlook.com>,
 <DM5PR13MB17210F26B6E01526217F94E08F7E0@DM5PR13MB1721.namprd13.prod.outlook.com>,
 <DM5PR13MB17218E714B3868FA75B4593B8F7E0@DM5PR13MB1721.namprd13.prod.outlook.com>
 <DM5PR13MB172104BD3FEAA9095C2DDA378F7E0@DM5PR13MB1721.namprd13.prod.outlook.com>
Message-ID: <BN6PR07MB34923687A5FE458A67FB6342907D0@BN6PR07MB3492.namprd07.prod.outlook.com>


Hi, all,

Using these instructions, I was able to get it to work!  Note that, while I pointed to the external (to my dev environment) solr server, it really isn't necessary, since the PUI solr requests are funneled through the back en.

At some point, I'll make the build/build.xml more flexible (to accommodate this) and do a pull request, but that's in the future.

I also will be looking (in the future, not now) at being able to host the Public UI on a separate server for reals.

Thanks again!

Cheers,
Bobbi


From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven Dennis (sdm7g)
Sent: Friday, September 29, 2017 5:34 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Running the (development) PUI on a separate server?


OK: This seems to work for me:



In the public:devserver target of build/build.xml:

  change -Daspace.config.backend_url=  to point to the remote backend server.



Solr URL  and public_user_secret are set in default_java_options property near the head of that file.

It looks like those can also be set from a JAVA_OPTS environment variable.

Solr URL should point to the remote solr server, and public_user_secret needs to be set to the same value for both local devserver and in AppConfig[:public_user_secret] on the remote server. Otherwise, you'll get login failures from the local public app being unable to log into the remote backend.



With those settings, it appears to be working for me, but I haven't exhaustively tested it.



-- Steve Majewski / UVA Alderman Library
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Majewski, Steven Dennis (sdm7g) <sdm7g at virginia.edu<mailto:sdm7g at virginia.edu>>
Sent: Friday, September 29, 2017 4:09:56 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Running the (development) PUI on a separate server?


Oops: Sorry. I wasn't thinking correctly about running dev mode.



The URLs except for the ports are hardwired in build.xml.

Looks like it only needs itself and backend URLs.  ( No solr ? )





 <target name="public:devserver" depends="set-classpath, public:clean, public:copy-shared-resources" description="Start an instance of the ArchivesSpacePublic development server">

    <java classpath="${jruby_classpath}" classname="org.jruby.Main" fork="true" failonerror="true"

          dir="../public">

      <jvmarg line="-Daspace.service=public -Daspace.config.backend_url=http://localhost:${aspace.backend.port}/ -Daspace.config.public_url=http://localhost:${aspace.public.port}/ ${default_java_options} ${env.JAVA_OPTS}"/>

      <env key="GEM_HOME" value="${gem_home}" />

      <env key="GEM_PATH" value="" />

      <env key="BUNDLE_PATH" value="${gem_home}" />

      <env key="ASPACE_INTEGRATION" value="${aspace.integration}" />

      <arg line="bin/rails s mizuno -b 0.0.0.0 --port=${aspace.public.port}" />

    </java>

  </target>



-- Steve Majewski / UVA Alderman Library
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Majewski, Steven Dennis (sdm7g) <sdm7g at virginia.edu<mailto:sdm7g at virginia.edu>>
Sent: Friday, September 29, 2017 3:57:09 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Running the (development) PUI on a separate server?


I haven't tried it (yet) but I'm guessing that you just have to set AppConfig[:enable_*] for all but :enable_public to false, and redirect all of the "http://localhost:port" default settings for AppConfig[:*_url] to point to the remote counterparts. You might also need to set AppConfig[:frontend_proxy_url]



That should (in theory) get you a configuration with only public server running, talking to backend, solr and frontend on remote server.





-- Steve Majewski / UVA Alderman Library
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Fox, Bobbi <bobbi_fox at harvard.edu<mailto:bobbi_fox at harvard.edu>>
Sent: Friday, September 29, 2017 2:14:58 PM
To: Archivesspace Users Group
Subject: [Archivesspace_Users_Group] Running the (development) PUI on a separate server?

Hi,

I'm working on customizing the PUI for our institution, working in development mode, and, rather than cloning off our humongous, takes-2+-days to index database (which I need to do, because my "product owner" is a committee made up of picky(yeah, that's redundant) Archivists :-) , I was hoping to point to the backend of our V2.1.* QA system already running.

Has anyone tried this?  What incredible munging of the build.xml am I likely to need to do?

Thanks,
Bobbi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171002/1473bb67/attachment.html>

From cpeterson at smith.edu  Mon Oct  2 16:57:47 2017
From: cpeterson at smith.edu (Christie Peterson)
Date: Mon, 02 Oct 2017 20:57:47 +0000
Subject: [Archivesspace_Users_Group] Tool tips and software updates
Message-ID: <CAFy-AYL69nRXQkTR7D2ZyaAP9hWO=5AwccfJfDJz+d5+Y_V_og@mail.gmail.com>

Hello everyone,

If we invest time into customizing tool tips, will our local changes be
retained with ASpace software updates? We're hosting with Lyrasis, if this
makes a difference.

Thanks,

Christie Peterson
-- 
?
Christie S. Peterson

Head of Technical Services for Special Collections
Smith College
Northampton, Mass.
413-585-2996
cpeterson at smith.edu

pronouns: she/her/hers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171002/ce9f4b52/attachment.html>

From lwoodford at jhu.edu  Mon Oct  2 17:08:36 2017
From: lwoodford at jhu.edu (Lora Woodford)
Date: Mon, 2 Oct 2017 21:08:36 +0000
Subject: [Archivesspace_Users_Group] Tool tips and software updates
In-Reply-To: <CAFy-AYL69nRXQkTR7D2ZyaAP9hWO=5AwccfJfDJz+d5+Y_V_og@mail.gmail.com>
References: <CAFy-AYL69nRXQkTR7D2ZyaAP9hWO=5AwccfJfDJz+d5+Y_V_og@mail.gmail.com>
Message-ID: <0899b2c1670a437a9ebaa397f9afe7b3@ESGEBEX8.win.ad.jhu.edu>

Hey Christie,

As long as you make your changes in a local plugin (see: http://archivesspace.github.io/archivesspace/user/customizing-and-theming-archivesspace/) and then have that plugin (and the config that points to it) moved forward through your upgrades, you shouldn?t lose this work.  We haven?t done anything with tooltips, but here?s an example of how we handle label/enum changes via a plugin: https://github.com/jhu-archives-and-manuscripts/jhu-local-plugins  If you start building out many plugins (even just label changes) be aware that they are loaded in the order they are listed in your config.rb!

Happy to help with any specific questions you might have.

Best,

Lora

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



From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Christie Peterson
Sent: Monday, October 02, 2017 4:58 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Tool tips and software updates

Hello everyone,

If we invest time into customizing tool tips, will our local changes be retained with ASpace software updates? We're hosting with Lyrasis, if this makes a difference.

Thanks,

Christie Peterson
--
?
Christie S. Peterson

Head of Technical Services for Special Collections
Smith College
Northampton, Mass.
413-585-2996
cpeterson at smith.edu<mailto:cpeterson at smith.edu>

pronouns: she/her/hers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171002/dc58a5bc/attachment.html>

From s.innes at auckland.ac.nz  Tue Oct  3 02:36:10 2017
From: s.innes at auckland.ac.nz (Stephen Innes)
Date: Tue, 3 Oct 2017 06:36:10 +0000
Subject: [Archivesspace_Users_Group] Digital objects in v2.1.1
Message-ID: <5a46855b749e4b7c972511053706b3ba@uxcn13-ogg-c.UoA.auckland.ac.nz>

We are currently upgrading to v2.1.1 and ironing out various issues. Currently digital object records are appearing as invalid with the message ?translation missing: en.no key - Property is required but was missing?. This appears to be related to the ?Other level? value not being properly defined in the backend (see attached screenshot).

Can someone help us resolve this issue?  The links worked fine in the previous version of AS we were using, (v1.4.2).

Thank you,

Stephen Innes

Stephen Innes (ALIANZA)
Special Collections Manager
General Library, Te Herenga M?tauranga Wh?nui
The University of Auckland
Private Bag 92019
Auckland 1142
New Zealand
Telephone (649) 373-7599 ext. 88062 | Fax (649) 373-7565
Website: http://www.library.auckland.ac.nz/about-us/collections/special-collections/general-library
Online exhibition: Special Collections First World War Centenary 2014-2018<http://www.specialcollections.auckland.ac.nz/ww1-centenary>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171003/97160f99/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: do-notsaving.PNG
Type: image/png
Size: 137587 bytes
Desc: do-notsaving.PNG
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171003/97160f99/attachment.png>

From j at minorscience.com  Tue Oct  3 10:30:03 2017
From: j at minorscience.com (Jason Loeffler)
Date: Tue, 3 Oct 2017 10:30:03 -0400
Subject: [Archivesspace_Users_Group] Digital objects in v2.1.1
In-Reply-To: <5a46855b749e4b7c972511053706b3ba@uxcn13-ogg-c.UoA.auckland.ac.nz>
References: <5a46855b749e4b7c972511053706b3ba@uxcn13-ogg-c.UoA.auckland.ac.nz>
Message-ID: <CAP4gJsUPGYBfR+X2cPBD=pLu+eQEt60kRXBqZiy9vrOULZhxrg@mail.gmail.com>

Hi Stephen,

Possibly related to https://archivesspace.atlassian.net/browse/ANW-219?

Can one of the core committers weigh in on this?

JL

On Tue, Oct 3, 2017 at 2:36 AM, Stephen Innes <s.innes at auckland.ac.nz>
wrote:

> We are currently upgrading to v2.1.1 and ironing out various issues.
> Currently digital object records are appearing as invalid with the message
> ?translation missing: en.no key - Property is required but was missing?.
> This appears to be related to the ?Other level? value not being properly
> defined in the backend (see attached screenshot).
>
>
>
> Can someone help us resolve this issue?  The links worked fine in the
> previous version of AS we were using, (v1.4.2).
>
>
>
> Thank you,
>
>
>
> Stephen Innes
>
>
>
> Stephen Innes (ALIANZA)
>
> Special Collections Manager
>
> General Library, Te Herenga M?tauranga Wh?nui
>
> The University of Auckland
>
> Private Bag 92019
>
> Auckland 1142
>
> New Zealand
>
> Telephone (649) 373-7599 ext. 88062 | Fax (649) 373-7565
>
> Website: http://www.library.auckland.ac.nz/about-us/collections/
> special-collections/general-library
>
> Online exhibition: Special Collections First World War Centenary 2014-2018
> <http://www.specialcollections.auckland.ac.nz/ww1-centenary>
>
>
>
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171003/d18f8385/attachment.html>

From noah.huffman at duke.edu  Tue Oct  3 10:37:09 2017
From: noah.huffman at duke.edu (Noah Huffman)
Date: Tue, 3 Oct 2017 14:37:09 +0000
Subject: [Archivesspace_Users_Group] Tool tips and software updates
In-Reply-To: <0899b2c1670a437a9ebaa397f9afe7b3@ESGEBEX8.win.ad.jhu.edu>
References: <CAFy-AYL69nRXQkTR7D2ZyaAP9hWO=5AwccfJfDJz+d5+Y_V_og@mail.gmail.com>
 <0899b2c1670a437a9ebaa397f9afe7b3@ESGEBEX8.win.ad.jhu.edu>
Message-ID: <BN6PR05MB3474A11AC95ED2823FE85E56E6720@BN6PR05MB3474.namprd05.prod.outlook.com>

Hi Christie,

We?ve modified some of the tooltips in a local plugin as Lora suggests.

Here?s an example: https://github.com/duke-libraries/archivesspace-duke-plugins/blob/master/plugins/local/frontend/locales/en.yml

-Noah

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Lora Woodford
Sent: Monday, October 2, 2017 5:09 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Tool tips and software updates

Hey Christie,

As long as you make your changes in a local plugin (see: http://archivesspace.github.io/archivesspace/user/customizing-and-theming-archivesspace/<https://urldefense.proofpoint.com/v2/url?u=http-3A__archivesspace.github.io_archivesspace_user_customizing-2Dand-2Dtheming-2Darchivesspace_&d=DwMGaQ&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=F0JE8U9-xhxe_nE7d7aEUi-uqfKqvYJ222bS0oz9mko&m=VvKcym4ziTtXfrthKs5Zg25gCISLQzxzv1bY0OSf9Dc&s=t-SsIfFVZZrTxpZhSBabbOyN1nbDcNiunllXciuW3jo&e=>) and then have that plugin (and the config that points to it) moved forward through your upgrades, you shouldn?t lose this work.  We haven?t done anything with tooltips, but here?s an example of how we handle label/enum changes via a plugin: https://github.com/jhu-archives-and-manuscripts/jhu-local-plugins<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_jhu-2Darchives-2Dand-2Dmanuscripts_jhu-2Dlocal-2Dplugins&d=DwMGaQ&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=F0JE8U9-xhxe_nE7d7aEUi-uqfKqvYJ222bS0oz9mko&m=VvKcym4ziTtXfrthKs5Zg25gCISLQzxzv1bY0OSf9Dc&s=BVrWcG0Wy47uwjiMhv1oG9waZOImRZF5FujOF9kxvhM&e=>  If you start building out many plugins (even just label changes) be aware that they are loaded in the order they are listed in your config.rb!

Happy to help with any specific questions you might have.

Best,

Lora

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



From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Christie Peterson
Sent: Monday, October 02, 2017 4:58 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] Tool tips and software updates

Hello everyone,

If we invest time into customizing tool tips, will our local changes be retained with ASpace software updates? We're hosting with Lyrasis, if this makes a difference.

Thanks,

Christie Peterson
--
?
Christie S. Peterson

Head of Technical Services for Special Collections
Smith College
Northampton, Mass.
413-585-2996
cpeterson at smith.edu<mailto:cpeterson at smith.edu>

pronouns: she/her/hers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171003/8c7b3442/attachment.html>

From christine.dibella at lyrasis.org  Tue Oct  3 10:51:36 2017
From: christine.dibella at lyrasis.org (Christine Di Bella)
Date: Tue, 3 Oct 2017 14:51:36 +0000
Subject: [Archivesspace_Users_Group] Digital objects in v2.1.1
In-Reply-To: <CAP4gJsUPGYBfR+X2cPBD=pLu+eQEt60kRXBqZiy9vrOULZhxrg@mail.gmail.com>
References: <5a46855b749e4b7c972511053706b3ba@uxcn13-ogg-c.UoA.auckland.ac.nz>
 <CAP4gJsUPGYBfR+X2cPBD=pLu+eQEt60kRXBqZiy9vrOULZhxrg@mail.gmail.com>
Message-ID: <MWHPR08MB345665BC4F3C51B2EB33F7FAF1720@MWHPR08MB3456.namprd08.prod.outlook.com>

Components designated as ?Other Level? having a value of ?null? in the tree is definitely an issue, as Jason points out, but I don?t think it?s the cause of Stephen?s issue since those records will save.

Stephen, are there other fields further down in your record that are possibly incomplete?

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)

[ASpaceOrgHomeMedium]


From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Jason Loeffler
Sent: Tuesday, October 3, 2017 10:30 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Digital objects in v2.1.1

Hi Stephen,

Possibly related to https://archivesspace.atlassian.net/browse/ANW-219?

Can one of the core committers weigh in on this?

JL

On Tue, Oct 3, 2017 at 2:36 AM, Stephen Innes <s.innes at auckland.ac.nz<mailto:s.innes at auckland.ac.nz>> wrote:
We are currently upgrading to v2.1.1 and ironing out various issues. Currently digital object records are appearing as invalid with the message ?translation missing: en.no<http://en.no> key - Property is required but was missing?. This appears to be related to the ?Other level? value not being properly defined in the backend (see attached screenshot).

Can someone help us resolve this issue?  The links worked fine in the previous version of AS we were using, (v1.4.2).

Thank you,

Stephen Innes

Stephen Innes (ALIANZA)
Special Collections Manager
General Library, Te Herenga M?tauranga Wh?nui
The University of Auckland
Private Bag 92019
Auckland 1142
New Zealand
Telephone (649) 373-7599 ext. 88062 | Fax (649) 373-7565
Website: http://www.library.auckland.ac.nz/about-us/collections/special-collections/general-library
Online exhibition: Special Collections First World War Centenary 2014-2018<http://www.specialcollections.auckland.ac.nz/ww1-centenary>



_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171003/56d75f69/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 6608 bytes
Desc: image001.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171003/56d75f69/attachment.jpg>

From noah.huffman at duke.edu  Tue Oct  3 12:24:04 2017
From: noah.huffman at duke.edu (Noah Huffman)
Date: Tue, 3 Oct 2017 16:24:04 +0000
Subject: [Archivesspace_Users_Group] DAO tags missing from EAD exports using
	API?
Message-ID: <BN6PR05MB3474D1AC12C47B5CC79CEADCE6720@BN6PR05MB3474.namprd05.prod.outlook.com>

Hi all,

Sorry for so many subject line acronyms...

I've noticed that <dao> elements are no longer appearing in EAD exports that are initiated through the API in version 2.1.2, even when using the "include_daos=true" parameter in the request.  I've confirmed this on test.archivesspace.org

The <dao> elements do appear when exporting EAD directly from the staff interface and selecting the appropriate "include dao tags" option.

Has anyone else experienced this?

-Noah

================
Noah Huffman
Archivist for Metadata, Systems, and Digital Records
David M. Rubenstein Rare Book & Manuscript Library
Duke University | 919-660-5982
http://library.duke.edu/rubenstein/




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171003/613e1e0e/attachment.html>

From sdm7g at virginia.edu  Tue Oct  3 13:43:45 2017
From: sdm7g at virginia.edu (Majewski, Steven (sdm7g))
Date: Tue, 3 Oct 2017 17:43:45 +0000
Subject: [Archivesspace_Users_Group] DAO tags missing from EAD exports
 using	API?
In-Reply-To: <BN6PR05MB3474D1AC12C47B5CC79CEADCE6720@BN6PR05MB3474.namprd05.prod.outlook.com>
References: <BN6PR05MB3474D1AC12C47B5CC79CEADCE6720@BN6PR05MB3474.namprd05.prod.outlook.com>
Message-ID: <DM5PR13MB17219FD656D60EBD2FFB68678F720@DM5PR13MB1721.namprd13.prod.outlook.com>

Backend API export is working for me on both 2.1.2 and current master devserver .

( I didn't currently have any digital objects with multiple file_versions that would produce daogrp/daoloc  output to test, only single file_versions -> dao. )


If I use the same params on the backend resource_descriptions  API export as the frontend export, I seem to get the same output.  Does it work for you with "include_unpublished=true" added along with "include_daos=true" ?


-- Steve Majewski / UVA Alderman Library
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Noah Huffman <noah.huffman at duke.edu>
Sent: Tuesday, October 3, 2017 12:24:04 PM
To: 'Archivesspace_Users_Group at lyralists.lyrasis.org'
Subject: [Archivesspace_Users_Group] DAO tags missing from EAD exports using API?

Hi all,

Sorry for so many subject line acronyms?

I?ve noticed that <dao> elements are no longer appearing in EAD exports that are initiated through the API in version 2.1.2, even when using the ?include_daos=true? parameter in the request.  I?ve confirmed this on test.archivesspace.org

The <dao> elements do appear when exporting EAD directly from the staff interface and selecting the appropriate ?include dao tags? option.

Has anyone else experienced this?

-Noah

================
Noah Huffman
Archivist for Metadata, Systems, and Digital Records
David M. Rubenstein Rare Book & Manuscript Library
Duke University | 919-660-5982
http://library.duke.edu/rubenstein/




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171003/1b865a4a/attachment.html>

From noah.huffman at duke.edu  Tue Oct  3 14:24:38 2017
From: noah.huffman at duke.edu (Noah Huffman)
Date: Tue, 3 Oct 2017 18:24:38 +0000
Subject: [Archivesspace_Users_Group] DAO tags missing from EAD exports
 using	API?
In-Reply-To: <DM5PR13MB17219FD656D60EBD2FFB68678F720@DM5PR13MB1721.namprd13.prod.outlook.com>
References: <BN6PR05MB3474D1AC12C47B5CC79CEADCE6720@BN6PR05MB3474.namprd05.prod.outlook.com>
 <DM5PR13MB17219FD656D60EBD2FFB68678F720@DM5PR13MB1721.namprd13.prod.outlook.com>
Message-ID: <BN6PR05MB34742D3BFCA6D69324779A9BE6720@BN6PR05MB3474.namprd05.prod.outlook.com>

Hi Steve,

So this is strange.  I tried several different combinations of parameters.  Now I'm getting daos, but only if I put the "include_daos=true" parameter as the first parameter in the request.

But, if I have "include_daos=true&?numbered_cs=true" I'm getting daos, but NOT numbered components like I should.

It seems like something has changed in this version that affects the order of parameters?

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven (sdm7g)
Sent: Tuesday, October 3, 2017 1:44 PM
To: Archivesspace Users Group <Archivesspace_Users_Group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] DAO tags missing from EAD exports using API?


Backend API export is working for me on both 2.1.2 and current master devserver .

( I didn't currently have any digital objects with multiple file_versions that would produce daogrp/daoloc  output to test, only single file_versions -> dao. )



If I use the same params on the backend resource_descriptions  API export as the frontend export, I seem to get the same output.  Does it work for you with "include_unpublished=true" added along with "include_daos=true" ?



-- Steve Majewski / UVA Alderman Library
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Noah Huffman <noah.huffman at duke.edu<mailto:noah.huffman at duke.edu>>
Sent: Tuesday, October 3, 2017 12:24:04 PM
To: 'Archivesspace_Users_Group at lyralists.lyrasis.org'
Subject: [Archivesspace_Users_Group] DAO tags missing from EAD exports using API?

Hi all,

Sorry for so many subject line acronyms...

I've noticed that <dao> elements are no longer appearing in EAD exports that are initiated through the API in version 2.1.2, even when using the "include_daos=true" parameter in the request.  I've confirmed this on test.archivesspace.org

The <dao> elements do appear when exporting EAD directly from the staff interface and selecting the appropriate "include dao tags" option.

Has anyone else experienced this?

-Noah

================
Noah Huffman
Archivist for Metadata, Systems, and Digital Records
David M. Rubenstein Rare Book & Manuscript Library
Duke University | 919-660-5982
http://library.duke.edu/rubenstein/




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171003/01dc3e90/attachment.html>

From noah.huffman at duke.edu  Tue Oct  3 15:30:33 2017
From: noah.huffman at duke.edu (Noah Huffman)
Date: Tue, 3 Oct 2017 19:30:33 +0000
Subject: [Archivesspace_Users_Group] DAO tags missing from EAD exports
 using	API?
In-Reply-To: <BN6PR05MB34742D3BFCA6D69324779A9BE6720@BN6PR05MB3474.namprd05.prod.outlook.com>
References: <BN6PR05MB3474D1AC12C47B5CC79CEADCE6720@BN6PR05MB3474.namprd05.prod.outlook.com>
 <DM5PR13MB17219FD656D60EBD2FFB68678F720@DM5PR13MB1721.namprd13.prod.outlook.com>
 <BN6PR05MB34742D3BFCA6D69324779A9BE6720@BN6PR05MB3474.namprd05.prod.outlook.com>
Message-ID: <BN6PR05MB3474337A2EE1F23B9145B90FE6720@BN6PR05MB3474.namprd05.prod.outlook.com>

OK, I think I sorted this out and everything is working as it should. Disregard the thread.

I tried using another method to hit the API and I'm getting the DAOs as expected. I suspect it's something odd with my scripting framework (my machine was wiped recently and I had to rebuild it).

Apologies for any alarm...

-Noah

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Noah Huffman
Sent: Tuesday, October 3, 2017 2:25 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] DAO tags missing from EAD exports using API?

Hi Steve,

So this is strange.  I tried several different combinations of parameters.  Now I'm getting daos, but only if I put the "include_daos=true" parameter as the first parameter in the request.

But, if I have "include_daos=true&?numbered_cs=true" I'm getting daos, but NOT numbered components like I should.

It seems like something has changed in this version that affects the order of parameters?

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven (sdm7g)
Sent: Tuesday, October 3, 2017 1:44 PM
To: Archivesspace Users Group <Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] DAO tags missing from EAD exports using API?


Backend API export is working for me on both 2.1.2 and current master devserver .

( I didn't currently have any digital objects with multiple file_versions that would produce daogrp/daoloc  output to test, only single file_versions -> dao. )



If I use the same params on the backend resource_descriptions  API export as the frontend export, I seem to get the same output.  Does it work for you with "include_unpublished=true" added along with "include_daos=true" ?



-- Steve Majewski / UVA Alderman Library
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Noah Huffman <noah.huffman at duke.edu<mailto:noah.huffman at duke.edu>>
Sent: Tuesday, October 3, 2017 12:24:04 PM
To: 'Archivesspace_Users_Group at lyralists.lyrasis.org'
Subject: [Archivesspace_Users_Group] DAO tags missing from EAD exports using API?

Hi all,

Sorry for so many subject line acronyms...

I've noticed that <dao> elements are no longer appearing in EAD exports that are initiated through the API in version 2.1.2, even when using the "include_daos=true" parameter in the request.  I've confirmed this on test.archivesspace.org

The <dao> elements do appear when exporting EAD directly from the staff interface and selecting the appropriate "include dao tags" option.

Has anyone else experienced this?

-Noah

================
Noah Huffman
Archivist for Metadata, Systems, and Digital Records
David M. Rubenstein Rare Book & Manuscript Library
Duke University | 919-660-5982
http://library.duke.edu/rubenstein/




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171003/b4d94d24/attachment.html>

From sdm7g at virginia.edu  Tue Oct  3 15:31:37 2017
From: sdm7g at virginia.edu (Majewski, Steven (sdm7g))
Date: Tue, 3 Oct 2017 19:31:37 +0000
Subject: [Archivesspace_Users_Group] DAO tags missing from EAD exports
 using	API?
In-Reply-To: <BN6PR05MB34742D3BFCA6D69324779A9BE6720@BN6PR05MB3474.namprd05.prod.outlook.com>
References: <BN6PR05MB3474D1AC12C47B5CC79CEADCE6720@BN6PR05MB3474.namprd05.prod.outlook.com>
 <DM5PR13MB17219FD656D60EBD2FFB68678F720@DM5PR13MB1721.namprd13.prod.outlook.com>,
 <BN6PR05MB34742D3BFCA6D69324779A9BE6720@BN6PR05MB3474.namprd05.prod.outlook.com>
Message-ID: <DM5PR13MB1721B2D2AA46CFFBBD77C9C48F720@DM5PR13MB1721.namprd13.prod.outlook.com>

I'm not seeing it here, and AFAIK there was no change in the parameter passing -- only in the serialization code.


Are you using the curl_as | curl_as_os scripts ? ( or some other method? )

And quoting the URL or escaping the "&" as \& ?


-- Steve Majewski / UVA Alderman Library
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Noah Huffman <noah.huffman at duke.edu>
Sent: Tuesday, October 3, 2017 2:24:38 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] DAO tags missing from EAD exports using API?

Hi Steve,

So this is strange.  I tried several different combinations of parameters.  Now I?m getting daos, but only if I put the ?include_daos=true? parameter as the first parameter in the request.

But, if I have ?include_daos=true&?numbered_cs=true? I?m getting daos, but NOT numbered components like I should.

It seems like something has changed in this version that affects the order of parameters?

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven (sdm7g)
Sent: Tuesday, October 3, 2017 1:44 PM
To: Archivesspace Users Group <Archivesspace_Users_Group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] DAO tags missing from EAD exports using API?


Backend API export is working for me on both 2.1.2 and current master devserver .

( I didn't currently have any digital objects with multiple file_versions that would produce daogrp/daoloc  output to test, only single file_versions -> dao. )



If I use the same params on the backend resource_descriptions  API export as the frontend export, I seem to get the same output.  Does it work for you with "include_unpublished=true" added along with "include_daos=true" ?



-- Steve Majewski / UVA Alderman Library
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Noah Huffman <noah.huffman at duke.edu<mailto:noah.huffman at duke.edu>>
Sent: Tuesday, October 3, 2017 12:24:04 PM
To: 'Archivesspace_Users_Group at lyralists.lyrasis.org'
Subject: [Archivesspace_Users_Group] DAO tags missing from EAD exports using API?

Hi all,

Sorry for so many subject line acronyms?

I?ve noticed that <dao> elements are no longer appearing in EAD exports that are initiated through the API in version 2.1.2, even when using the ?include_daos=true? parameter in the request.  I?ve confirmed this on test.archivesspace.org

The <dao> elements do appear when exporting EAD directly from the staff interface and selecting the appropriate ?include dao tags? option.

Has anyone else experienced this?

-Noah

================
Noah Huffman
Archivist for Metadata, Systems, and Digital Records
David M. Rubenstein Rare Book & Manuscript Library
Duke University | 919-660-5982
http://library.duke.edu/rubenstein/




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171003/f5503e64/attachment.html>

From christine.dibella at lyrasis.org  Wed Oct  4 09:58:50 2017
From: christine.dibella at lyrasis.org (Christine Di Bella)
Date: Wed, 4 Oct 2017 13:58:50 +0000
Subject: [Archivesspace_Users_Group] release candidate available -
	ArchivesSpace v2.2.0-RC1
Message-ID: <MWHPR08MB3456AEE5B7D70B8D8F259219F1730@MWHPR08MB3456.namprd08.prod.outlook.com>

The ArchivesSpace team is pleased to announce a release candidate, v2.2.0-RC1. You can download it at https://github.com/archivesspace/archivesspace/releases/tag/v2.2.0-RC1 or test it out without downloading at http://test.archivesspace.org (username admin /password admin).

We are especially pleased because this release candidate includes two community-contributed areas of new functionality:

Tufts University subsidized a new assessment module, based very closely on a community-authored specification and hewing closely to the functionality previously available in Archivists' Toolkit. The development was done by Hudson Molonglo. Dan Santamaria and Adrienne Pruitt took the lead on the Tufts side in working closely with HM developers James Bullen, Mark Triggs, and Payten Giles. They also coordinated putting the module out for wider testing, in which people at institutions including the Smithsonian, Smith College, University of Michigan Special Collections, and the Historical Society of Pennsylvania participated.

Trevor Thornton of North Carolina State University and Noah Huffman of Duke University partnered to create an EAD3 exporter, based on a community-distributed specification. Trevor did the development and Noah did extensive and iterative testing. We are excited to have this first level of support for EAD3 in ArchivesSpace and see this as a building block for additional EAD3 support in future releases. Thanks also to Mark Custer at Yale for providing testing feedback.

Thank you so much to Dan, Adrienne, Trevor, and Noah for all their work in bringing these projects to completion and making the results available to the entire ArchivesSpace community. If your institution would like to get involved in subsidizing or working on development prioritized by the ArchivesSpace community, please get in touch with me or Laney.

This release candidate also includes some bug fixes and improvements contributed by community members Steve Majewski, Chris Fitzpatrick, Mark Cooper, Payten Giles, and Christian von Kleist, as well as development work by our Tech Lead Laney McGlohon.

Please test this release candidate as you are able over the next few days and report any issues you find to me at christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>. Barring significant issues, we hope to make the production release available sometime next week.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)

[ASpaceOrgHomeMedium]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171004/80d1f34c/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 6608 bytes
Desc: image003.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171004/80d1f34c/attachment.jpg>

From jsuszczynski at library.rochester.edu  Thu Oct  5 14:11:29 2017
From: jsuszczynski at library.rochester.edu (Suszczynski, Jeffrey)
Date: Thu, 5 Oct 2017 18:11:29 +0000
Subject: [Archivesspace_Users_Group] ArchivesSpace API - looking for working
 example of 'Update a Resource'
Message-ID: <CY4PR07MB2935841CA9B3FA8D5138DEF088700@CY4PR07MB2935.namprd07.prod.outlook.com>

Hello, all -

I've been working with the ArchivesSpace API for a while now, and can successfully pull resource records out of a repository, etc.  More recently, though, I've been trying to update an existing resource within a repository, and keep receiving errors.

Does anyone out there have a working code example of updating a resource in ArchivesSpace, using a local file (preferably PHP, but Python or other languages could be instructive as well)?  I feel like I'm missing something easy and obvious...

Thanks much in advance!
jeff


Jeff Suszczynski
Web Applications Programmer, River Campus Libraries
University of Rochester


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171005/052161ac/attachment-0001.html>

From j at minorscience.com  Thu Oct  5 14:14:04 2017
From: j at minorscience.com (Jason Loeffler)
Date: Thu, 5 Oct 2017 14:14:04 -0400
Subject: [Archivesspace_Users_Group] ArchivesSpace API - looking for
 working example of 'Update a Resource'
In-Reply-To: <CY4PR07MB2935841CA9B3FA8D5138DEF088700@CY4PR07MB2935.namprd07.prod.outlook.com>
References: <CY4PR07MB2935841CA9B3FA8D5138DEF088700@CY4PR07MB2935.namprd07.prod.outlook.com>
Message-ID: <CAP4gJsVCYWmom1cUHFFaJDfijT7GwRqwQbuQoMBq-QX-qaFwZg@mail.gmail.com>

Do you have an example of the update you'd like to make? Can you send an
example of the code you're using to update the resource, as well as the
error you're receiving?

Best, Jason

On Thu, Oct 5, 2017 at 2:11 PM, Suszczynski, Jeffrey <
jsuszczynski at library.rochester.edu> wrote:

> Hello, all ?
>
>
>
> I?ve been working with the ArchivesSpace API for a while now, and can
> successfully pull resource records out of a repository, etc.  More
> recently, though, I?ve been trying to update an existing resource within a
> repository, and keep receiving errors.
>
>
>
> Does anyone out there have a working code example of updating a resource
> in ArchivesSpace, using a local file (preferably PHP, but Python or other
> languages could be instructive as well)?  I feel like I?m missing something
> easy and obvious?
>
>
>
> Thanks much in advance!
> jeff
>
>
>
>
>
> Jeff Suszczynski
>
> Web Applications Programmer, River Campus Libraries
>
> University of Rochester
>
>
>
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171005/d80c033a/attachment.html>

From seth.shaw at unlv.edu  Thu Oct  5 14:21:47 2017
From: seth.shaw at unlv.edu (Seth Shaw)
Date: Thu, 5 Oct 2017 11:21:47 -0700
Subject: [Archivesspace_Users_Group] ArchivesSpace API - looking for
 working example of 'Update a Resource'
In-Reply-To: <CY4PR07MB2935841CA9B3FA8D5138DEF088700@CY4PR07MB2935.namprd07.prod.outlook.com>
References: <CY4PR07MB2935841CA9B3FA8D5138DEF088700@CY4PR07MB2935.namprd07.prod.outlook.com>
Message-ID: <CANuEgP7VU-cmtOYqUfLinfG6gd33tEd9BOXc-6_qFWWdDo7+Jw@mail.gmail.com>

See Noah Huffman's blog post on this topic (
https://blogs.library.duke.edu/bitstreams/2016/09/21/archivesspace-api-fun/)
and the associated scripts on github (
https://github.com/duke-libraries/archivesspace-duke-scripts/tree/master/python
).

Another example of updating a simple field (EAD ID) that I've written can
be found at
https://github.com/seth-shaw-unlv/small-stuff/blob/master/as-coll-mint/as_coll_mint.py


On Thu, Oct 5, 2017 at 11:11 AM, Suszczynski, Jeffrey <
jsuszczynski at library.rochester.edu> wrote:

> Hello, all ?
>
>
>
> I?ve been working with the ArchivesSpace API for a while now, and can
> successfully pull resource records out of a repository, etc.  More
> recently, though, I?ve been trying to update an existing resource within a
> repository, and keep receiving errors.
>
>
>
> Does anyone out there have a working code example of updating a resource
> in ArchivesSpace, using a local file (preferably PHP, but Python or other
> languages could be instructive as well)?  I feel like I?m missing something
> easy and obvious?
>
>
>
> Thanks much in advance!
> jeff
>
>
>
>
>
> Jeff Suszczynski
>
> Web Applications Programmer, River Campus Libraries
>
> University of Rochester
>
>
>
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171005/34774a2e/attachment.html>

From christine.dibella at lyrasis.org  Thu Oct  5 14:40:23 2017
From: christine.dibella at lyrasis.org (Christine Di Bella)
Date: Thu, 5 Oct 2017 18:40:23 +0000
Subject: [Archivesspace_Users_Group] RFP for added container management
	functionality in ArchivesSpace
Message-ID: <MWHPR08MB3456FB0664676FF6116F8399F1700@MWHPR08MB3456.namprd08.prod.outlook.com>

Hello ArchivesSpace members,

ArchivesSpace is seeking proposals from individuals or firms interested in providing development for a limited scope project to add functionality to the container management area of the application. We are prioritizing this work for engagement of an outside contractor based on expressed interest from a number of members, including one that may have funding to pay for it. Please feel free to forward this RFP on to people you think may be interested and qualified to do this work.

We are asking that people please email proposals to me (christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>) by October 27, 2017. Proposals should include a proposed action plan, pricing, timeline, names and contact information for at least two client references, and examples of relevant work in ArchivesSpace or other applications. If people have questions about the RFP, feel free to send them my way as well. Laney can answer technical questions about the application and how delivery of code would work.

Issuing RFPs for specific projects is another strategy we are using to diversify our pool of available developers and continue to making substantial forward progress on the application. If you have any questions, or if you have suggestions for projects that may be particularly appropriate for this type of treatment, please just let us know.

Thanks,
Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)

[ASpaceOrgHomeMedium]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171005/6e170c80/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 6608 bytes
Desc: image002.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171005/6e170c80/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ASpaceContainer Features RFP201710.pdf
Type: application/pdf
Size: 143039 bytes
Desc: ASpaceContainer Features RFP201710.pdf
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171005/6e170c80/attachment.pdf>

From alicia.detelich at yale.edu  Thu Oct  5 16:15:52 2017
From: alicia.detelich at yale.edu (Detelich, Alicia)
Date: Thu, 5 Oct 2017 20:15:52 +0000
Subject: [Archivesspace_Users_Group] RFP for added container management
 functionality in ArchivesSpace
Message-ID: <MWHPR08MB34856CD1F8717B521388FF318E700@MWHPR08MB3485.namprd08.prod.outlook.com>

Hi Christine,

Thank you for sending this. It seems like an exciting project, and many of the listed features are much-needed. I wonder, though, about the advisability of adding the "ability to create top containers independent of specific material records" - https://archivesspace.atlassian.net/browse/AR-1874. You can already do this via the API - in fact, you have to create unlinked top containers before you can link them to material description records. This is less than ideal, as it adds extra steps to the process - after creating the top containers, you then have to pull those top container URIs and link them to the material descriptions using a different endpoint.

If the goal is to create top containers in bulk (and then link them to descriptions) via the staff interface, wouldn't it make more sense, as the JIRA ticket above notes, to add that ability within a material description record or RDE (https://archivesspace.atlassian.net/browse/AR-1873), rather than to enable the potential proliferation of unlinked containers? It seems like this could lead to all kinds of confusion and messy data in ArchivesSpace, especially if there are multiple unlinked containers with the same container profile, indicator, etc. I think it might be better to solve the underlying issue rather than write a workaround into the application.

Alicia

---
Alicia Detelich
Archivist
Manuscripts and Archives
Yale University Libraries
alicia.detelich at yale.edu

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Christine Di Bella
Sent: Thursday, October 5, 2017 2:40 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>; Archivesspace Member Reps <archivesspace_member_reps at lyralists.lyrasis.org>; archivesspace_tac_uac at lyralists.lyrasis.org
Cc: ArchivesSpace Board of Trustees mail list <archivesspace_bot_members at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] RFP for added container management functionality in ArchivesSpace

Hello ArchivesSpace members,

ArchivesSpace is seeking proposals from individuals or firms interested in providing development for a limited scope project to add functionality to the container management area of the application. We are prioritizing this work for engagement of an outside contractor based on expressed interest from a number of members, including one that may have funding to pay for it. Please feel free to forward this RFP on to people you think may be interested and qualified to do this work.

We are asking that people please email proposals to me (christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>) by October 27, 2017. Proposals should include a proposed action plan, pricing, timeline, names and contact information for at least two client references, and examples of relevant work in ArchivesSpace or other applications. If people have questions about the RFP, feel free to send them my way as well. Laney can answer technical questions about the application and how delivery of code would work.

Issuing RFPs for specific projects is another strategy we are using to diversify our pool of available developers and continue to making substantial forward progress on the application. If you have any questions, or if you have suggestions for projects that may be particularly appropriate for this type of treatment, please just let us know.

Thanks,
Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)

[ASpaceOrgHomeMedium]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171005/ae009cec/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 4074 bytes
Desc: image002.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171005/ae009cec/attachment.jpg>

From harmeyna at purdue.edu  Fri Oct  6 09:19:56 2017
From: harmeyna at purdue.edu (Harmeyer, Neal A)
Date: Fri, 6 Oct 2017 13:19:56 +0000
Subject: [Archivesspace_Users_Group] Linked Accessions on Agent Page Not
	Displaying
Message-ID: <c6d394633290457292f656edf6a58be3@wppexc09.purdue.lcl>

Hello everyone,

It appears accessions that have a linked agent record are not displaying on the Agent's individual page in the public interface. All collections associated with the agents, whether as a source, subject, or creator, do display on the agent page as Related Collections and/or Records-just not accessions. I have made certain the accessions in question are enabled for publication and discoverable in the public interface via search/browse, so it's not that the accessions are hidden from public view. I've highlighted an example in the attached screenshots where an agent with 13 linked accessions/collections combined in the database gives the false impression there is only a single collection associated with that agent when landing on the agent page.

Any chance I'm missing something? Or is there a reason accessions do not appear on an agent page? Purdue would like to see published accessions also appear on the page of an agent in the public interface.

We're using version 2.1.2.

Thank you,
Neal
--
Neal Harmeyer
Digital Archivist
Archives and Special Collections
Purdue University Libraries
harmeyna at purdue.edu<mailto:harmeyna at purdue.edu>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171006/70361b95/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2-accessions-display-agents-single-unprocessed-agent-linked.JPG
Type: image/jpeg
Size: 97442 bytes
Desc: 2-accessions-display-agents-single-unprocessed-agent-linked.JPG
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171006/70361b95/attachment-0003.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 3-accessions-display-agents-name-page-related-materials.JPG
Type: image/jpeg
Size: 289215 bytes
Desc: 3-accessions-display-agents-name-page-related-materials.JPG
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171006/70361b95/attachment-0004.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 1-accessions-display-agents-allresults.JPG
Type: image/jpeg
Size: 223113 bytes
Desc: 1-accessions-display-agents-allresults.JPG
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171006/70361b95/attachment-0005.jpe>

From mcallahan at smith.edu  Fri Oct  6 09:36:26 2017
From: mcallahan at smith.edu (Maureen Callahan)
Date: Fri, 6 Oct 2017 09:36:26 -0400
Subject: [Archivesspace_Users_Group] RFP for added container management
 functionality in ArchivesSpace
In-Reply-To: <MWHPR08MB34856CD1F8717B521388FF318E700@MWHPR08MB3485.namprd08.prod.outlook.com>
References: <MWHPR08MB34856CD1F8717B521388FF318E700@MWHPR08MB3485.namprd08.prod.outlook.com>
Message-ID: <CAH0VKbBnQ13i2ramgDb1he9K91+uw-NP1UZv7m3ALRtfVn-gaQ@mail.gmail.com>

Hi everyone,

I just wanted to chime in to echo Alicia's excitement about most of these
changes and express my own concern about AR-1874.

It's hard to imagine, from a collections control perspective, the advantage
of having free-floating top containers not associated with intellectual
information. Even if you have a true "mystery box" in your repository that
has indecipherable scrawled sharpie on it (we've all been there, I AM
there, I feel you), I think that it would be more valuable to associate
this with an accession or resource record that explains that this is a true
mystery and where you can record the steps that you've already taken to
decipher it. Otherwise, you can't tell whether it's a lost/mystery box or
if it was just somehow unlinked from the resource/accession record it
belongs to.

Something I find valuable about ArchivesSpace is that as a system, it
forces a minimum of best archival practices -- for instance, a resource
record reinforces the DACS single-level minimum element set, top containers
won't let you repeat barcodes, etc. I think that those of us who have
participated in collection survey / remediation / backlog projects would
definitely appreciate a system that forces at least some association
between the stuff and where it came from.

Thanks!
Maureen

On Thu, Oct 5, 2017 at 4:15 PM, Detelich, Alicia <alicia.detelich at yale.edu>
wrote:

> Hi Christine,
>
>
>
> Thank you for sending this. It seems like an exciting project, and many of
> the listed features are much-needed. I wonder, though, about the
> advisability of adding the ?ability to create top containers independent of
> specific material records? - https://archivesspace.
> atlassian.net/browse/AR-1874. You can already do this via the API - in
> fact, you have to create unlinked top containers before you can link them
> to material description records. This is less than ideal, as it adds extra
> steps to the process - after creating the top containers, you then have to
> pull those top container URIs and link them to the material descriptions
> using a different endpoint.
>
>
>
> If the goal is to create top containers in bulk (and then link them to
> descriptions) via the staff interface, wouldn?t it make more sense, as the
> JIRA ticket above notes, to add that ability within a material description
> record or RDE (https://archivesspace.atlassian.net/browse/AR-1873),
> rather than to enable the potential proliferation of unlinked containers?
> It seems like this could lead to all kinds of confusion and messy data in
> ArchivesSpace, especially if there are multiple unlinked containers with
> the same container profile, indicator, etc. I think it might be better to
> solve the underlying issue rather than write a workaround into the
> application.
>
>
>
> Alicia
>
>
>
> ---
>
> Alicia Detelich
>
> Archivist
>
> Manuscripts and Archives
>
> Yale University Libraries
>
> alicia.detelich at yale.edu
>
>
>
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:
> archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Christine
> Di Bella
> *Sent:* Thursday, October 5, 2017 2:40 PM
> *To:* Archivesspace Users Group <archivesspace_users_group@
> lyralists.lyrasis.org>; Archivesspace Member Reps <
> archivesspace_member_reps at lyralists.lyrasis.org>; archivesspace_tac_uac@
> lyralists.lyrasis.org
> *Cc:* ArchivesSpace Board of Trustees mail list <
> archivesspace_bot_members at lyralists.lyrasis.org>
> *Subject:* [Archivesspace_Users_Group] RFP for added container management
> functionality in ArchivesSpace
>
>
>
> Hello ArchivesSpace members,
>
>
>
> ArchivesSpace is seeking proposals from individuals or firms interested in
> providing development for a limited scope project to add functionality to
> the container management area of the application. We are prioritizing this
> work for engagement of an outside contractor based on expressed interest
> from a number of members, including one that may have funding to pay for
> it. Please feel free to forward this RFP on to people you think may be
> interested and qualified to do this work.
>
>
>
> We are asking that people please email proposals to me (
> christine.dibella at lyrasis.org) by October 27, 2017. Proposals should
> include a proposed action plan, pricing, timeline, names and contact
> information for at least two client references, and examples of relevant
> work in ArchivesSpace or other applications. If people have questions about
> the RFP, feel free to send them my way as well. Laney can answer technical
> questions about the application and how delivery of code would work.
>
>
>
> Issuing RFPs for specific projects is another strategy we are using to
> diversify our pool of available developers and continue to making
> substantial forward progress on the application. If you have any questions,
> or if you have suggestions for projects that may be particularly
> appropriate for this type of treatment, please just let us know.
>
>
>
> Thanks,
>
> Christine
>
>
>
> Christine Di Bella
>
> ArchivesSpace Program Manager
>
> christine.dibella at lyrasis.org
>
> 800.999.8558 x2905 <(800)%20999-8558>
>
> 678-235-2905 <(678)%20235-2905>
>
> cdibella13 (Skype)
>
>
>
> [image: ASpaceOrgHomeMedium]
>
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>


-- 
Maureen Callahan
Sophia Smith Collection Archivist
Smith College Special Collections
Northampton, Massachusetts 01063
T. 413 585 2981 C. 215.863.1860
mcallahan at smith.edu

Pronouns: she/her/hers

Facebook: https://www.facebook.com/SophiaSmithCollection/
Instagram: https://www.instagram.com/smithlibraries/
Twitter: https://twitter.com/archivalagents

*Please note*. Smith College Special Collections is now housed at Young
Library
<https://www.smith.edu/libraries/about/new-neilson/wheres-my-library>.
Learn more about renovations to Neilson Library here
<https://www.smith.edu/libraries/about/new-neilson>.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171006/2f4feb3a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 4074 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171006/2f4feb3a/attachment.jpg>

From cyndi.shein at unlv.edu  Fri Oct  6 12:41:09 2017
From: cyndi.shein at unlv.edu (Cyndi Shein)
Date: Fri, 6 Oct 2017 09:41:09 -0700
Subject: [Archivesspace_Users_Group] RFP for added container management
 functionality in ArchivesSpace
In-Reply-To: <CAH0VKbBnQ13i2ramgDb1he9K91+uw-NP1UZv7m3ALRtfVn-gaQ@mail.gmail.com>
References: <MWHPR08MB34856CD1F8717B521388FF318E700@MWHPR08MB3485.namprd08.prod.outlook.com>
 <CAH0VKbBnQ13i2ramgDb1he9K91+uw-NP1UZv7m3ALRtfVn-gaQ@mail.gmail.com>
Message-ID: <CAHYOJB_vaz3qcAyz4-BseH0WrRBVGqO1z5tjZnR9ok8noj-9NA@mail.gmail.com>

I agree with Maureen.

Cyndi

On Fri, Oct 6, 2017 at 6:36 AM, Maureen Callahan <mcallahan at smith.edu>
wrote:

> Hi everyone,
>
> I just wanted to chime in to echo Alicia's excitement about most of these
> changes and express my own concern about AR-1874.
>
> It's hard to imagine, from a collections control perspective, the
> advantage of having free-floating top containers not associated with
> intellectual information. Even if you have a true "mystery box" in your
> repository that has indecipherable scrawled sharpie on it (we've all been
> there, I AM there, I feel you), I think that it would be more valuable to
> associate this with an accession or resource record that explains that this
> is a true mystery and where you can record the steps that you've already
> taken to decipher it. Otherwise, you can't tell whether it's a lost/mystery
> box or if it was just somehow unlinked from the resource/accession record
> it belongs to.
>
> Something I find valuable about ArchivesSpace is that as a system, it
> forces a minimum of best archival practices -- for instance, a resource
> record reinforces the DACS single-level minimum element set, top containers
> won't let you repeat barcodes, etc. I think that those of us who have
> participated in collection survey / remediation / backlog projects would
> definitely appreciate a system that forces at least some association
> between the stuff and where it came from.
>
> Thanks!
> Maureen
>
> On Thu, Oct 5, 2017 at 4:15 PM, Detelich, Alicia <alicia.detelich at yale.edu
> > wrote:
>
>> Hi Christine,
>>
>>
>>
>> Thank you for sending this. It seems like an exciting project, and many
>> of the listed features are much-needed. I wonder, though, about the
>> advisability of adding the ?ability to create top containers independent of
>> specific material records? - https://archivesspace.atlassia
>> n.net/browse/AR-1874. You can already do this via the API - in fact, you
>> have to create unlinked top containers before you can link them to material
>> description records. This is less than ideal, as it adds extra steps to the
>> process - after creating the top containers, you then have to pull those
>> top container URIs and link them to the material descriptions using a
>> different endpoint.
>>
>>
>>
>> If the goal is to create top containers in bulk (and then link them to
>> descriptions) via the staff interface, wouldn?t it make more sense, as the
>> JIRA ticket above notes, to add that ability within a material description
>> record or RDE (https://archivesspace.atlassian.net/browse/AR-1873),
>> rather than to enable the potential proliferation of unlinked containers?
>> It seems like this could lead to all kinds of confusion and messy data in
>> ArchivesSpace, especially if there are multiple unlinked containers with
>> the same container profile, indicator, etc. I think it might be better to
>> solve the underlying issue rather than write a workaround into the
>> application.
>>
>>
>>
>> Alicia
>>
>>
>>
>> ---
>>
>> Alicia Detelich
>>
>> Archivist
>>
>> Manuscripts and Archives
>>
>> Yale University Libraries
>>
>> alicia.detelich at yale.edu
>>
>>
>>
>> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:
>> archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Christine
>> Di Bella
>> *Sent:* Thursday, October 5, 2017 2:40 PM
>> *To:* Archivesspace Users Group <archivesspace_users_group at lyr
>> alists.lyrasis.org>; Archivesspace Member Reps <
>> archivesspace_member_reps at lyralists.lyrasis.org>;
>> archivesspace_tac_uac at lyralists.lyrasis.org
>> *Cc:* ArchivesSpace Board of Trustees mail list <
>> archivesspace_bot_members at lyralists.lyrasis.org>
>> *Subject:* [Archivesspace_Users_Group] RFP for added container
>> management functionality in ArchivesSpace
>>
>>
>>
>> Hello ArchivesSpace members,
>>
>>
>>
>> ArchivesSpace is seeking proposals from individuals or firms interested
>> in providing development for a limited scope project to add functionality
>> to the container management area of the application. We are prioritizing
>> this work for engagement of an outside contractor based on expressed
>> interest from a number of members, including one that may have funding to
>> pay for it. Please feel free to forward this RFP on to people you think may
>> be interested and qualified to do this work.
>>
>>
>>
>> We are asking that people please email proposals to me (
>> christine.dibella at lyrasis.org) by October 27, 2017. Proposals should
>> include a proposed action plan, pricing, timeline, names and contact
>> information for at least two client references, and examples of relevant
>> work in ArchivesSpace or other applications. If people have questions about
>> the RFP, feel free to send them my way as well. Laney can answer technical
>> questions about the application and how delivery of code would work.
>>
>>
>>
>> Issuing RFPs for specific projects is another strategy we are using to
>> diversify our pool of available developers and continue to making
>> substantial forward progress on the application. If you have any questions,
>> or if you have suggestions for projects that may be particularly
>> appropriate for this type of treatment, please just let us know.
>>
>>
>>
>> Thanks,
>>
>> Christine
>>
>>
>>
>> Christine Di Bella
>>
>> ArchivesSpace Program Manager
>>
>> christine.dibella at lyrasis.org
>>
>> 800.999.8558 x2905 <(800)%20999-8558>
>>
>> 678-235-2905 <(678)%20235-2905>
>>
>> cdibella13 (Skype)
>>
>>
>>
>> [image: ASpaceOrgHomeMedium]
>>
>>
>>
>> _______________________________________________
>> Archivesspace_Users_Group mailing list
>> Archivesspace_Users_Group at lyralists.lyrasis.org
>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>>
>>
>
>
> --
> Maureen Callahan
> Sophia Smith Collection Archivist
> Smith College Special Collections
> Northampton, Massachusetts 01063
> T. 413 585 2981 <(413)%20585-2981> C. 215.863.1860 <(215)%20863-1860>
> mcallahan at smith.edu
>
> Pronouns: she/her/hers
>
> Facebook: https://www.facebook.com/SophiaSmithCollection/
> Instagram: https://www.instagram.com/smithlibraries/
> Twitter: https://twitter.com/archivalagents
>
> *Please note*. Smith College Special Collections is now housed at Young
> Library
> <https://www.smith.edu/libraries/about/new-neilson/wheres-my-library>.
> Learn more about renovations to Neilson Library here
> <https://www.smith.edu/libraries/about/new-neilson>.
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171006/d7a4ada9/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 4074 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171006/d7a4ada9/attachment.jpg>

From jsteele at jhu.edu  Mon Oct  9 09:06:08 2017
From: jsteele at jhu.edu (Jordon Steele)
Date: Mon, 9 Oct 2017 13:06:08 +0000
Subject: [Archivesspace_Users_Group] Search engine optimization for the
	ASpace PUI?
Message-ID: <b5998a7603c2463b9d71aad31f423b81@ESGMTWEX6.win.ad.jhu.edu>

Hi all,



Since adopting the PUI, we have noticed that our search engine rankings for our finding aids have fallen substantially. I'm curious if anyone who has experienced something similar can share any steps they took to improve these rankings. It's unclear to us at present if this is a function of the PUI code base or not. I saw a bunch of tickets about search issues within the application, nothing on SEO, though (forgive me if I overlooked something).



Thanks in advance!


Best,

Jordon

Jordon Steele
Hodson Curator of the University Archives
The Sheridan Libraries
Johns Hopkins University
3400 N Charles Street
Baltimore, MD 21218
(410) 516-5493
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171009/2fc08b6f/attachment.html>

From JShedd at library.msstate.edu  Mon Oct  9 11:50:57 2017
From: JShedd at library.msstate.edu (Shedd, Julie)
Date: Mon, 9 Oct 2017 15:50:57 +0000
Subject: [Archivesspace_Users_Group] Job - Web Developer at Mississippi
	State University
Message-ID: <6314a65ff0ec43039f491621985ca24b@mail05.ad.msstate.edu>

Apply at http://explore.msujobs.msstate.edu/cw/en-us/job/496306/web-developer. Please contact Demetrice Williams with any questions: dwilliams at library.msstate.edu<mailto:dwilliams at library.msstate.edu>.

Web Developer

Job no: 496306
Position type: Full-Time 12-Month
Department: 320100 - General Library
Location: Main Campus - Starkville, MS
Categories: Professional
Position Open Date: Sep 15 2017

Salary Grade/Salary Minimum:
14/$40,400

Department Profile:
The University Libraries provide their communities of users an ongoing, creative and technologically advanced library program.

Area of Specialization:
Web Services

Essential Duties and Responsibilities:
The following examples are intended as illustrations only of the various types of duties assigned in positions allocated to this classification. The absence of specific statements of duties does not exclude those tasks from the position if the work is similar, related, or a logical assignment of the position.

  1.  Maintains existing and develops new websites and web applications including database programming, multimedia development and web editing;
  2.  Assists in integrating other 3rd party applications into new and existing websites/applications;
  3.  Assists with concept design, content delivery and exploring/recommending emerging technologies and services that will benefit the library program;
  4.  Provides technical support, training and ongoing development for a variety of existing applications;
  5.  Develops and maintains mobile web applications;
  6.  Works with Library Web Team to ensure appropriate web site ADA compliance as well as compliance with University policies;
  7.  Supervises student workers and manages student payroll for Web Services team;
  8.  Tracks, analyzes and reports on current web usage statistics;
  9.  Performs miscellaneous job-related duties as assigned.

Minimum Qualifications:
Bachelor's degree in related field ~AND~ One (1) year related experience in maintaining and developing web-related applications.

Preferred Qualifications:

  *   Experience with Drupal
  *   Experience with agile development methodologies

Knowledge, Skills, and Abilities:

  *   Strong interpersonal communication, organizational and problem-solving skills;
  *   Demonstrated experience with web design software and programming experience using HTML, CSS, PHP, JavaScript and other languages;
  *   Experience with various database systems including MySQL and Microsoft SQL;
  *   Must be familiar with Internet protocols, web-based authentication methods and proxy servers in order to manage the site and maintain a high level of security for various databases and websites;
  *   Understanding of web standards and accessibility as defined by the W3C and Section 508 Compliance;

Working Conditions and Physical Effort:

  *   No unusual physical requirements. Must be able to sit at a computer for extended periods of time. Requires limited lifting of files and records and nearly all work is performed in a comfortable indoor facility;
  *   Frequent external imposed deadlines; set and revised beyond one's control; interruptions influence priorities; difficult to anticipate nature or volume of work with certainty beyond a few days; meeting of deadlines and coordination of unrelated activities are key to position; involves conflict-resolution or similar interactions involving emotional issues or stress on a regular basis;
  *   Job frequently requires walking, sitting, reaching, talking, hearing, handling objects with hands;
  *   Vision requirements: Ability to see information in print and/or electronically;
  *   Work is normally performed in a typical interior/office work environment;
  *   No or very limited exposure to physical risk;
  *   No or very limited physical effort required.

Instructions for Applying:
All applicants must apply online at www.msujobs.msstate.edu<http://explore.msujobs.msstate.edu/cw/en-us/job/496306/www.msujobs.msstate.edu> and attach a cover letter and resume.
Equal Employment Opportunity Statement:
MSU is an equal opportunity employer, and all qualified applicants will receive consideration for employment without regard to race, color, religion, ethnicity, sex (including pregnancy and gender identity), national origin, disability status, age, sexual orientation, genetic information, protected veteran status, or any other characteristic protected by law. We always welcome nominations and applications from women, members of any minority group, and others who share our passion for building a diverse community that reflects the diversity in our student population.


---------------------------------------------------------------------------------------------------
   Julie D. Shedd
   Coordinator of Digital Initiatives & Web Services, Mississippi State University Libraries<http://library.msstate.edu/>
   (662) 325-0300 | jshedd at library.msstate.edu<mailto:jshedd at library.msstate.edu> | http://library.msstate.edu/juliedshedd

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171009/8d56eea4/attachment.html>

From Alston.Cobourn at tamucc.edu  Mon Oct  9 14:24:21 2017
From: Alston.Cobourn at tamucc.edu (Cobourn, Alston)
Date: Mon, 9 Oct 2017 18:24:21 +0000
Subject: [Archivesspace_Users_Group] Archivesspace_Users_Group Digest,
	Vol 51, Issue 2
In-Reply-To: <mailman.3403.1507296004.20855.archivesspace_users_group@lyralists.lyrasis.org>
References: <mailman.3403.1507296004.20855.archivesspace_users_group@lyralists.lyrasis.org>
Message-ID: <DM5PR06MB31139EE3EE32B03243A8B9B6E0740@DM5PR06MB3113.namprd06.prod.outlook.com>

In July I added an accession record to ArchivesSpace and added instances to it.  I looked at that accession record on several occasions after that.


Two weeks ago I looked at our ArchivesSpace accession records to gather statistics for our annual report and discovered that the accession record mentioned above no longer displayed in accessions browse view and was not returned as a search result when searched for.  The linked instances do still show up in search results, but the system says they are not linked to any other records.


If I try to add a new accession to the system with the same ID number it tells me it cannot add the record because that identifier is already in use.  I have confirmed that the original accession is still listed in the accessions table in the backend database.


Does anyone have thoughts as to why this record was showing up in the staff interface but now is not?  I have not run into this issue with any other records of any kind.  The indexer appears to be working; changes we make- deletions and additions-  are showing up in the staff interface.

________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of archivesspace_users_group-request at lyralists.lyrasis.org <archivesspace_users_group-request at lyralists.lyrasis.org>
Sent: Friday, October 6, 2017 8:20:04 AM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: Archivesspace_Users_Group Digest, Vol 51, Issue 2

Send Archivesspace_Users_Group mailing list submissions to
        archivesspace_users_group at lyralists.lyrasis.org

To subscribe or unsubscribe via the World Wide Web, visit
        http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

or, via email, send a message with subject or body 'help' to
        archivesspace_users_group-request at lyralists.lyrasis.org

You can reach the person managing the list at
        archivesspace_users_group-owner at lyralists.lyrasis.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Archivesspace_Users_Group digest..."


Today's Topics:

   1. Re: ArchivesSpace API - looking for working example of
      'Update a Resource' (Jason Loeffler)
   2. Re: ArchivesSpace API - looking for working example of
      'Update a Resource' (Seth Shaw)
   3. RFP for added container management        functionality in
      ArchivesSpace (Christine Di Bella)
   4. Re: RFP for added container management functionality in
      ArchivesSpace (Detelich, Alicia)
   5. Linked Accessions on Agent Page Not       Displaying (Harmeyer, Neal A)


----------------------------------------------------------------------

Message: 1
Date: Thu, 5 Oct 2017 14:14:04 -0400
From: Jason Loeffler <j at minorscience.com>
To: Archivesspace Users Group
        <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] ArchivesSpace API - looking
        for working example of 'Update a Resource'
Message-ID:
        <CAP4gJsVCYWmom1cUHFFaJDfijT7GwRqwQbuQoMBq-QX-qaFwZg at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Do you have an example of the update you'd like to make? Can you send an
example of the code you're using to update the resource, as well as the
error you're receiving?

Best, Jason

On Thu, Oct 5, 2017 at 2:11 PM, Suszczynski, Jeffrey <
jsuszczynski at library.rochester.edu> wrote:

> Hello, all ?
>
>
>
> I?ve been working with the ArchivesSpace API for a while now, and can
> successfully pull resource records out of a repository, etc.  More
> recently, though, I?ve been trying to update an existing resource within a
> repository, and keep receiving errors.
>
>
>
> Does anyone out there have a working code example of updating a resource
> in ArchivesSpace, using a local file (preferably PHP, but Python or other
> languages could be instructive as well)?  I feel like I?m missing something
> easy and obvious?
>
>
>
> Thanks much in advance!
> jeff
>
>
>
>
>
> Jeff Suszczynski
>
> Web Applications Programmer, River Campus Libraries
>
> University of Rochester
>
>
>
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171005/d80c033a/attachment-0001.html>

------------------------------

Message: 2
Date: Thu, 5 Oct 2017 11:21:47 -0700
From: Seth Shaw <seth.shaw at unlv.edu>
To: Archivesspace Users Group
        <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] ArchivesSpace API - looking
        for working example of 'Update a Resource'
Message-ID:
        <CANuEgP7VU-cmtOYqUfLinfG6gd33tEd9BOXc-6_qFWWdDo7+Jw at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

See Noah Huffman's blog post on this topic (
https://blogs.library.duke.edu/bitstreams/2016/09/21/archivesspace-api-fun/)
and the associated scripts on github (
https://github.com/duke-libraries/archivesspace-duke-scripts/tree/master/python
).

Another example of updating a simple field (EAD ID) that I've written can
be found at
https://github.com/seth-shaw-unlv/small-stuff/blob/master/as-coll-mint/as_coll_mint.py


On Thu, Oct 5, 2017 at 11:11 AM, Suszczynski, Jeffrey <
jsuszczynski at library.rochester.edu> wrote:

> Hello, all ?
>
>
>
> I?ve been working with the ArchivesSpace API for a while now, and can
> successfully pull resource records out of a repository, etc.  More
> recently, though, I?ve been trying to update an existing resource within a
> repository, and keep receiving errors.
>
>
>
> Does anyone out there have a working code example of updating a resource
> in ArchivesSpace, using a local file (preferably PHP, but Python or other
> languages could be instructive as well)?  I feel like I?m missing something
> easy and obvious?
>
>
>
> Thanks much in advance!
> jeff
>
>
>
>
>
> Jeff Suszczynski
>
> Web Applications Programmer, River Campus Libraries
>
> University of Rochester
>
>
>
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171005/34774a2e/attachment-0001.html>

------------------------------

Message: 3
Date: Thu, 5 Oct 2017 18:40:23 +0000
From: Christine Di Bella <christine.dibella at lyrasis.org>
To: Archivesspace Users Group
        <archivesspace_users_group at lyralists.lyrasis.org>, Archivesspace
        Member Reps <archivesspace_member_reps at lyralists.lyrasis.org>,
        "archivesspace_tac_uac at lyralists.lyrasis.org"
        <archivesspace_tac_uac at lyralists.lyrasis.org>
Cc: ArchivesSpace Board of Trustees mail list
        <archivesspace_bot_members at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] RFP for added container
        management      functionality in ArchivesSpace
Message-ID:
        <MWHPR08MB3456FB0664676FF6116F8399F1700 at MWHPR08MB3456.namprd08.prod.outlook.com>

Content-Type: text/plain; charset="us-ascii"

Hello ArchivesSpace members,

ArchivesSpace is seeking proposals from individuals or firms interested in providing development for a limited scope project to add functionality to the container management area of the application. We are prioritizing this work for engagement of an outside contractor based on expressed interest from a number of members, including one that may have funding to pay for it. Please feel free to forward this RFP on to people you think may be interested and qualified to do this work.

We are asking that people please email proposals to me (christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>) by October 27, 2017. Proposals should include a proposed action plan, pricing, timeline, names and contact information for at least two client references, and examples of relevant work in ArchivesSpace or other applications. If people have questions about the RFP, feel free to send them my way as well. Laney can answer technical questions about the application and how delivery of code would work.

Issuing RFPs for specific projects is another strategy we are using to diversify our pool of available developers and continue to making substantial forward progress on the application. If you have any questions, or if you have suggestions for projects that may be particularly appropriate for this type of treatment, please just let us know.

Thanks,
Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)

[ASpaceOrgHomeMedium]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171005/6e170c80/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 6608 bytes
Desc: image002.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171005/6e170c80/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ASpaceContainer Features RFP201710.pdf
Type: application/pdf
Size: 143039 bytes
Desc: ASpaceContainer Features RFP201710.pdf
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171005/6e170c80/attachment-0001.pdf>

------------------------------

Message: 4
Date: Thu, 5 Oct 2017 20:15:52 +0000
From: "Detelich, Alicia" <alicia.detelich at yale.edu>
To: Archivesspace Users Group
        <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] RFP for added container
        management functionality in ArchivesSpace
Message-ID:
        <MWHPR08MB34856CD1F8717B521388FF318E700 at MWHPR08MB3485.namprd08.prod.outlook.com>

Content-Type: text/plain; charset="us-ascii"

Hi Christine,

Thank you for sending this. It seems like an exciting project, and many of the listed features are much-needed. I wonder, though, about the advisability of adding the "ability to create top containers independent of specific material records" - https://archivesspace.atlassian.net/browse/AR-1874. You can already do this via the API - in fact, you have to create unlinked top containers before you can link them to material description records. This is less than ideal, as it adds extra steps to the process - after creating the top containers, you then have to pull those top container URIs and link them to the material descriptions using a different endpoint.

If the goal is to create top containers in bulk (and then link them to descriptions) via the staff interface, wouldn't it make more sense, as the JIRA ticket above notes, to add that ability within a material description record or RDE (https://archivesspace.atlassian.net/browse/AR-1873), rather than to enable the potential proliferation of unlinked containers? It seems like this could lead to all kinds of confusion and messy data in ArchivesSpace, especially if there are multiple unlinked containers with the same container profile, indicator, etc. I think it might be better to solve the underlying issue rather than write a workaround into the application.

Alicia

---
Alicia Detelich
Archivist
Manuscripts and Archives
Yale University Libraries
alicia.detelich at yale.edu

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Christine Di Bella
Sent: Thursday, October 5, 2017 2:40 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>; Archivesspace Member Reps <archivesspace_member_reps at lyralists.lyrasis.org>; archivesspace_tac_uac at lyralists.lyrasis.org
Cc: ArchivesSpace Board of Trustees mail list <archivesspace_bot_members at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] RFP for added container management functionality in ArchivesSpace

Hello ArchivesSpace members,

ArchivesSpace is seeking proposals from individuals or firms interested in providing development for a limited scope project to add functionality to the container management area of the application. We are prioritizing this work for engagement of an outside contractor based on expressed interest from a number of members, including one that may have funding to pay for it. Please feel free to forward this RFP on to people you think may be interested and qualified to do this work.

We are asking that people please email proposals to me (christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>) by October 27, 2017. Proposals should include a proposed action plan, pricing, timeline, names and contact information for at least two client references, and examples of relevant work in ArchivesSpace or other applications. If people have questions about the RFP, feel free to send them my way as well. Laney can answer technical questions about the application and how delivery of code would work.

Issuing RFPs for specific projects is another strategy we are using to diversify our pool of available developers and continue to making substantial forward progress on the application. If you have any questions, or if you have suggestions for projects that may be particularly appropriate for this type of treatment, please just let us know.

Thanks,
Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)

[ASpaceOrgHomeMedium]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171005/ae009cec/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 4074 bytes
Desc: image002.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171005/ae009cec/attachment-0001.jpg>

------------------------------

Message: 5
Date: Fri, 6 Oct 2017 13:19:56 +0000
From: "Harmeyer, Neal A" <harmeyna at purdue.edu>
To: Archivesspace Users Group
        <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Linked Accessions on Agent Page
        Not     Displaying
Message-ID: <c6d394633290457292f656edf6a58be3 at wppexc09.purdue.lcl>
Content-Type: text/plain; charset="us-ascii"

Hello everyone,

It appears accessions that have a linked agent record are not displaying on the Agent's individual page in the public interface. All collections associated with the agents, whether as a source, subject, or creator, do display on the agent page as Related Collections and/or Records-just not accessions. I have made certain the accessions in question are enabled for publication and discoverable in the public interface via search/browse, so it's not that the accessions are hidden from public view. I've highlighted an example in the attached screenshots where an agent with 13 linked accessions/collections combined in the database gives the false impression there is only a single collection associated with that agent when landing on the agent page.

Any chance I'm missing something? Or is there a reason accessions do not appear on an agent page? Purdue would like to see published accessions also appear on the page of an agent in the public interface.

We're using version 2.1.2.

Thank you,
Neal
--
Neal Harmeyer
Digital Archivist
Archives and Special Collections
Purdue University Libraries
harmeyna at purdue.edu<mailto:harmeyna at purdue.edu>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171006/70361b95/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2-accessions-display-agents-single-unprocessed-agent-linked.JPG
Type: image/jpeg
Size: 97442 bytes
Desc: 2-accessions-display-agents-single-unprocessed-agent-linked.JPG
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171006/70361b95/attachment.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 3-accessions-display-agents-name-page-related-materials.JPG
Type: image/jpeg
Size: 289215 bytes
Desc: 3-accessions-display-agents-name-page-related-materials.JPG
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171006/70361b95/attachment-0001.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 1-accessions-display-agents-allresults.JPG
Type: image/jpeg
Size: 223113 bytes
Desc: 1-accessions-display-agents-allresults.JPG
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171006/70361b95/attachment-0002.jpe>

------------------------------

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


End of Archivesspace_Users_Group Digest, Vol 51, Issue 2
********************************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171009/2cc35585/attachment.html>

From blake.carver at lyrasis.org  Mon Oct  9 17:14:51 2017
From: blake.carver at lyrasis.org (Blake Carver)
Date: Mon, 9 Oct 2017 21:14:51 +0000
Subject: [Archivesspace_Users_Group] Archivesspace_Users_Group Digest,
 Vol 51, Issue 2
In-Reply-To: <DM5PR06MB31139EE3EE32B03243A8B9B6E0740@DM5PR06MB3113.namprd06.prod.outlook.com>
References: <mailman.3403.1507296004.20855.archivesspace_users_group@lyralists.lyrasis.org>,
 <DM5PR06MB31139EE3EE32B03243A8B9B6E0740@DM5PR06MB3113.namprd06.prod.outlook.com>
Message-ID: <BY2PR0801MB1510F4C09B125B29979F0C389F740@BY2PR0801MB1510.namprd08.prod.outlook.com>

That's almost certainly an indexing issue. The record is in the database, but has somehow ended up either not in the index or the index has gone off the rails.
You should probably recreate your indexes:
http://archivesspace.github.io/archivesspace/user/re-creating-indexes/



________________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Cobourn, Alston <Alston.Cobourn at tamucc.edu>
Sent: Monday, October 9, 2017 2:24:21 PM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: Re: [Archivesspace_Users_Group] Archivesspace_Users_Group Digest,      Vol 51, Issue 2

In July I added an accession record to ArchivesSpace and added instances to it.  I looked at that accession record on several occasions after that.


Two weeks ago I looked at our ArchivesSpace accession records to gather statistics for our annual report and discovered that the accession record mentioned above no longer displayed in accessions browse view and was not returned as a search result when searched for.  The linked instances do still show up in search results, but the system says they are not linked to any other records.


If I try to add a new accession to the system with the same ID number it tells me it cannot add the record because that identifier is already in use.  I have confirmed that the original accession is still listed in the accessions table in the backend database.


Does anyone have thoughts as to why this record was showing up in the staff interface but now is not?  I have not run into this issue with any other records of any kind.  The indexer appears to be working; changes we make- deletions and additions-  are showing up in the staff interface.

________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of archivesspace_users_group-request at lyralists.lyrasis.org <archivesspace_users_group-request at lyralists.lyrasis.org>
Sent: Friday, October 6, 2017 8:20:04 AM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: Archivesspace_Users_Group Digest, Vol 51, Issue 2

Send Archivesspace_Users_Group mailing list submissions to
        archivesspace_users_group at lyralists.lyrasis.org

To subscribe or unsubscribe via the World Wide Web, visit
        http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

or, via email, send a message with subject or body 'help' to
        archivesspace_users_group-request at lyralists.lyrasis.org

You can reach the person managing the list at
        archivesspace_users_group-owner at lyralists.lyrasis.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Archivesspace_Users_Group digest..."


Today's Topics:

   1. Re: ArchivesSpace API - looking for working example of
      'Update a Resource' (Jason Loeffler)
   2. Re: ArchivesSpace API - looking for working example of
      'Update a Resource' (Seth Shaw)
   3. RFP for added container management        functionality in
      ArchivesSpace (Christine Di Bella)
   4. Re: RFP for added container management functionality in
      ArchivesSpace (Detelich, Alicia)
   5. Linked Accessions on Agent Page Not       Displaying (Harmeyer, Neal A)


----------------------------------------------------------------------

Message: 1
Date: Thu, 5 Oct 2017 14:14:04 -0400
From: Jason Loeffler <j at minorscience.com>
To: Archivesspace Users Group
        <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] ArchivesSpace API - looking
        for working example of 'Update a Resource'
Message-ID:
        <CAP4gJsVCYWmom1cUHFFaJDfijT7GwRqwQbuQoMBq-QX-qaFwZg at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Do you have an example of the update you'd like to make? Can you send an
example of the code you're using to update the resource, as well as the
error you're receiving?

Best, Jason

On Thu, Oct 5, 2017 at 2:11 PM, Suszczynski, Jeffrey <
jsuszczynski at library.rochester.edu> wrote:

> Hello, all ?
>
>
>
> I?ve been working with the ArchivesSpace API for a while now, and can
> successfully pull resource records out of a repository, etc.  More
> recently, though, I?ve been trying to update an existing resource within a
> repository, and keep receiving errors.
>
>
>
> Does anyone out there have a working code example of updating a resource
> in ArchivesSpace, using a local file (preferably PHP, but Python or other
> languages could be instructive as well)?  I feel like I?m missing something
> easy and obvious?
>
>
>
> Thanks much in advance!
> jeff
>
>
>
>
>
> Jeff Suszczynski
>
> Web Applications Programmer, River Campus Libraries
>
> University of Rochester
>
>
>
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171005/d80c033a/attachment-0001.html>

------------------------------

Message: 2
Date: Thu, 5 Oct 2017 11:21:47 -0700
From: Seth Shaw <seth.shaw at unlv.edu>
To: Archivesspace Users Group
        <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] ArchivesSpace API - looking
        for working example of 'Update a Resource'
Message-ID:
        <CANuEgP7VU-cmtOYqUfLinfG6gd33tEd9BOXc-6_qFWWdDo7+Jw at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

See Noah Huffman's blog post on this topic (
https://blogs.library.duke.edu/bitstreams/2016/09/21/archivesspace-api-fun/)
and the associated scripts on github (
https://github.com/duke-libraries/archivesspace-duke-scripts/tree/master/python
).

Another example of updating a simple field (EAD ID) that I've written can
be found at
https://github.com/seth-shaw-unlv/small-stuff/blob/master/as-coll-mint/as_coll_mint.py


On Thu, Oct 5, 2017 at 11:11 AM, Suszczynski, Jeffrey <
jsuszczynski at library.rochester.edu> wrote:

> Hello, all ?
>
>
>
> I?ve been working with the ArchivesSpace API for a while now, and can
> successfully pull resource records out of a repository, etc.  More
> recently, though, I?ve been trying to update an existing resource within a
> repository, and keep receiving errors.
>
>
>
> Does anyone out there have a working code example of updating a resource
> in ArchivesSpace, using a local file (preferably PHP, but Python or other
> languages could be instructive as well)?  I feel like I?m missing something
> easy and obvious?
>
>
>
> Thanks much in advance!
> jeff
>
>
>
>
>
> Jeff Suszczynski
>
> Web Applications Programmer, River Campus Libraries
>
> University of Rochester
>
>
>
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171005/34774a2e/attachment-0001.html>

------------------------------

Message: 3
Date: Thu, 5 Oct 2017 18:40:23 +0000
From: Christine Di Bella <christine.dibella at lyrasis.org>
To: Archivesspace Users Group
        <archivesspace_users_group at lyralists.lyrasis.org>, Archivesspace
        Member Reps <archivesspace_member_reps at lyralists.lyrasis.org>,
        "archivesspace_tac_uac at lyralists.lyrasis.org"
        <archivesspace_tac_uac at lyralists.lyrasis.org>
Cc: ArchivesSpace Board of Trustees mail list
        <archivesspace_bot_members at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] RFP for added container
        management      functionality in ArchivesSpace
Message-ID:
        <MWHPR08MB3456FB0664676FF6116F8399F1700 at MWHPR08MB3456.namprd08.prod.outlook.com>

Content-Type: text/plain; charset="us-ascii"

Hello ArchivesSpace members,

ArchivesSpace is seeking proposals from individuals or firms interested in providing development for a limited scope project to add functionality to the container management area of the application. We are prioritizing this work for engagement of an outside contractor based on expressed interest from a number of members, including one that may have funding to pay for it. Please feel free to forward this RFP on to people you think may be interested and qualified to do this work.

We are asking that people please email proposals to me (christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>) by October 27, 2017. Proposals should include a proposed action plan, pricing, timeline, names and contact information for at least two client references, and examples of relevant work in ArchivesSpace or other applications. If people have questions about the RFP, feel free to send them my way as well. Laney can answer technical questions about the application and how delivery of code would work.

Issuing RFPs for specific projects is another strategy we are using to diversify our pool of available developers and continue to making substantial forward progress on the application. If you have any questions, or if you have suggestions for projects that may be particularly appropriate for this type of treatment, please just let us know.

Thanks,
Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)

[ASpaceOrgHomeMedium]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171005/6e170c80/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 6608 bytes
Desc: image002.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171005/6e170c80/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ASpaceContainer Features RFP201710.pdf
Type: application/pdf
Size: 143039 bytes
Desc: ASpaceContainer Features RFP201710.pdf
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171005/6e170c80/attachment-0001.pdf>

------------------------------

Message: 4
Date: Thu, 5 Oct 2017 20:15:52 +0000
From: "Detelich, Alicia" <alicia.detelich at yale.edu>
To: Archivesspace Users Group
        <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] RFP for added container
        management functionality in ArchivesSpace
Message-ID:
        <MWHPR08MB34856CD1F8717B521388FF318E700 at MWHPR08MB3485.namprd08.prod.outlook.com>

Content-Type: text/plain; charset="us-ascii"

Hi Christine,

Thank you for sending this. It seems like an exciting project, and many of the listed features are much-needed. I wonder, though, about the advisability of adding the "ability to create top containers independent of specific material records" - https://archivesspace.atlassian.net/browse/AR-1874. You can already do this via the API - in fact, you have to create unlinked top containers before you can link them to material description records. This is less than ideal, as it adds extra steps to the process - after creating the top containers, you then have to pull those top container URIs and link them to the material descriptions using a different endpoint.

If the goal is to create top containers in bulk (and then link them to descriptions) via the staff interface, wouldn't it make more sense, as the JIRA ticket above notes, to add that ability within a material description record or RDE (https://archivesspace.atlassian.net/browse/AR-1873), rather than to enable the potential proliferation of unlinked containers? It seems like this could lead to all kinds of confusion and messy data in ArchivesSpace, especially if there are multiple unlinked containers with the same container profile, indicator, etc. I think it might be better to solve the underlying issue rather than write a workaround into the application.

Alicia

---
Alicia Detelich
Archivist
Manuscripts and Archives
Yale University Libraries
alicia.detelich at yale.edu

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Christine Di Bella
Sent: Thursday, October 5, 2017 2:40 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>; Archivesspace Member Reps <archivesspace_member_reps at lyralists.lyrasis.org>; archivesspace_tac_uac at lyralists.lyrasis.org
Cc: ArchivesSpace Board of Trustees mail list <archivesspace_bot_members at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] RFP for added container management functionality in ArchivesSpace

Hello ArchivesSpace members,

ArchivesSpace is seeking proposals from individuals or firms interested in providing development for a limited scope project to add functionality to the container management area of the application. We are prioritizing this work for engagement of an outside contractor based on expressed interest from a number of members, including one that may have funding to pay for it. Please feel free to forward this RFP on to people you think may be interested and qualified to do this work.

We are asking that people please email proposals to me (christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>) by October 27, 2017. Proposals should include a proposed action plan, pricing, timeline, names and contact information for at least two client references, and examples of relevant work in ArchivesSpace or other applications. If people have questions about the RFP, feel free to send them my way as well. Laney can answer technical questions about the application and how delivery of code would work.

Issuing RFPs for specific projects is another strategy we are using to diversify our pool of available developers and continue to making substantial forward progress on the application. If you have any questions, or if you have suggestions for projects that may be particularly appropriate for this type of treatment, please just let us know.

Thanks,
Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)

[ASpaceOrgHomeMedium]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171005/ae009cec/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 4074 bytes
Desc: image002.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171005/ae009cec/attachment-0001.jpg>

------------------------------

Message: 5
Date: Fri, 6 Oct 2017 13:19:56 +0000
From: "Harmeyer, Neal A" <harmeyna at purdue.edu>
To: Archivesspace Users Group
        <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Linked Accessions on Agent Page
        Not     Displaying
Message-ID: <c6d394633290457292f656edf6a58be3 at wppexc09.purdue.lcl>
Content-Type: text/plain; charset="us-ascii"

Hello everyone,

It appears accessions that have a linked agent record are not displaying on the Agent's individual page in the public interface. All collections associated with the agents, whether as a source, subject, or creator, do display on the agent page as Related Collections and/or Records-just not accessions. I have made certain the accessions in question are enabled for publication and discoverable in the public interface via search/browse, so it's not that the accessions are hidden from public view. I've highlighted an example in the attached screenshots where an agent with 13 linked accessions/collections combined in the database gives the false impression there is only a single collection associated with that agent when landing on the agent page.

Any chance I'm missing something? Or is there a reason accessions do not appear on an agent page? Purdue would like to see published accessions also appear on the page of an agent in the public interface.

We're using version 2.1.2.

Thank you,
Neal
--
Neal Harmeyer
Digital Archivist
Archives and Special Collections
Purdue University Libraries
harmeyna at purdue.edu<mailto:harmeyna at purdue.edu>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171006/70361b95/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2-accessions-display-agents-single-unprocessed-agent-linked.JPG
Type: image/jpeg
Size: 97442 bytes
Desc: 2-accessions-display-agents-single-unprocessed-agent-linked.JPG
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171006/70361b95/attachment.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 3-accessions-display-agents-name-page-related-materials.JPG
Type: image/jpeg
Size: 289215 bytes
Desc: 3-accessions-display-agents-name-page-related-materials.JPG
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171006/70361b95/attachment-0001.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 1-accessions-display-agents-allresults.JPG
Type: image/jpeg
Size: 223113 bytes
Desc: 1-accessions-display-agents-allresults.JPG
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171006/70361b95/attachment-0002.jpe>

------------------------------

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


End of Archivesspace_Users_Group Digest, Vol 51, Issue 2
********************************************************

From abwick at umn.edu  Tue Oct 10 16:38:41 2017
From: abwick at umn.edu (Amanda Wick)
Date: Tue, 10 Oct 2017 15:38:41 -0500
Subject: [Archivesspace_Users_Group] ArchivesSpace Community Survey
Message-ID: <CAD2sC+G9kxAjn4y7N=5Pp=6+GUCOtpNqizHsmYY1UOOG8Z8xPQ@mail.gmail.com>

Hello fellow ArchivesSpace users,

My colleagues at the University of Minnesota and I are working on a series
of articles for publication about our experience implementing
ArchivesSpace. As such, we'd like to compare our experience with other
ArchivesSpace community members via a web-based survey.

*Survey Details*:

   - The survey should take approximately 15-20 minutes to complete
   depending on length of any long-form answers.
   - You may start, stop, and return to the survey at any time that the
   survey is open.
   - All responses will be anonymized for research purposes and the dataset
   will be made available on request for future studies.
   - No questions are required and we ask that you complete the sections
   that are applicable to your specific institution.
   - Please try to limit responses to one respondent per institution.


If you'd like to participate in this survey, please click here
<https://umn.qualtrics.com/jfe/form/SV_4NiTHB6ZYJDSlaR>.

If you have any questions about the survey or subsequent research, please
contact Amanda Wick at abwick at umn.edu.

Best,
Amanda

-- 

Amanda Wick, Archivist
Special Collections and Rare Books
Charles Babbage Institute (Interim)

Elmer L. Andersen Library, Suite 211
University of Minnesota Libraries
222 - 21st Avenue South
Minneapolis, MN 55455
*Tel*: 612-625-4867
*Email*: abwick at umn.edu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171010/320b3d93/attachment.html>

From laura.ugleanjackson at unco.edu  Wed Oct 11 12:57:17 2017
From: laura.ugleanjackson at unco.edu (Uglean Jackson, Laura)
Date: Wed, 11 Oct 2017 16:57:17 +0000
Subject: [Archivesspace_Users_Group] ASpace for paging boxes?
Message-ID: <4550D4B2-A6E9-43A4-A748-CDCECA67796B@unco.edu>

Dear ASpace Users,

I?m curious to know if anyone is using ASpace to page boxes (check them in and out). If so, how are you doing this?

We will be using ASpace for stacks management and plan to use our ILS to check boxes in and out. Of course it would be great to only have to use one system for everything. I don?t think ASpace has paging functionality, but am curious to know if anyone has a work-around, built a plug-in, or otherwise figured out how to use ASpace for checking out boxes.

Feel free to respond to the list or contact me directly.

Thank you!
Laura


Laura Uglean Jackson
Special Collections & Archives Librarian
University of Northern Colorado Library
Laura.ugleanjackson at unco.edu<mailto:Laura.ugleanjackson at unco.edu>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171011/b08abb63/attachment.html>

From Joshua.D.Shaw at dartmouth.edu  Wed Oct 11 14:30:11 2017
From: Joshua.D.Shaw at dartmouth.edu (Joshua D. Shaw)
Date: Wed, 11 Oct 2017 18:30:11 +0000
Subject: [Archivesspace_Users_Group] ASpace for paging boxes?
In-Reply-To: <4550D4B2-A6E9-43A4-A748-CDCECA67796B@unco.edu>
References: <4550D4B2-A6E9-43A4-A748-CDCECA67796B@unco.edu>
Message-ID: <CY4PR03MB3077481954B9D6DAF60D8872AB4A0@CY4PR03MB3077.namprd03.prod.outlook.com>

Hi Laura-


We (Dartmouth) are in the very early stages of a project which will (hopefully!) provide the ability to circulate items and to allow patrons to kick off the request process from the PUI frontend. We're planning a plugin type architecture for now that will eventually give us:


1) circulation of any object (checkout, checkin, hold)

2) allow patrons to initiate the circulation/request process, including registration. We have both internal Dartmouth people and tons of non-Dartmouth researchers, so we need a method to authenticate/register any patron.

3) allow staff to mediate the requests - either by modifying a patron request or by adding items on an ad hoc basis (since a bunch of our stuff isn't listed in any system, we'll be allowing a free text-ish field as well for those pesky items)

4) printing of pull slips - dual slips so we get one for the item and one for the shelf

5) allow staff a view of what is currently in use in the reading room and what is on hold.

6) stats! TBD, but breakdown by patron type and collection at least


There's some other bits and pieces, but I think those are the highlights.


Early days at this point, but it'd be great to hear your ideas - and those of anyone else who is interested!


Joshua


PS. You can contact me (joshua.d.shaw at dartmouth.edu) or Peter Carini (peter.carini at dartmouth.edu) directly if that's helpful.

________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Uglean Jackson, Laura <laura.ugleanjackson at unco.edu>
Sent: Wednesday, October 11, 2017 12:57:17 PM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] ASpace for paging boxes?

Dear ASpace Users,

I?m curious to know if anyone is using ASpace to page boxes (check them in and out). If so, how are you doing this?

We will be using ASpace for stacks management and plan to use our ILS to check boxes in and out. Of course it would be great to only have to use one system for everything. I don?t think ASpace has paging functionality, but am curious to know if anyone has a work-around, built a plug-in, or otherwise figured out how to use ASpace for checking out boxes.

Feel free to respond to the list or contact me directly.

Thank you!
Laura


Laura Uglean Jackson
Special Collections & Archives Librarian
University of Northern Colorado Library
Laura.ugleanjackson at unco.edu<mailto:Laura.ugleanjackson at unco.edu>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171011/485dcda5/attachment.html>

From christine.dibella at lyrasis.org  Thu Oct 12 14:53:31 2017
From: christine.dibella at lyrasis.org (Christine Di Bella)
Date: Thu, 12 Oct 2017 18:53:31 +0000
Subject: [Archivesspace_Users_Group] ArchivesSpace v2.2.0 released
Message-ID: <MWHPR08MB3456CCC6BC7576B09DA3E17DF14B0@MWHPR08MB3456.namprd08.prod.outlook.com>

The ArchivesSpace team is pleased to release version 2.2.0!


You can download the new release from Github at https://github.com/archivesspace/archivesspace/releases/tag/v2.2.0. Please see the technical documentation<http://archivesspace.github.io/archivesspace/user/upgrading-to-a-new-release-of-archivesspace/> for information on how to upgrade your ArchivesSpace installations.

We are especially pleased because this release includes two new areas of long-desired functionality contributed by community members:

Tufts University subsidized a new assessment module, based very closely on a community-authored specification and hewing closely to the functionality previously available in Archivists' Toolkit. The development was done by Hudson Molonglo. Dan Santamaria and Adrienne Pruitt took the lead on the Tufts side in working closely with HM developers James Bullen, Mark Triggs, and Payten Giles. They also coordinated putting the module out for wider testing, in which people at institutions including the Smithsonian, Smith College, University of Michigan Special Collections, and the Historical Society of Pennsylvania participated.

Trevor Thornton of North Carolina State University and Noah Huffman of Duke University partnered to create an EAD3 exporter, based on a community-distributed specification. Trevor did the development and Noah did extensive and iterative testing. We are excited to have this first level of support for EAD3 in ArchivesSpace and see this as a building block for additional EAD3 support in future releases. Thanks also to Mark Custer at Yale for providing testing feedback.

Thank you so much to Dan, Adrienne, Trevor, and Noah for all their work in bringing these projects to completion and making the results available to the entire ArchivesSpace community. If your institution would like to get involved in subsidizing or working on development prioritized by the ArchivesSpace community, please get in touch with me or Laney.

This release also includes some bug fixes and improvements contributed by community members Steve Majewski, Chris Fitzpatrick, Mark Cooper, Payten Giles, and Christian von Kleist, as well as development work by our Tech Lead Laney McGlohon.

I want to note that this release does not include improvements to the relevancy ranking for search results in the new Public User Interface (JIRA issues: https://archivesspace.atlassian.net/browse/ANW-201 and https://archivesspace.atlassian.net/browse/AR-1882). Knowing how important this is for many users, we have prioritized it for a fix and been working on it since the tickets were first filed; unfortunately due to the complexity of the problem, we have not yet been able to address it satisfactorily enough to include a fix in this release. Rather than further delay releasing the new functionality that our community members have worked so hard on, we have chosen to put out this release now and will keep working on the PUI indexer issue. We intend to have another minor release, that hopefully includes those improvements, later in October or early in November.

Thanks as always to all who contributed to this release, by identifying needed improvements, writing specifications, writing code, testing, and providing technical support. We truly appreciate all that so many of you do in coordination with the ArchivesSpace team to make each release of the ArchivesSpace application possible.

If you have any question or difficulties upgrading, please just let us know.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)

[ASpaceOrgHomeMedium]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171012/617ccb72/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 6608 bytes
Desc: image002.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171012/617ccb72/attachment.jpg>

From lmcphee at ucsd.edu  Fri Oct 13 10:54:05 2017
From: lmcphee at ucsd.edu (McPhee, Laurel)
Date: Fri, 13 Oct 2017 14:54:05 +0000
Subject: [Archivesspace_Users_Group] ASpace search glitch (staff interface)
Message-ID: <DM5PR04MB0954E5011E1C39B06811DFB1DB480@DM5PR04MB0954.namprd04.prod.outlook.com>

Hello,

I have a puzzling search problem that I can't recreate in the sandbox. We recently upgraded to v2.1.2. General keyword searching works find in the staff interface, but if we enclose any search terms in quotes, for example, "Theatre and Arts Foundation" we get the lovely white screen/bold red text message: We're sorry, but something went wrong, even though we have a collection named Theatre and Arts Foundation Records.  We've tried this with lots of different word combinations that we know should work fine and retrieve results-same error message.

However, if I search for the resource or accession number for any collection in quotes, such as "mss 0152", the correct collection pops right up, so the use of quotes is not a total deal-breaker in our search. I was thinking I'd go to the sandbox and smugly recreate the problem and report it, but using some of the sample collections in there to do quotes-enclosed searches, everything worked perfectly. What could be going wrong at UCSD? Thank you for any insight!

Laurel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171013/fa923549/attachment.html>

From rstanonik at ucsd.edu  Fri Oct 13 12:45:46 2017
From: rstanonik at ucsd.edu (Stanonik, Ronald)
Date: Fri, 13 Oct 2017 16:45:46 +0000
Subject: [Archivesspace_Users_Group] ASpace search glitch (staff
	interface)
In-Reply-To: <DM5PR04MB0954E5011E1C39B06811DFB1DB480@DM5PR04MB0954.namprd04.prod.outlook.com>
References: <DM5PR04MB0954E5011E1C39B06811DFB1DB480@DM5PR04MB0954.namprd04.prod.outlook.com>
Message-ID: <CO2PR04MB2134443CB3F4500F2C333A17D8480@CO2PR04MB2134.namprd04.prod.outlook.com>

Hi,

I'm a system administrator for UCSD Library and I'm attaching a stacktrace from the error that Laurel reported.

I'm forcing a solr reindex (removed Indexer_state) to see if that helps.

Any other suggestion appreciated.

Thanks,

Ron

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of McPhee, Laurel
Sent: Friday, October 13, 2017 7:54 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Cc: Christensen, Marlayna <mkchristensen at ucsd.edu>
Subject: [Archivesspace_Users_Group] ASpace search glitch (staff interface)

Hello,

I have a puzzling search problem that I can't recreate in the sandbox. We recently upgraded to v2.1.2. General keyword searching works find in the staff interface, but if we enclose any search terms in quotes, for example, "Theatre and Arts Foundation" we get the lovely white screen/bold red text message: We're sorry, but something went wrong, even though we have a collection named Theatre and Arts Foundation Records.  We've tried this with lots of different word combinations that we know should work fine and retrieve results-same error message.

However, if I search for the resource or accession number for any collection in quotes, such as "mss 0152", the correct collection pops right up, so the use of quotes is not a total deal-breaker in our search. I was thinking I'd go to the sandbox and smugly recreate the problem and report it, but using some of the sample collections in there to do quotes-enclosed searches, everything worked perfectly. What could be going wrong at UCSD? Thank you for any insight!

Laurel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171013/bb04a69e/attachment.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: FATAL.txt
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171013/bb04a69e/attachment.txt>

From rstanonik at ucsd.edu  Fri Oct 13 14:04:33 2017
From: rstanonik at ucsd.edu (Stanonik, Ronald)
Date: Fri, 13 Oct 2017 18:04:33 +0000
Subject: [Archivesspace_Users_Group] ASpace search glitch
	(staff	interface)
In-Reply-To: <CO2PR04MB2134443CB3F4500F2C333A17D8480@CO2PR04MB2134.namprd04.prod.outlook.com>
References: <DM5PR04MB0954E5011E1C39B06811DFB1DB480@DM5PR04MB0954.namprd04.prod.outlook.com>
 <CO2PR04MB2134443CB3F4500F2C333A17D8480@CO2PR04MB2134.namprd04.prod.outlook.com>
Message-ID: <CO2PR04MB2134164D93FA91451F7F7988D8480@CO2PR04MB2134.namprd04.prod.outlook.com>

I did a little testing and it appears that double quotes fail, but single quotes succeed.
Ron

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Stanonik, Ronald
Sent: Friday, October 13, 2017 9:46 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] ASpace search glitch (staff interface)

Hi,

I'm a system administrator for UCSD Library and I'm attaching a stacktrace from the error that Laurel reported.

I'm forcing a solr reindex (removed Indexer_state) to see if that helps.

Any other suggestion appreciated.

Thanks,

Ron

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of McPhee, Laurel
Sent: Friday, October 13, 2017 7:54 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Cc: Christensen, Marlayna <mkchristensen at ucsd.edu<mailto:mkchristensen at ucsd.edu>>
Subject: [Archivesspace_Users_Group] ASpace search glitch (staff interface)

Hello,

I have a puzzling search problem that I can't recreate in the sandbox. We recently upgraded to v2.1.2. General keyword searching works find in the staff interface, but if we enclose any search terms in quotes, for example, "Theatre and Arts Foundation" we get the lovely white screen/bold red text message: We're sorry, but something went wrong, even though we have a collection named Theatre and Arts Foundation Records.  We've tried this with lots of different word combinations that we know should work fine and retrieve results-same error message.

However, if I search for the resource or accession number for any collection in quotes, such as "mss 0152", the correct collection pops right up, so the use of quotes is not a total deal-breaker in our search. I was thinking I'd go to the sandbox and smugly recreate the problem and report it, but using some of the sample collections in there to do quotes-enclosed searches, everything worked perfectly. What could be going wrong at UCSD? Thank you for any insight!

Laurel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171013/198923c3/attachment.html>

From blake.carver at lyrasis.org  Fri Oct 13 14:39:08 2017
From: blake.carver at lyrasis.org (Blake Carver)
Date: Fri, 13 Oct 2017 18:39:08 +0000
Subject: [Archivesspace_Users_Group] ASpace search
	glitch	(staff	interface)
In-Reply-To: <CO2PR04MB2134164D93FA91451F7F7988D8480@CO2PR04MB2134.namprd04.prod.outlook.com>
References: <DM5PR04MB0954E5011E1C39B06811DFB1DB480@DM5PR04MB0954.namprd04.prod.outlook.com>
 <CO2PR04MB2134443CB3F4500F2C333A17D8480@CO2PR04MB2134.namprd04.prod.outlook.com>,
 <CO2PR04MB2134164D93FA91451F7F7988D8480@CO2PR04MB2134.namprd04.prod.outlook.com>
Message-ID: <BY2PR0801MB1510773F95D8682FA967BD5D9F480@BY2PR0801MB1510.namprd08.prod.outlook.com>

Hi Ron,
Did the reindex finish and it's still throwing that error?
Any errors while indexing?
-Blake


________________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Stanonik, Ronald <rstanonik at ucsd.edu>
Sent: Friday, October 13, 2017 2:04:33 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] ASpace search glitch   (staff  interface)

I did a little testing and it appears that double quotes fail, but single quotes succeed.
Ron

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Stanonik, Ronald
Sent: Friday, October 13, 2017 9:46 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] ASpace search glitch (staff interface)

Hi,

I?m a system administrator for UCSD Library and I?m attaching a stacktrace from the error that Laurel reported.

I?m forcing a solr reindex (removed Indexer_state) to see if that helps.

Any other suggestion appreciated.

Thanks,

Ron

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of McPhee, Laurel
Sent: Friday, October 13, 2017 7:54 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Cc: Christensen, Marlayna <mkchristensen at ucsd.edu<mailto:mkchristensen at ucsd.edu>>
Subject: [Archivesspace_Users_Group] ASpace search glitch (staff interface)

Hello,

I have a puzzling search problem that I can?t recreate in the sandbox. We recently upgraded to v2.1.2. General keyword searching works find in the staff interface, but if we enclose any search terms in quotes, for example, ?Theatre and Arts Foundation? we get the lovely white screen/bold red text message: We?re sorry, but something went wrong, even though we have a collection named Theatre and Arts Foundation Records.  We?ve tried this with lots of different word combinations that we know should work fine and retrieve results?same error message.

However, if I search for the resource or accession number for any collection in quotes, such as ?mss 0152?, the correct collection pops right up, so the use of quotes is not a total deal-breaker in our search. I was thinking I?d go to the sandbox and smugly recreate the problem and report it, but using some of the sample collections in there to do quotes-enclosed searches, everything worked perfectly. What could be going wrong at UCSD? Thank you for any insight!

Laurel

From rstanonik at ucsd.edu  Fri Oct 13 15:02:18 2017
From: rstanonik at ucsd.edu (Stanonik, Ronald)
Date: Fri, 13 Oct 2017 19:02:18 +0000
Subject: [Archivesspace_Users_Group] ASpace
	search	glitch	(staff	interface)
In-Reply-To: <BY2PR0801MB1510773F95D8682FA967BD5D9F480@BY2PR0801MB1510.namprd08.prod.outlook.com>
References: <DM5PR04MB0954E5011E1C39B06811DFB1DB480@DM5PR04MB0954.namprd04.prod.outlook.com>
 <CO2PR04MB2134443CB3F4500F2C333A17D8480@CO2PR04MB2134.namprd04.prod.outlook.com>,
 <CO2PR04MB2134164D93FA91451F7F7988D8480@CO2PR04MB2134.namprd04.prod.outlook.com>
 <BY2PR0801MB1510773F95D8682FA967BD5D9F480@BY2PR0801MB1510.namprd08.prod.outlook.com>
Message-ID: <CO2PR04MB2134918E9C83951608FE5374D8480@CO2PR04MB2134.namprd04.prod.outlook.com>

I believe indexing finished.

I didn't see anything in the log that looked like indexing errors.

The problem is still occurring, double quote surrounding multiple terms fails with " We're sorry, but something went wrong."

Single quotes succeed.

We're running 2.1.2 on RHEL 6.9, using 
java version "1.7.0_40"
Java(TM) SE Runtime Environment (build 1.7.0_40-b43)
Java HotSpot(TM) 64-Bit Server VM (build 24.0-b56, mixed mode)

-----Original Message-----
From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Blake Carver
Sent: Friday, October 13, 2017 11:39 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] ASpace search glitch (staff interface)

Hi Ron,
Did the reindex finish and it's still throwing that error?
Any errors while indexing?
-Blake


________________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Stanonik, Ronald <rstanonik at ucsd.edu>
Sent: Friday, October 13, 2017 2:04:33 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] ASpace search glitch   (staff  interface)

I did a little testing and it appears that double quotes fail, but single quotes succeed.
Ron

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Stanonik, Ronald
Sent: Friday, October 13, 2017 9:46 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] ASpace search glitch (staff interface)

Hi,

I'm a system administrator for UCSD Library and I'm attaching a stacktrace from the error that Laurel reported.

I'm forcing a solr reindex (removed Indexer_state) to see if that helps.

Any other suggestion appreciated.

Thanks,

Ron

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of McPhee, Laurel
Sent: Friday, October 13, 2017 7:54 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Cc: Christensen, Marlayna <mkchristensen at ucsd.edu<mailto:mkchristensen at ucsd.edu>>
Subject: [Archivesspace_Users_Group] ASpace search glitch (staff interface)

Hello,

I have a puzzling search problem that I can't recreate in the sandbox. We recently upgraded to v2.1.2. General keyword searching works find in the staff interface, but if we enclose any search terms in quotes, for example, "Theatre and Arts Foundation" we get the lovely white screen/bold red text message: We're sorry, but something went wrong, even though we have a collection named Theatre and Arts Foundation Records.  We've tried this with lots of different word combinations that we know should work fine and retrieve results-same error message.

However, if I search for the resource or accession number for any collection in quotes, such as "mss 0152", the correct collection pops right up, so the use of quotes is not a total deal-breaker in our search. I was thinking I'd go to the sandbox and smugly recreate the problem and report it, but using some of the sample collections in there to do quotes-enclosed searches, everything worked perfectly. What could be going wrong at UCSD? Thank you for any insight!

Laurel
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

From rstanonik at ucsd.edu  Fri Oct 13 15:07:42 2017
From: rstanonik at ucsd.edu (Stanonik, Ronald)
Date: Fri, 13 Oct 2017 19:07:42 +0000
Subject: [Archivesspace_Users_Group]
	ASpace	search	glitch	(staff	interface)
In-Reply-To: <CO2PR04MB2134918E9C83951608FE5374D8480@CO2PR04MB2134.namprd04.prod.outlook.com>
References: <DM5PR04MB0954E5011E1C39B06811DFB1DB480@DM5PR04MB0954.namprd04.prod.outlook.com>
 <CO2PR04MB2134443CB3F4500F2C333A17D8480@CO2PR04MB2134.namprd04.prod.outlook.com>,
 <CO2PR04MB2134164D93FA91451F7F7988D8480@CO2PR04MB2134.namprd04.prod.outlook.com>
 <BY2PR0801MB1510773F95D8682FA967BD5D9F480@BY2PR0801MB1510.namprd08.prod.outlook.com>
 <CO2PR04MB2134918E9C83951608FE5374D8480@CO2PR04MB2134.namprd04.prod.outlook.com>
Message-ID: <CO2PR04MB2134C0405A6F94911B55B7BFD8480@CO2PR04MB2134.namprd04.prod.outlook.com>

More testing.
Not all multiple term queries fail.

These fail.
"Theatre and Arts Foundation"
"Tunaboat Association"

These succeed
"Alpha Beta"
"One Two Three"

So, maybe something about some of the data?

Ron

-----Original Message-----
From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Stanonik, Ronald
Sent: Friday, October 13, 2017 12:02 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] ASpace search glitch (staff interface)

I believe indexing finished.

I didn't see anything in the log that looked like indexing errors.

The problem is still occurring, double quote surrounding multiple terms fails with " We're sorry, but something went wrong."

Single quotes succeed.

We're running 2.1.2 on RHEL 6.9, using
java version "1.7.0_40"
Java(TM) SE Runtime Environment (build 1.7.0_40-b43) Java HotSpot(TM) 64-Bit Server VM (build 24.0-b56, mixed mode)

-----Original Message-----
From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Blake Carver
Sent: Friday, October 13, 2017 11:39 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] ASpace search glitch (staff interface)

Hi Ron,
Did the reindex finish and it's still throwing that error?
Any errors while indexing?
-Blake


________________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Stanonik, Ronald <rstanonik at ucsd.edu>
Sent: Friday, October 13, 2017 2:04:33 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] ASpace search glitch   (staff  interface)

I did a little testing and it appears that double quotes fail, but single quotes succeed.
Ron

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Stanonik, Ronald
Sent: Friday, October 13, 2017 9:46 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] ASpace search glitch (staff interface)

Hi,

I'm a system administrator for UCSD Library and I'm attaching a stacktrace from the error that Laurel reported.

I'm forcing a solr reindex (removed Indexer_state) to see if that helps.

Any other suggestion appreciated.

Thanks,

Ron

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of McPhee, Laurel
Sent: Friday, October 13, 2017 7:54 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Cc: Christensen, Marlayna <mkchristensen at ucsd.edu<mailto:mkchristensen at ucsd.edu>>
Subject: [Archivesspace_Users_Group] ASpace search glitch (staff interface)

Hello,

I have a puzzling search problem that I can't recreate in the sandbox. We recently upgraded to v2.1.2. General keyword searching works find in the staff interface, but if we enclose any search terms in quotes, for example, "Theatre and Arts Foundation" we get the lovely white screen/bold red text message: We're sorry, but something went wrong, even though we have a collection named Theatre and Arts Foundation Records.  We've tried this with lots of different word combinations that we know should work fine and retrieve results-same error message.

However, if I search for the resource or accession number for any collection in quotes, such as "mss 0152", the correct collection pops right up, so the use of quotes is not a total deal-breaker in our search. I was thinking I'd go to the sandbox and smugly recreate the problem and report it, but using some of the sample collections in there to do quotes-enclosed searches, everything worked perfectly. What could be going wrong at UCSD? Thank you for any insight!

Laurel
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

From blake.carver at lyrasis.org  Fri Oct 13 15:19:31 2017
From: blake.carver at lyrasis.org (Blake Carver)
Date: Fri, 13 Oct 2017 19:19:31 +0000
Subject: [Archivesspace_Users_Group]
	ASpace	search	glitch	(staff	interface)
In-Reply-To: <CO2PR04MB2134C0405A6F94911B55B7BFD8480@CO2PR04MB2134.namprd04.prod.outlook.com>
References: <DM5PR04MB0954E5011E1C39B06811DFB1DB480@DM5PR04MB0954.namprd04.prod.outlook.com>
 <CO2PR04MB2134443CB3F4500F2C333A17D8480@CO2PR04MB2134.namprd04.prod.outlook.com>,
 <CO2PR04MB2134164D93FA91451F7F7988D8480@CO2PR04MB2134.namprd04.prod.outlook.com>
 <BY2PR0801MB1510773F95D8682FA967BD5D9F480@BY2PR0801MB1510.namprd08.prod.outlook.com>
 <CO2PR04MB2134918E9C83951608FE5374D8480@CO2PR04MB2134.namprd04.prod.outlook.com>,
 <CO2PR04MB2134C0405A6F94911B55B7BFD8480@CO2PR04MB2134.namprd04.prod.outlook.com>
Message-ID: <BY2PR0801MB1510F7C32A58AC8DB68B12319F480@BY2PR0801MB1510.namprd08.prod.outlook.com>

It might be something in the data, in the log you attached I see:

>> field "finding_aid_filing_title" was indexed without position data; cannot run PhraseQuery (term=tunaboat)

That isn't great. If there's no other errors when it reindexed, that might me something in the data.

________________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Stanonik, Ronald <rstanonik at ucsd.edu>
Sent: Friday, October 13, 2017 3:07:42 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group]        ASpace  search  glitch  (staff  interface)

More testing.
Not all multiple term queries fail.

These fail.
"Theatre and Arts Foundation"
"Tunaboat Association"

These succeed
"Alpha Beta"
"One Two Three"

So, maybe something about some of the data?

Ron

-----Original Message-----
From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Stanonik, Ronald
Sent: Friday, October 13, 2017 12:02 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] ASpace search glitch (staff interface)

I believe indexing finished.

I didn't see anything in the log that looked like indexing errors.

The problem is still occurring, double quote surrounding multiple terms fails with " We're sorry, but something went wrong."

Single quotes succeed.

We're running 2.1.2 on RHEL 6.9, using
java version "1.7.0_40"
Java(TM) SE Runtime Environment (build 1.7.0_40-b43) Java HotSpot(TM) 64-Bit Server VM (build 24.0-b56, mixed mode)

-----Original Message-----
From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Blake Carver
Sent: Friday, October 13, 2017 11:39 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] ASpace search glitch (staff interface)

Hi Ron,
Did the reindex finish and it's still throwing that error?
Any errors while indexing?
-Blake


________________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Stanonik, Ronald <rstanonik at ucsd.edu>
Sent: Friday, October 13, 2017 2:04:33 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] ASpace search glitch   (staff  interface)

I did a little testing and it appears that double quotes fail, but single quotes succeed.
Ron

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Stanonik, Ronald
Sent: Friday, October 13, 2017 9:46 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] ASpace search glitch (staff interface)

Hi,

I'm a system administrator for UCSD Library and I'm attaching a stacktrace from the error that Laurel reported.

I'm forcing a solr reindex (removed Indexer_state) to see if that helps.

Any other suggestion appreciated.

Thanks,

Ron

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of McPhee, Laurel
Sent: Friday, October 13, 2017 7:54 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Cc: Christensen, Marlayna <mkchristensen at ucsd.edu<mailto:mkchristensen at ucsd.edu>>
Subject: [Archivesspace_Users_Group] ASpace search glitch (staff interface)

Hello,

I have a puzzling search problem that I can't recreate in the sandbox. We recently upgraded to v2.1.2. General keyword searching works find in the staff interface, but if we enclose any search terms in quotes, for example, "Theatre and Arts Foundation" we get the lovely white screen/bold red text message: We're sorry, but something went wrong, even though we have a collection named Theatre and Arts Foundation Records.  We've tried this with lots of different word combinations that we know should work fine and retrieve results-same error message.

However, if I search for the resource or accession number for any collection in quotes, such as "mss 0152", the correct collection pops right up, so the use of quotes is not a total deal-breaker in our search. I was thinking I'd go to the sandbox and smugly recreate the problem and report it, but using some of the sample collections in there to do quotes-enclosed searches, everything worked perfectly. What could be going wrong at UCSD? Thank you for any insight!

Laurel
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

From rstanonik at ucsd.edu  Fri Oct 13 18:16:13 2017
From: rstanonik at ucsd.edu (Stanonik, Ronald)
Date: Fri, 13 Oct 2017 22:16:13 +0000
Subject: [Archivesspace_Users_Group]
	ASpace	search	glitch	(staff	interface)
In-Reply-To: <BY2PR0801MB1510F7C32A58AC8DB68B12319F480@BY2PR0801MB1510.namprd08.prod.outlook.com>
References: <DM5PR04MB0954E5011E1C39B06811DFB1DB480@DM5PR04MB0954.namprd04.prod.outlook.com>
 <CO2PR04MB2134443CB3F4500F2C333A17D8480@CO2PR04MB2134.namprd04.prod.outlook.com>,
 <CO2PR04MB2134164D93FA91451F7F7988D8480@CO2PR04MB2134.namprd04.prod.outlook.com>
 <BY2PR0801MB1510773F95D8682FA967BD5D9F480@BY2PR0801MB1510.namprd08.prod.outlook.com>
 <CO2PR04MB2134918E9C83951608FE5374D8480@CO2PR04MB2134.namprd04.prod.outlook.com>,
 <CO2PR04MB2134C0405A6F94911B55B7BFD8480@CO2PR04MB2134.namprd04.prod.outlook.com>
 <BY2PR0801MB1510F7C32A58AC8DB68B12319F480@BY2PR0801MB1510.namprd08.prod.outlook.com>
Message-ID: <CO2PR04MB2134C115F16168B95D966A1ED8480@CO2PR04MB2134.namprd04.prod.outlook.com>

No problems when I used Advanced Search (click on down arrow to right of search box).

"tunaboat association", which failed before, succeeded for every search type (Creator, Identifier, ...).

It's a clue, but I don't know what it means.

Ron

-----Original Message-----
From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Blake Carver
Sent: Friday, October 13, 2017 12:20 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] ASpace search glitch (staff interface)

It might be something in the data, in the log you attached I see:

>> field "finding_aid_filing_title" was indexed without position data; cannot run PhraseQuery (term=tunaboat)

That isn't great. If there's no other errors when it reindexed, that might me something in the data.

________________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Stanonik, Ronald <rstanonik at ucsd.edu>
Sent: Friday, October 13, 2017 3:07:42 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group]        ASpace  search  glitch  (staff  interface)

More testing.
Not all multiple term queries fail.

These fail.
"Theatre and Arts Foundation"
"Tunaboat Association"

These succeed
"Alpha Beta"
"One Two Three"

So, maybe something about some of the data?

Ron

-----Original Message-----
From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Stanonik, Ronald
Sent: Friday, October 13, 2017 12:02 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] ASpace search glitch (staff interface)

I believe indexing finished.

I didn't see anything in the log that looked like indexing errors.

The problem is still occurring, double quote surrounding multiple terms fails with " We're sorry, but something went wrong."

Single quotes succeed.

We're running 2.1.2 on RHEL 6.9, using
java version "1.7.0_40"
Java(TM) SE Runtime Environment (build 1.7.0_40-b43) Java HotSpot(TM) 64-Bit Server VM (build 24.0-b56, mixed mode)

-----Original Message-----
From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Blake Carver
Sent: Friday, October 13, 2017 11:39 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] ASpace search glitch (staff interface)

Hi Ron,
Did the reindex finish and it's still throwing that error?
Any errors while indexing?
-Blake


________________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Stanonik, Ronald <rstanonik at ucsd.edu>
Sent: Friday, October 13, 2017 2:04:33 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] ASpace search glitch   (staff  interface)

I did a little testing and it appears that double quotes fail, but single quotes succeed.
Ron

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Stanonik, Ronald
Sent: Friday, October 13, 2017 9:46 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] ASpace search glitch (staff interface)

Hi,

I'm a system administrator for UCSD Library and I'm attaching a stacktrace from the error that Laurel reported.

I'm forcing a solr reindex (removed Indexer_state) to see if that helps.

Any other suggestion appreciated.

Thanks,

Ron

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of McPhee, Laurel
Sent: Friday, October 13, 2017 7:54 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Cc: Christensen, Marlayna <mkchristensen at ucsd.edu<mailto:mkchristensen at ucsd.edu>>
Subject: [Archivesspace_Users_Group] ASpace search glitch (staff interface)

Hello,

I have a puzzling search problem that I can't recreate in the sandbox. We recently upgraded to v2.1.2. General keyword searching works find in the staff interface, but if we enclose any search terms in quotes, for example, "Theatre and Arts Foundation" we get the lovely white screen/bold red text message: We're sorry, but something went wrong, even though we have a collection named Theatre and Arts Foundation Records.  We've tried this with lots of different word combinations that we know should work fine and retrieve results-same error message.

However, if I search for the resource or accession number for any collection in quotes, such as "mss 0152", the correct collection pops right up, so the use of quotes is not a total deal-breaker in our search. I was thinking I'd go to the sandbox and smugly recreate the problem and report it, but using some of the sample collections in there to do quotes-enclosed searches, everything worked perfectly. What could be going wrong at UCSD? Thank you for any insight!

Laurel
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

From CurbowJ at bvu.edu  Mon Oct 16 11:49:54 2017
From: CurbowJ at bvu.edu (Joan Curbow)
Date: Mon, 16 Oct 2017 15:49:54 +0000
Subject: [Archivesspace_Users_Group] Searching within a large collection
Message-ID: <CY1PR05MB23620347B0C07C17159F47C6B54F0@CY1PR05MB2362.namprd05.prod.outlook.com>

I hesitate to even ask this question, because I have a nagging feeling that it is a question whose answer is obvious, and I?ll feel really stupid for asking it, but here goes.

I have a large collection of university photographs, and one of my series of Alumni and Former Students. I have files for individual students, so you can imagine that this collection gets large and unwieldy. Sometimes I want to be able to search within this collection, but I don?t understand if there?s a way to do that. Is there? Is this even a thing? Does anyone else ever wish for that ability?

Sincerely,

Joan Curbow
Reference Librarian and Archivist
Buena Vista University Library
Buena Vista University
610 West Fourth Street
Storm Lake, Iowa  50588
712.749.2094
www.library.bvu.edu??




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171016/c420d5f7/attachment.html>

From CurbowJ at bvu.edu  Mon Oct 16 14:16:47 2017
From: CurbowJ at bvu.edu (Joan Curbow)
Date: Mon, 16 Oct 2017 18:16:47 +0000
Subject: [Archivesspace_Users_Group] I should have been more clear in my
	question
Message-ID: <CY1PR05MB236283E4383011A97FEBC594B54F0@CY1PR05MB2362.namprd05.prod.outlook.com>

I was specifically asking if one could search within a collection in the staff interface, not the PUI.

Sincerely,

Joan Curbow
Reference Librarian and Archivist
Buena Vista University Library
Buena Vista University
610 West Fourth Street
Storm Lake, Iowa  50588
712.749.2094
www.library.bvu.edu??




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171016/23bd5da7/attachment.html>

From mark.custer at yale.edu  Mon Oct 16 15:07:29 2017
From: mark.custer at yale.edu (Custer, Mark)
Date: Mon, 16 Oct 2017 19:07:29 +0000
Subject: [Archivesspace_Users_Group] I should have been more clear in
	my	question
In-Reply-To: <CY1PR05MB236283E4383011A97FEBC594B54F0@CY1PR05MB2362.namprd05.prod.outlook.com>
References: <CY1PR05MB236283E4383011A97FEBC594B54F0@CY1PR05MB2362.namprd05.prod.outlook.com>
Message-ID: <BN3PR08MB1303000A67EE439D75E849CF8C4F0@BN3PR08MB1303.namprd08.prod.outlook.com>

Hi, Joan.

In the PUI, yes, you can do this.

In the Staff Interface, you can also do this, but the approach isn?t as obvious.  But you can return every record that?s part of a specific resource by searching for its URI fragment.  For example, in http://test.archivesspace.org, there?s a Repository named GoneRepo, and in that repository there?s a resource named Aperture Labs Records.  That resource has a URI fragment of ?resources/45?, which is unique in that instance of ArchivesSpace.  If you search for that fragment in quotes, like so, http://test.archivesspace.org/search?utf8=%E2%9C%93&q=%22resources%2F45%22, then you?ll get all of the records associated with that collection.  You can then filter by ?archival objects,? for instance, if you only want all the components that are part of that collection, rather than top container, event, and other record types.

Does that help?

Mark



From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Joan Curbow
Sent: Monday, 16 October, 2017 2:17 PM
To: Archivesspace Users Group (archivesspace_users_group at lyralists.lyrasis.org) <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] I should have been more clear in my question

I was specifically asking if one could search within a collection in the staff interface, not the PUI.

Sincerely,

Joan Curbow
Reference Librarian and Archivist
Buena Vista University Library
Buena Vista University
610 West Fourth Street
Storm Lake, Iowa  50588
712.749.2094
www.library.bvu.edu<http://www.library.bvu.edu>??




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171016/389fe264/attachment.html>

From Christine.Kim at lyrasis.org  Mon Oct 16 15:09:30 2017
From: Christine.Kim at lyrasis.org (Christine Kim)
Date: Mon, 16 Oct 2017 19:09:30 +0000
Subject: [Archivesspace_Users_Group] ArchivesSpace Update - October 2017
Message-ID: <MWHPR08MB24954C35FA276C2BE3510339F54F0@MWHPR08MB2495.namprd08.prod.outlook.com>

[ASpaceOrgHome.jpg]

October 2017 Update

This month's update includes a variety of highlights. We have a pre-release version of the Archivists' Toolkit migration tool that migrates directly into ArchivesSpace version 2.1.2, and we need help testing this before it goes live. We're still accepting applications for a new DevOps Specialist to support the ArchivesSpace community. And read on for details on the upcoming PUI implementation strategies webinar on October 26!


Development

The ArchivesSpace team is pleased to release version 2.2.0!

You can download the new release from Github at https://github.com/archivesspace/archivesspace/releases/tag/v2.2.0. Please see the technical documentation<http://archivesspace.github.io/archivesspace/user/upgrading-to-a-new-release-of-archivesspace/> for information on how to upgrade your ArchivesSpace installations.

We are especially pleased because this release includes two new areas of long-desired functionality contributed by community members:

Tufts University subsidized a new assessment module, based very closely on a community-authored specification and hewing closely to the functionality previously available in Archivists' Toolkit. The development was done by Hudson Molonglo. Dan Santamaria and Adrienne Pruitt took the lead on the Tufts side in working closely with HM developers James Bullen, Mark Triggs, and Payten Giles. They also coordinated putting the module out for wider testing, in which people at institutions including the Smithsonian, Smith College, University of Michigan Special Collections, and the Historical Society of Pennsylvania participated.

Trevor Thornton of North Carolina State University and Noah Huffman of Duke University partnered to create an EAD3 exporter, based on a community-distributed specification. Trevor did the development and Noah did extensive and iterative testing. We are excited to have this first level of support for EAD3 in ArchivesSpace and see this as a building block for additional EAD3 support in future releases. Thanks also to Mark Custer at Yale for providing testing feedback.

Thank you so much to Dan, Adrienne, Trevor, and Noah for all their work in bringing these projects to completion and making the results available to the entire ArchivesSpace community. If your institution would like to get involved in subsidizing or working on development prioritized by the ArchivesSpace community, please get in touch with me or Laney.

This release also includes some bug fixes and improvements contributed by community members Steve Majewski, Chris Fitzpatrick, Mark Cooper, Payten Giles, and Christian von Kleist, as well as development work by our Tech Lead Laney McGlohon.

I want to note that this release does not include improvements to the relevancy ranking for search results in the new Public User Interface (JIRA issues: https://archivesspace.atlassian.net/browse/ANW-201 and https://archivesspace.atlassian.net/browse/AR-1882). Knowing how important this is for many users, we have prioritized it for a fix and been working on it since the tickets were first filed; unfortunately due to the complexity of the problem, we have not yet been able to address it satisfactorily enough to include a fix in this release. Rather than further delay releasing the new functionality that our community members have worked so hard on, we have chosen to put out this release now and will keep working on the PUI indexer issue. We intend to have another minor release, that hopefully includes those improvements, later in October or early in November.

Thanks as always to all who contributed to this release, by identifying needed improvements, writing specifications, writing code, testing, and providing technical support. We truly appreciate all that so many of you do in coordination with the ArchivesSpace team to make each release of the ArchivesSpace application possible.


Webinar on the new PUI: October 26, 1-2:30 EST

Join us on October 26 as we take a close look at a variety of implementation strategies on the new ArchivesSpace PUI!

Mark Custer (Archivist and Metadata Coordinator, Yale University) and Susan Pyzynski (Associate Librarian of Houghton Library for Technical Services, Harvard University) were deeply entrenched in the public interface as they led the community effort to shape this essential access point for archival collections. Now they have moved onto their next great challenge -- implementing the PUI at their own institutions. Mark and Susan will each share the strategies they have created to roll out the new PUI. Both institutions aim to be using the new PUI by early next year.

Grand Valley State University has been using the ArchivesSpace PUI since 2014 and have already rolled out the new public interface. Annie Benefiel (Archivist for Collection Management, GVSU) and Leigh Rupinski (Archivist for Public Services & Community Engagement, GVSU) will share valuable insight on how the PUI has affected their day-to-day responsibilities as well as public reception and adapting their instruction for students and researchers.

Please join us on October 26 at 1-2:30 EST as Mark, Susan, Annie, and Leigh as they share their experiences. Please feel free to bring any questions you have on the new public interface!

The webinar will be available through: http://lyrasis.adobeconnect.com/rnz7zrtmy04h/ and the recording will be available at a later date.

No registration required. The session is limited to the first 100 participants. Please feel free to host a webinar viewing group.

If you have any questions about this webinar, please contact Kim at christine.kim at lyrasis.org<mailto:christine.kim at lyrasis.org>. We look forward to seeing you at the webinar!


Call for Testers - Archivists' Toolkit to ArchivesSpace Migration

The ArchivesSpace Program Team is looking for people who haven't yet migrated from Archivists' Toolkit to ArchivesSpace to test updates to the Archivists' Toolkit migration tool.

We have developed a pre-release version of the Archivists' Toolkit migration tool that migrates directly into ArchivesSpace version 2.1.2. In addition to the updates we have already made, we are planning to add the assessment information from AT to the migration tool once the assessment module is available in a production release of ArchivesSpace.

If you're interested, please email Laney at laney.mcglohon at lyrasis.org<mailto:laney.mcglohon at lyrasis.org>.


Request for Proposals for Container Management Development

ArchivesSpace is seeking proposals from individuals or firms interested in providing development for a limited scope project to add functionality to the container management area of the application. We are prioritizing this work for engagement of an outside contractor based on expressed interest from a number of members, including one that may have funding to pay for it. Please feel free to forward this RFP on to people you think may be interested and qualified to do this work.

We are asking that people please email proposals to Christine (christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>) by October 27, 2017. Proposals should include a proposed action plan, pricing, timeline, names and contact information for at least two client references, and examples of relevant work in ArchivesSpace or other applications. If people have questions about the RFP, feel free to send them my way as well. Laney can answer technical questions about the application and how delivery of code would work.

Issuing RFPs for specific projects is another strategy we are using to diversify our pool of available developers and continue to making substantial forward progress on the application. If you have any questions, or if you have suggestions for projects that may be particularly appropriate for this type of treatment, please just let us know.


We're hiring! DevOps Specialist supporting ArchivesSpace

Announced in last month's update, we are still accepting applications for the DevOps Specialist position supporting the ArchivesSpace community and the ArchivesSpace program team.

LYRASIS, the organizational home for ArchivesSpace, recently approved an additional staff position based in Technology Services to support ArchivesSpace technical needs. The position description can be found at https://www.lyrasis.org/job/Pages/LYRASIS-Positions.aspx. While the position will report to the Director of Technology Services, the person in the position will work closely with the ArchivesSpace program team to provide technical support for ArchivesSpace members as well as coding and other technical assistance for the application. Over time the person will have additional responsibilities for supporting LYRASIS hosting clients.

This position is ideal for someone who is familiar with ArchivesSpace or other archival/collection management systems and likes to help people with their technical questions. Previous experience with multiple platforms (Linux, Mac, Windows), MySQL, Java, Ruby, and Apache Solr is required.

We are excited about this additional support within the organizational home for ArchivesSpace technical needs. If you are interested in applying, or know someone who is, applications, including a cover letter and resume, are being accepted via email at human.resources at lyrasis.org<mailto:human.resources at lyrasis.org>. If you have questions about the position, feel free to reach out to Christine (christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>) or Laney (laney.mcglohon at lyrasis.org<mailto:laney.mcglohon at lyrasis.org>).


Introducing a new blog series: All About Community!

ArchivesSpace is community-supported software. But what does that mean? With a current program staff of only 3.75 FTE, ArchivesSpace owes its dynamic growth primarily to the active user community, currently over 300 members strong.

Without this community, the progress ArchivesSpace has made since its first release in 2013 could not be possible. So how do we all work together?

All About Community is a blog series that highlights the many teams and groups that contribute to the growth and development of ArchivesSpace. This series aims to provide insight on how our diverse community comes together with a shared vision to preserve permanently valuable records and provide access to our researchers.

Every month, we'll take a close look at each team, group, council, etc to highlight their major accomplishments and activities. Follow along: http://archivesspace.org/category/all-about-community/

Have ideas, questions, feedback, or your own stories you'd like to share? Email Kim at christine.kim at lyrasis.org<mailto:christine.kim at lyrasis.org>.


Membership Update

Our new members since September 21 include:

  *   University of Mary Washington
  *   Organ Historical Society Library and Archives
  *   Tyrrell Historical Society
  *   College of Charleston
  *   Northwest Texas Conference of the United Methodist Church

New educational member:

  *   Cairo University

As of October 12, we have 332 General members, 16 Educational Program members, and 3 Registered Service Providers. If you are interested in your institution becoming a member of ArchivesSpace, please email us at ArchivesSpaceHome at lyrasis.org<mailto:ArchivesSpaceHome at lyrasis.org> for more information.


ArchivesSpace monthly updates provide news about ArchivesSpace community and program activities and are sent to our member listservs, the ArchivesSpace Google Group, and SAA's Collection Management Tools roundtable listserv, as well as being posted on the ArchivesSpace website. Please feel free to share this update with people you know who have an interest in ArchivesSpace but may not be on one of these lists.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171016/b7380f91/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 20006 bytes
Desc: image001.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171016/b7380f91/attachment.jpg>

From mark.custer at yale.edu  Mon Oct 16 15:13:21 2017
From: mark.custer at yale.edu (Custer, Mark)
Date: Mon, 16 Oct 2017 19:13:21 +0000
Subject: [Archivesspace_Users_Group] I should have been more clear
	in	my	question
In-Reply-To: <BN3PR08MB1303000A67EE439D75E849CF8C4F0@BN3PR08MB1303.namprd08.prod.outlook.com>
References: <CY1PR05MB236283E4383011A97FEBC594B54F0@CY1PR05MB2362.namprd05.prod.outlook.com>
 <BN3PR08MB1303000A67EE439D75E849CF8C4F0@BN3PR08MB1303.namprd08.prod.outlook.com>
Message-ID: <BN3PR08MB1303532ED8C63045406533D68C4F0@BN3PR08MB1303.namprd08.prod.outlook.com>

I should add that I think that there should be an easier, user-friendly way to do this in the staff interface, though!!!  Searching for the URI fragment just happens to be my current workaround.

I wonder if anyone else has other solutions for this right now, especially a working plugin that could become part of the core code?



From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Custer, Mark
Sent: Monday, 16 October, 2017 3:07 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] I should have been more clear in my question

Hi, Joan.

In the PUI, yes, you can do this.

In the Staff Interface, you can also do this, but the approach isn?t as obvious.  But you can return every record that?s part of a specific resource by searching for its URI fragment.  For example, in http://test.archivesspace.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__test.archivesspace.org&d=DwMGaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=11hM8HX7HlA9sIpr53-NaHOP075tgHypEKvcVTWnm4E&s=r2jIsp6YrP9MJ4M1y9UYt5iqAyax0ajQMSu75vno1OQ&e=>, there?s a Repository named GoneRepo, and in that repository there?s a resource named Aperture Labs Records.  That resource has a URI fragment of ?resources/45?, which is unique in that instance of ArchivesSpace.  If you search for that fragment in quotes, like so, http://test.archivesspace.org/search?utf8=%E2%9C%93&q=%22resources%2F45%22<https://urldefense.proofpoint.com/v2/url?u=http-3A__test.archivesspace.org_search-3Futf8-3D-25E2-259C-2593-26q-3D-2522resources-252F45-2522&d=DwMGaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=11hM8HX7HlA9sIpr53-NaHOP075tgHypEKvcVTWnm4E&s=6vKqh-2GvwL35qfsDQPGPK8FiVy2ocxHaW0aI-GTFGg&e=>, then you?ll get all of the records associated with that collection.  You can then filter by ?archival objects,? for instance, if you only want all the components that are part of that collection, rather than top container, event, and other record types.

Does that help?

Mark



From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Joan Curbow
Sent: Monday, 16 October, 2017 2:17 PM
To: Archivesspace Users Group (archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>) <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] I should have been more clear in my question

I was specifically asking if one could search within a collection in the staff interface, not the PUI.

Sincerely,

Joan Curbow
Reference Librarian and Archivist
Buena Vista University Library
Buena Vista University
610 West Fourth Street
Storm Lake, Iowa  50588
712.749.2094
www.library.bvu.edu<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.library.bvu.edu&d=DwMGaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=11hM8HX7HlA9sIpr53-NaHOP075tgHypEKvcVTWnm4E&s=Yiw56QwuDvKqvy8N7TE5KOFRRAAta13UDlzdDbUmFBI&e=>??




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171016/454d219d/attachment.html>

From ltang5 at lib.msu.edu  Mon Oct 16 16:22:39 2017
From: ltang5 at lib.msu.edu (Tang, Lydia)
Date: Mon, 16 Oct 2017 20:22:39 +0000
Subject: [Archivesspace_Users_Group] I should have been more clear in my
 question
In-Reply-To: <BN3PR08MB1303532ED8C63045406533D68C4F0@BN3PR08MB1303.namprd08.prod.outlook.com>
References: <CY1PR05MB236283E4383011A97FEBC594B54F0@CY1PR05MB2362.namprd05.prod.outlook.com>
 <BN3PR08MB1303000A67EE439D75E849CF8C4F0@BN3PR08MB1303.namprd08.prod.outlook.com>
 <BN3PR08MB1303532ED8C63045406533D68C4F0@BN3PR08MB1303.namprd08.prod.outlook.com>
Message-ID: <81B91DCC-04B8-4927-8653-D2DD51CC7C2A@lib.msu.edu>

Could it be accomplished by expanding out the Advanced Search in the staff interface to include different keywords?  I wonder if searching ?___? and the resource identifier might do it?  Otherwise/additionally, would be it be helpful to have a ?Search this collection? search bar on a resource page?  (Sorry for my lousy wireframe).  Ideally then it would show all of the results within the Resource tree.  It would mean having to pull up the individual collection, but I remember definitely cases where I ended up downloading the PDF of the finding aid to keyword search it to find what I needed via the staff interface since it was something nested among dozens of series.  If others have ideas, please keep sharing them!
Lydia

From: <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of "Custer, Mark" <mark.custer at yale.edu>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Date: Monday, October 16, 2017 at 3:13 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] I should have been more clear in my question

I should add that I think that there should be an easier, user-friendly way to do this in the staff interface, though!!!  Searching for the URI fragment just happens to be my current workaround.

I wonder if anyone else has other solutions for this right now, especially a working plugin that could become part of the core code?



From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Custer, Mark
Sent: Monday, 16 October, 2017 3:07 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] I should have been more clear in my question

Hi, Joan.

In the PUI, yes, you can do this.

In the Staff Interface, you can also do this, but the approach isn?t as obvious.  But you can return every record that?s part of a specific resource by searching for its URI fragment.  For example, in http://test.archivesspace.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__test.archivesspace.org&d=DwMGaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=11hM8HX7HlA9sIpr53-NaHOP075tgHypEKvcVTWnm4E&s=r2jIsp6YrP9MJ4M1y9UYt5iqAyax0ajQMSu75vno1OQ&e=>, there?s a Repository named GoneRepo, and in that repository there?s a resource named Aperture Labs Records.  That resource has a URI fragment of ?resources/45?, which is unique in that instance of ArchivesSpace.  If you search for that fragment in quotes, like so, http://test.archivesspace.org/search?utf8=%E2%9C%93&q=%22resources%2F45%22<https://urldefense.proofpoint.com/v2/url?u=http-3A__test.archivesspace.org_search-3Futf8-3D-25E2-259C-2593-26q-3D-2522resources-252F45-2522&d=DwMGaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=11hM8HX7HlA9sIpr53-NaHOP075tgHypEKvcVTWnm4E&s=6vKqh-2GvwL35qfsDQPGPK8FiVy2ocxHaW0aI-GTFGg&e=>, then you?ll get all of the records associated with that collection.  You can then filter by ?archival objects,? for instance, if you only want all the components that are part of that collection, rather than top container, event, and other record types.

Does that help?

Mark



From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Joan Curbow
Sent: Monday, 16 October, 2017 2:17 PM
To: Archivesspace Users Group (archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>) <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] I should have been more clear in my question

I was specifically asking if one could search within a collection in the staff interface, not the PUI.

Sincerely,

Joan Curbow
Reference Librarian and Archivist
Buena Vista University Library
Buena Vista University
610 West Fourth Street
Storm Lake, Iowa  50588
712.749.2094
www.library.bvu.edu<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.library.bvu.edu&d=DwMGaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=11hM8HX7HlA9sIpr53-NaHOP075tgHypEKvcVTWnm4E&s=Yiw56QwuDvKqvy8N7TE5KOFRRAAta13UDlzdDbUmFBI&e=>??




-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2017-10-16 at 4.05.41 PM.png
Type: image/png
Size: 85613 bytes
Desc: Screen Shot 2017-10-16 at 4.05.41 PM.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171016/46a1314b/attachment.png>

From CurbowJ at bvu.edu  Mon Oct 16 16:43:05 2017
From: CurbowJ at bvu.edu (Joan Curbow)
Date: Mon, 16 Oct 2017 20:43:05 +0000
Subject: [Archivesspace_Users_Group] I should have been more clear in my
 question
In-Reply-To: <81B91DCC-04B8-4927-8653-D2DD51CC7C2A@lib.msu.edu>
References: <CY1PR05MB236283E4383011A97FEBC594B54F0@CY1PR05MB2362.namprd05.prod.outlook.com>
 <BN3PR08MB1303000A67EE439D75E849CF8C4F0@BN3PR08MB1303.namprd08.prod.outlook.com>
 <BN3PR08MB1303532ED8C63045406533D68C4F0@BN3PR08MB1303.namprd08.prod.outlook.com>
 <81B91DCC-04B8-4927-8653-D2DD51CC7C2A@lib.msu.edu>
Message-ID: <CY1PR05MB2362EC813C24B1D6655D8313B54F0@CY1PR05MB2362.namprd05.prod.outlook.com>

Mark, that seems like a pretty labor-intensive way to find the info, but if that's what works, I could try it.

I would love to see the functionality for this enhanced along the lines of what Lydia discusses, i.e. "Search this collection" search box. For really large and/or complex collections, it seems like this would be a big help.

Thanks for your responses, though.

Joan

-----Original Message-----
From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Tang, Lydia
Sent: Monday, October 16, 2017 3:23 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] I should have been more clear in my question

Could it be accomplished by expanding out the Advanced Search in the staff interface to include different keywords?  I wonder if searching ?___? and the resource identifier might do it?  Otherwise/additionally, would be it be helpful to have a ?Search this collection? search bar on a resource page?  (Sorry for my lousy wireframe).  Ideally then it would show all of the results within the Resource tree.  It would mean having to pull up the individual collection, but I remember definitely cases where I ended up downloading the PDF of the finding aid to keyword search it to find what I needed via the staff interface since it was something nested among dozens of series.  If others have ideas, please keep sharing them!
Lydia

From: <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of "Custer, Mark" <mark.custer at yale.edu>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Date: Monday, October 16, 2017 at 3:13 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] I should have been more clear in my question

I should add that I think that there should be an easier, user-friendly way to do this in the staff interface, though!!!  Searching for the URI fragment just happens to be my current workaround.

I wonder if anyone else has other solutions for this right now, especially a working plugin that could become part of the core code?



From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Custer, Mark
Sent: Monday, 16 October, 2017 3:07 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] I should have been more clear in my question

Hi, Joan.

In the PUI, yes, you can do this.

In the Staff Interface, you can also do this, but the approach isn?t as obvious.  But you can return every record that?s part of a specific resource by searching for its URI fragment.  For example, in http://test.archivesspace.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__test.archivesspace.org&d=DwMGaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=11hM8HX7HlA9sIpr53-NaHOP075tgHypEKvcVTWnm4E&s=r2jIsp6YrP9MJ4M1y9UYt5iqAyax0ajQMSu75vno1OQ&e=>, there?s a Repository named GoneRepo, and in that repository there?s a resource named Aperture Labs Records.  That resource has a URI fragment of ?resources/45?, which is unique in that instance of ArchivesSpace.  If you search for that fragment in quotes, like so, http://test.archivesspace.org/search?utf8=%E2%9C%93&q=%22resources%2F45%22<https://urldefense.proofpoint.com/v2/url?u=http-3A__test.archivesspace.org_search-3Futf8-3D-25E2-259C-2593-26q-3D-2522resources-252F45-2522&d=DwMGaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=11hM8HX7HlA9sIpr53-NaHOP075tgHypEKvcVTWnm4E&s=6vKqh-2GvwL35qfsDQPGPK8FiVy2ocxHaW0aI-GTFGg&e=>, then you?ll get all of the records associated with that collection.  You can then filter by ?archival objects,? for instance, if you only want all the components that are part of that collection, rather than top container, event, and other record types.

Does that help?

Mark



From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Joan Curbow
Sent: Monday, 16 October, 2017 2:17 PM
To: Archivesspace Users Group (archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>) <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] I should have been more clear in my question

I was specifically asking if one could search within a collection in the staff interface, not the PUI.

Sincerely,

Joan Curbow
Reference Librarian and Archivist
Buena Vista University Library
Buena Vista University
610 West Fourth Street
Storm Lake, Iowa  50588
712.749.2094
www.library.bvu.edu<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.library.bvu.edu&d=DwMGaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=11hM8HX7HlA9sIpr53-NaHOP075tgHypEKvcVTWnm4E&s=Yiw56QwuDvKqvy8N7TE5KOFRRAAta13UDlzdDbUmFBI&e=>??





From mcallahan at smith.edu  Mon Oct 16 16:53:37 2017
From: mcallahan at smith.edu (Maureen Callahan)
Date: Mon, 16 Oct 2017 16:53:37 -0400
Subject: [Archivesspace_Users_Group] Narrowing search results by facet in
	the staff interface
Message-ID: <CAH0VKbCM-WsZJs36wZm7eDiP8V1VRo6HfaXaSxQBYihcEEhJFg@mail.gmail.com>

While we're making feature requests ---

I'd love to be able to refine search results by collection as a facet. For
instance, true story, I was on the reference desk this afternoon and a
student said that she wanted archives about Taiwan. Despite my best
reference interview skills, she didn't want to narrow down and just wanted
everything we have about Taiwan.

Here's what that looks like:

[image: Inline image 1]
Imagine about a zillion more records that just say "Taiwan" without any
further context. I know that there's going to be a push for greater
usability for the staff interface -- it would be great to have this
included.

Another great facet would be to use the machine-actionable conditions
governing access statements to see what's open for research now and what
will be open in the future (or is governed by a non-time-bound
restriction). It would be great to have this in the PUI as well.

Those are my ideas of the day.

Maureen


-- 
Maureen Callahan
Sophia Smith Collection Archivist
Smith College Special Collections
Northampton, Massachusetts 01063
T. 413 585 2981 C. 215.863.1860
mcallahan at smith.edu

Pronouns: she/her/hers

Facebook: https://www.facebook.com/SophiaSmithCollection/
Instagram: https://www.instagram.com/smithlibraries/
Twitter: https://twitter.com/archivalagents

*Please note*. Smith College Special Collections is now housed at Young
Library
<https://www.smith.edu/libraries/about/new-neilson/wheres-my-library>.
Learn more about renovations to Neilson Library here
<https://www.smith.edu/libraries/about/new-neilson>.

On Mon, Oct 16, 2017 at 4:22 PM, Tang, Lydia <ltang5 at lib.msu.edu> wrote:

> Could it be accomplished by expanding out the Advanced Search in the staff
> interface to include different keywords?  I wonder if searching ?___? and
> the resource identifier might do it?  Otherwise/additionally, would be it
> be helpful to have a ?Search this collection? search bar on a resource
> page?  (Sorry for my lousy wireframe).  Ideally then it would show all of
> the results within the Resource tree.  It would mean having to pull up the
> individual collection, but I remember definitely cases where I ended up
> downloading the PDF of the finding aid to keyword search it to find what I
> needed via the staff interface since it was something nested among dozens
> of series.  If others have ideas, please keep sharing them!
> Lydia
>
> From: <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf
> of "Custer, Mark" <mark.custer at yale.edu>
> Reply-To: Archivesspace Users Group <archivesspace_users_group@
> lyralists.lyrasis.org>
> Date: Monday, October 16, 2017 at 3:13 PM
> To: Archivesspace Users Group <archivesspace_users_group@
> lyralists.lyrasis.org>
> Subject: Re: [Archivesspace_Users_Group] I should have been more clear in
> my question
>
> I should add that I think that there should be an easier, user-friendly
> way to do this in the staff interface, though!!!  Searching for the URI
> fragment just happens to be my current workaround.
>
> I wonder if anyone else has other solutions for this right now, especially
> a working plugin that could become part of the core code?
>
>
>
> From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:
> archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of
> Custer, Mark
> Sent: Monday, 16 October, 2017 3:07 PM
> To: Archivesspace Users Group <archivesspace_users_group@
> lyralists.lyrasis.org>
> Subject: Re: [Archivesspace_Users_Group] I should have been more clear in
> my question
>
> Hi, Joan.
>
> In the PUI, yes, you can do this.
>
> In the Staff Interface, you can also do this, but the approach isn?t as
> obvious.  But you can return every record that?s part of a specific
> resource by searching for its URI fragment.  For example, in
> http://test.archivesspace.org<https://urldefense.proofpoint.
> com/v2/url?u=http-3A__test.archivesspace.org&d=DwMGaQ&c=
> cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=
> 11hM8HX7HlA9sIpr53-NaHOP075tgHypEKvcVTWnm4E&s=
> r2jIsp6YrP9MJ4M1y9UYt5iqAyax0ajQMSu75vno1OQ&e=>, there?s a Repository
> named GoneRepo, and in that repository there?s a resource named Aperture
> Labs Records.  That resource has a URI fragment of ?resources/45?, which is
> unique in that instance of ArchivesSpace.  If you search for that fragment
> in quotes, like so, http://test.archivesspace.org/
> search?utf8=%E2%9C%93&q=%22resources%2F45%22<https://
> urldefense.proofpoint.com/v2/url?u=http-3A__test.archivesspace.org_search-
> 3Futf8-3D-25E2-259C-2593-26q-3D-2522resources-252F45-2522&
> d=DwMGaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUC
> Pm3xGvnFT0zjU&m=11hM8HX7HlA9sIpr53-NaHOP075tgHypEKvcVTWnm4E&s=6vKqh-
> 2GvwL35qfsDQPGPK8FiVy2ocxHaW0aI-GTFGg&e=>, then you?ll get all of the
> records associated with that collection.  You can then filter by ?archival
> objects,? for instance, if you only want all the components that are part
> of that collection, rather than top container, event, and other record
> types.
>
> Does that help?
>
> Mark
>
>
>
> From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:
> archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:
> archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of
> Joan Curbow
> Sent: Monday, 16 October, 2017 2:17 PM
> To: Archivesspace Users Group (archivesspace_users_group@
> lyralists.lyrasis.org<mailto:archivesspace_users_group@
> lyralists.lyrasis.org>) <archivesspace_users_group at lyralists.lyrasis.org
> <mailto:archivesspace_users_group at lyralists.lyrasis.org>>
> Subject: [Archivesspace_Users_Group] I should have been more clear in my
> question
>
> I was specifically asking if one could search within a collection in the
> staff interface, not the PUI.
>
> Sincerely,
>
> Joan Curbow
> Reference Librarian and Archivist
> Buena Vista University Library
> Buena Vista University
> 610 West Fourth Street
> Storm Lake, Iowa  50588
> 712.749.2094
> www.library.bvu.edu<https://urldefense.proofpoint.com/v2/
> url?u=http-3A__www.library.bvu.edu&d=DwMGaQ&c=cjytLXgP8ixuoHflwc-poQ&r=
> 7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=11hM8HX7HlA9sIpr53-
> NaHOP075tgHypEKvcVTWnm4E&s=Yiw56QwuDvKqvy8N7TE5KOFRRAAta13UDlzdDbUmFBI&e=
> >??
>
>
>
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171016/1e66cbe5/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2017-10-16 at 4.25.23 PM.png
Type: image/png
Size: 228586 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171016/1e66cbe5/attachment-0001.png>

From mark.custer at yale.edu  Mon Oct 16 17:12:19 2017
From: mark.custer at yale.edu (Custer, Mark)
Date: Mon, 16 Oct 2017 21:12:19 +0000
Subject: [Archivesspace_Users_Group] Narrowing search results by facet
	in	the staff interface
In-Reply-To: <CAH0VKbCM-WsZJs36wZm7eDiP8V1VRo6HfaXaSxQBYihcEEhJFg@mail.gmail.com>
References: <CAH0VKbCM-WsZJs36wZm7eDiP8V1VRo6HfaXaSxQBYihcEEhJFg@mail.gmail.com>
Message-ID: <BN3PR08MB13030A11112E12099281FFAF8C4F0@BN3PR08MB1303.namprd08.prod.outlook.com>

Joan,



I completely agree that other search options should be part of the staff interface.  I just wanted to show that there is a workaround in this particular use case, as long as you combine the URI fragment search trick with the advanced search features in the staff interface.  E.g. here I?m searching for the term ?cake? within any record attached to ?resources/45?:



[cid:image002.jpg at 01D346A1.EADE9110]



Not ideal, but it helps when searching within a single collection (or just a few, if you?re willing to add more rows and Booleans ?).



Moving forward, there should definitely be a closer alignment, as well continued improvements, in both the staff and public interfaces of ASpace.  If I recall correctly, Dartmouth has done a lot of work updating how the search results appear in the staff interface, for instance.  And, as Maureen notes, there?s always room for other facets to consider adding, and a restriction one would be fantastic!  Another one that I?d love to have is the ability to just add a simple ?on-site? vs. ?off-site? facet that could be governed by flagging certain locations as ?off-site? locations.



Mark


From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Maureen Callahan
Sent: Monday, 16 October, 2017 4:54 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Narrowing search results by facet in the staff interface

While we're making feature requests ---

I'd love to be able to refine search results by collection as a facet. For instance, true story, I was on the reference desk this afternoon and a student said that she wanted archives about Taiwan. Despite my best reference interview skills, she didn't want to narrow down and just wanted everything we have about Taiwan.

Here's what that looks like:

[Inline image 1]
Imagine about a zillion more records that just say "Taiwan" without any further context. I know that there's going to be a push for greater usability for the staff interface -- it would be great to have this included.

Another great facet would be to use the machine-actionable conditions governing access statements to see what's open for research now and what will be open in the future (or is governed by a non-time-bound restriction). It would be great to have this in the PUI as well.

Those are my ideas of the day.

Maureen


--
Maureen Callahan
Sophia Smith Collection Archivist
Smith College Special Collections
Northampton, Massachusetts 01063
T. 413 585 2981 C. 215.863.1860
mcallahan at smith.edu<mailto:mcallahan at smith.edu>

Pronouns: she/her/hers

Facebook: https://www.facebook.com/SophiaSmithCollection/<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_SophiaSmithCollection_&d=DwMFaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=CsKKkFuZwLmWxDbgxHRhnOSBC7snrb6eb1unn0m6fSE&s=GOCMkYfSuRoPjfn9Gvu_WFEuGr1Wn0jvsRSO8cWeO8Q&e=>
Instagram: https://www.instagram.com/smithlibraries/<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.instagram.com_smithlibraries_&d=DwMFaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=CsKKkFuZwLmWxDbgxHRhnOSBC7snrb6eb1unn0m6fSE&s=_7NJbCl6UkDnmtrsTOCCl_hzvI8Y1oQF28K-yXprF6w&e=>
Twitter: https://twitter.com/archivalagents<https://urldefense.proofpoint.com/v2/url?u=https-3A__twitter.com_archivalagents&d=DwMFaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=CsKKkFuZwLmWxDbgxHRhnOSBC7snrb6eb1unn0m6fSE&s=Antau6TlvP-FIOdWoejq1MPtHkj4kk7DZvJWZ2PNrs8&e=>

Please note. Smith College Special Collections is now housed at Young Library<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.smith.edu_libraries_about_new-2Dneilson_wheres-2Dmy-2Dlibrary&d=DwMFaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=CsKKkFuZwLmWxDbgxHRhnOSBC7snrb6eb1unn0m6fSE&s=X_HlLmn04jWSJsjgTa7BlGP2YFhAu6anOaI-r_x0COE&e=>. Learn more about renovations to Neilson Library here<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.smith.edu_libraries_about_new-2Dneilson&d=DwMFaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=CsKKkFuZwLmWxDbgxHRhnOSBC7snrb6eb1unn0m6fSE&s=JDtFBsZ-ZjV2Gb73_NYD4VsEFHluyHJ_uFGU2injEoM&e=>.

On Mon, Oct 16, 2017 at 4:22 PM, Tang, Lydia <ltang5 at lib.msu.edu<mailto:ltang5 at lib.msu.edu>> wrote:
Could it be accomplished by expanding out the Advanced Search in the staff interface to include different keywords?  I wonder if searching ?___? and the resource identifier might do it?  Otherwise/additionally, would be it be helpful to have a ?Search this collection? search bar on a resource page?  (Sorry for my lousy wireframe).  Ideally then it would show all of the results within the Resource tree.  It would mean having to pull up the individual collection, but I remember definitely cases where I ended up downloading the PDF of the finding aid to keyword search it to find what I needed via the staff interface since it was something nested among dozens of series.  If others have ideas, please keep sharing them!
Lydia

From: <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of "Custer, Mark" <mark.custer at yale.edu<mailto:mark.custer at yale.edu>>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Date: Monday, October 16, 2017 at 3:13 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] I should have been more clear in my question

I should add that I think that there should be an easier, user-friendly way to do this in the staff interface, though!!!  Searching for the URI fragment just happens to be my current workaround.

I wonder if anyone else has other solutions for this right now, especially a working plugin that could become part of the core code?



From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>] On Behalf Of Custer, Mark
Sent: Monday, 16 October, 2017 3:07 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] I should have been more clear in my question

Hi, Joan.

In the PUI, yes, you can do this.

In the Staff Interface, you can also do this, but the approach isn?t as obvious.  But you can return every record that?s part of a specific resource by searching for its URI fragment.  For example, in http://test.archivesspace.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__test.archivesspace.org&d=DwMFaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=CsKKkFuZwLmWxDbgxHRhnOSBC7snrb6eb1unn0m6fSE&s=k8h5wS5XcSv3NN27zyZPs3A2l9dLNX_To2bga2Mhnm4&e=><https://urldefense.proofpoint.com/v2/url?u=http-3A__test.archivesspace.org&d=DwMGaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=11hM8HX7HlA9sIpr53-NaHOP075tgHypEKvcVTWnm4E&s=r2jIsp6YrP9MJ4M1y9UYt5iqAyax0ajQMSu75vno1OQ&e=>, there?s a Repository named GoneRepo, and in that repository there?s a resource named Aperture Labs Records.  That resource has a URI fragment of ?resources/45?, which is unique in that instance of ArchivesSpace.  If you search for that fragment in quotes, like so, http://test.archivesspace.org/search?utf8=%E2%9C%93&q=%22resources%2F45%22<https://urldefense.proofpoint.com/v2/url?u=http-3A__test.archivesspace.org_search-3Futf8-3D-25E2-259C-2593-26q-3D-2522resources-252F45-2522&d=DwMFaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=CsKKkFuZwLmWxDbgxHRhnOSBC7snrb6eb1unn0m6fSE&s=cKXFTznSqC6O44cHIkepK2UdeuGTiDSINfcwYULklLA&e=><https://urldefense.proofpoint.com/v2/url?u=http-3A__test.archivesspace.org_search-3Futf8-3D-25E2-259C-2593-26q-3D-2522resources-252F45-2522&d=DwMGaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=11hM8HX7HlA9sIpr53-NaHOP075tgHypEKvcVTWnm4E&s=6vKqh-2GvwL35qfsDQPGPK8FiVy2ocxHaW0aI-GTFGg&e=>, then you?ll get all of the records associated with that collection.  You can then filter by ?archival objects,? for instance, if you only want all the components that are part of that collection, rather than top container, event, and other record types.

Does that help?

Mark



From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org><mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>] On Behalf Of Joan Curbow
Sent: Monday, 16 October, 2017 2:17 PM
To: Archivesspace Users Group (archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org><mailto:archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>) <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org><mailto:archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>>
Subject: [Archivesspace_Users_Group] I should have been more clear in my question

I was specifically asking if one could search within a collection in the staff interface, not the PUI.

Sincerely,

Joan Curbow
Reference Librarian and Archivist
Buena Vista University Library
Buena Vista University
610 West Fourth Street
Storm Lake, Iowa  50588
712.749.2094<tel:712.749.2094>
www.library.bvu.edu<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.library.bvu.edu&d=DwMFaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=CsKKkFuZwLmWxDbgxHRhnOSBC7snrb6eb1unn0m6fSE&s=9XsmhnQodS5io7zxJQ_71r7vzTbDvU31IHYKsjVglVw&e=><https://urldefense.proofpoint.com/v2/url?u=http-3A__www.library.bvu.edu&d=DwMGaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=11hM8HX7HlA9sIpr53-NaHOP075tgHypEKvcVTWnm4E&s=Yiw56QwuDvKqvy8N7TE5KOFRRAAta13UDlzdDbUmFBI&e=>??





_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group<https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwMFaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=CsKKkFuZwLmWxDbgxHRhnOSBC7snrb6eb1unn0m6fSE&s=9QbkVdKKPBngajkX3U_OogsExXEhM8ozfwzD7mUxlwk&e=>




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171016/d0b7ef2b/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 28062 bytes
Desc: image002.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171016/d0b7ef2b/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 61314 bytes
Desc: image004.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171016/d0b7ef2b/attachment.png>

From noah.huffman at duke.edu  Tue Oct 17 10:04:36 2017
From: noah.huffman at duke.edu (Noah Huffman)
Date: Tue, 17 Oct 2017 14:04:36 +0000
Subject: [Archivesspace_Users_Group] v2.1.2 indexing woes
Message-ID: <BN6PR05MB3474399869398C661C6D633DE64C0@BN6PR05MB3474.namprd05.prod.outlook.com>

Hi all,

We upgraded to version 2.1.2 last week and have since been experiencing some fairly severe indexing issues.  For example, when creating or editing new records it often takes 20-30 minutes for those changes to index and become visible in the staff UI. Also, deleted records still persist in searches and browses, sometimes indefinitely, even though the records themselves have been deleted from the underlying database.  The SOLR admin site also reports that the indexer is consuming almost all of the available memory (12GB RAM).

I've read all the previous posts about indexing issues and we don't seem to have any orphaned records or other previously reported issues that might cause this.

The log file does indicate some problem, but I can't interpret what's going on.

Here's a gist with a snapshot of the log file showing the error that is repeating over and over, usually followed by thousands of rows that indicate some kind of delete action. I'm definitely not deleting this many documents...

https://gist.github.com/noahgh221/2a274def65c858662c64e4cd2c5b0de4

My hunch is that ASpace is stuck in some sort of loop trying to delete (unsuccessfully) the same set of records over and over.  We've shut the application down and triggered a re-index, but the problem still persists. The initial re-index completes without any issues but then the periodic indexer starts throwing these errors and reporting the deletions.

Thanks for any advice,
-Noah

================
Noah Huffman
Archivist for Metadata, Systems, and Digital Records
David M. Rubenstein Rare Book & Manuscript Library
Duke University | 919-660-5982
http://library.duke.edu/rubenstein/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171017/2d3953fc/attachment.html>

From s.innes at auckland.ac.nz  Tue Oct 17 19:55:03 2017
From: s.innes at auckland.ac.nz (Stephen Innes)
Date: Tue, 17 Oct 2017 23:55:03 +0000
Subject: [Archivesspace_Users_Group] ArchivesSpace upgrade REMINDER
Message-ID: <95881b497dc940a48f3c1767ac112266@uxcn13-ogg-c.UoA.auckland.ac.nz>

A reminder to cease using ArchivesSpace today before 4 pm to allow for the upgrade to v2.2.0. I will inform you when AS is ready to use again tomorrow.

Thanks,

Stephen Innes

From: Stephen Innes
Sent: Tuesday, 17 October 2017 2:18 PM
To: 'Anne Newnham (a.newnham at auckland.ac.nz)' <a.newnham at auckland.ac.nz>; 'Katherine Pawley' <k.pawley at auckland.ac.nz>; 'Rod Chan' <rod.chan at auckland.ac.nz>; Sarah Cox <sl.cox at auckland.ac.nz>; Sarah Dunbar <s.dunbar at auckland.ac.nz>; Selina Foote <s.foote at auckland.ac.nz>; 'Stephen Innes (s.innes at auckland.ac.nz)' <s.innes at auckland.ac.nz>; 'William Hamill (w.hamill at auckland.ac.nz)' <w.hamill at auckland.ac.nz>
Cc: Michael Ng (michael.ng at auckland.ac.nz) <michael.ng at auckland.ac.nz>; Ksenija Obradovic <k.obradovic at auckland.ac.nz>
Subject: ArchivesSpace upgrade to v2.2.0 Wednesday 18 October

Michael Ng of LADS will be upgrading ArchivesSpace to the latest version (2.2.0) from Wednesday 18 October 4 pm until Thursday 19 October noon (approx.) Until the upgrade is complete there will be no access to ArchivesSpace production so please do not attempt to access it. I will inform you when you can use AS again on Thursday.

There were some minor bugs in the initial versions of AS 2.0 and these have been rectified by AS ? they had important implications for IDs throughout the system (such as any file ID) and the display of digital object links, so it was well worth delaying a little longer to get a workable system running which meets our needs. We have also been working on tidying up some hangovers from the migration from Archivists? Toolkit and upgrading the Controlled Value Lists.

Following this upgrade we will do further work on the Public User Interface ? I have the earlier feedback from you and there are other changes I would like to see implemented.  The PUI will only be accessible to staff at first while we test it and organise support and help resources for the wider user community. In the meantime, the feedback and development work on the PUI is available at: P:\Special Collections\ArchivesSpace\Public User Interface\pui-interface-implementation.xlsx

A big thank you to Michael Ng who has worked tirelessly to make it all happen!


Regards,

Stephen Innes


Stephen Innes (ALIANZA)
Special Collections Manager
General Library, Te Herenga M?tauranga Wh?nui
The University of Auckland
Private Bag 92019
Auckland 1142
New Zealand
Telephone (649) 373-7599 ext. 88062 | Fax (649) 373-7565
Website: http://www.library.auckland.ac.nz/about-us/collections/special-collections/general-library
Online exhibition: Special Collections First World War Centenary 2014-2018<http://www.specialcollections.auckland.ac.nz/ww1-centenary>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171017/bda1b357/attachment.html>

From s.innes at auckland.ac.nz  Tue Oct 17 20:56:16 2017
From: s.innes at auckland.ac.nz (Stephen Innes)
Date: Wed, 18 Oct 2017 00:56:16 +0000
Subject: [Archivesspace_Users_Group] Recall: ArchivesSpace upgrade REMINDER
Message-ID: <36c79ee5f53847f3b0bdc3411c8d8af3@uxcn13-ogg-c.UoA.auckland.ac.nz>

Stephen Innes would like to recall the message, "ArchivesSpace upgrade REMINDER".

From bmg17 at psu.edu  Wed Oct 18 11:39:06 2017
From: bmg17 at psu.edu (Ben Goldman)
Date: Wed, 18 Oct 2017 11:39:06 -0400 (EDT)
Subject: [Archivesspace_Users_Group] transferring resource to another
	repository
Message-ID: <542540168.5870912.1508341146419.JavaMail.zimbra@psu.edu>

Hello, 

Can anyone confirm whether top containers associated with a resource will transfer to another repository along with the resource record when it is transferred? 

Thanks, 
Ben 

Ben Goldman 
Digital Records Archivist & 
Sally W. Kalin Early Career Librarian for Technological Innovations 
Penn State University Libraries 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171018/25abde32/attachment.html>

From benn.joseph at northwestern.edu  Wed Oct 18 12:01:03 2017
From: benn.joseph at northwestern.edu (Benn Joseph)
Date: Wed, 18 Oct 2017 16:01:03 +0000
Subject: [Archivesspace_Users_Group] transferring resource to another
 repository
Message-ID: <f05eddc2f54043dd81642839875a381b@evcspmbx04.ads.northwestern.edu>

Just tried it in v2.1.2 and it worked for me?both the resource and all top containers transferred completely. It took a few minutes to reindex, but after that everything showed up on both the staff and public interface.

--Benn

Benn Joseph
Head of Archival Processing
Northwestern University Libraries
Northwestern University
www.library.northwestern.edu
benn.joseph at northwestern.edu<mailto:benn.joseph at northwestern.edu%0d>
847.467.6581

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Ben Goldman
Sent: Wednesday, October 18, 2017 10:39 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] transferring resource to another repository

Hello,

Can anyone confirm whether top containers associated with a resource will transfer to another repository along with the resource record when it is transferred?

Thanks,
Ben

Ben Goldman
Digital Records Archivist &
Sally W. Kalin Early Career Librarian for Technological Innovations
Penn State University Libraries
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171018/ad6090f3/attachment.html>

From bobbi_fox at harvard.edu  Wed Oct 18 14:06:43 2017
From: bobbi_fox at harvard.edu (Fox, Bobbi)
Date: Wed, 18 Oct 2017 18:06:43 +0000
Subject: [Archivesspace_Users_Group] batch re-ordering of controlled value
	lists; script/plugin, anyone?
Message-ID: <BN6PR07MB3492EB22E765B19088165F10904D0@BN6PR07MB3492.namprd07.prod.outlook.com>

In the course of adapting ArchivesSpace to Harvard's needs, we've ended up with some very weedy controlled values lists (extent type > 200 values! -- of course, some of them need to be removed) with arbitrary positioning.  Our support team is tasked with the job of wrangling the lists with a defined order, and the interactive "move up/down one position at a time, wait for the server to refresh, etc." is really tedious.

Has anyone written a script/created a plugin that would do this with less effort?  I'm inclined to do it at the mysql level, rather than write an extension to the backend/controller/enumeration.rb, but maybe someone has done this already?

Thanks,
Bobbi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171018/648110aa/attachment.html>

From j at minorscience.com  Wed Oct 18 14:23:10 2017
From: j at minorscience.com (Jason Loeffler)
Date: Wed, 18 Oct 2017 11:23:10 -0700
Subject: [Archivesspace_Users_Group] batch re-ordering of controlled
 value lists; script/plugin, anyone?
In-Reply-To: <BN6PR07MB3492EB22E765B19088165F10904D0@BN6PR07MB3492.namprd07.prod.outlook.com>
References: <BN6PR07MB3492EB22E765B19088165F10904D0@BN6PR07MB3492.namprd07.prod.outlook.com>
Message-ID: <CAP4gJsVqTpLK7Ch_8PwwvidjpDkBz4Vrqnc8RuGdF4_WyFyisg@mail.gmail.com>

Agreed. I opened a ticket on this issue last June.

<goog_983756235>
https://archivesspace.atlassian.net/browse/AR-1512

Draggable interface elements would solve this on the front end though I'm
not sure what's required at the controller level.

On Wed, Oct 18, 2017 at 11:06 AM, Fox, Bobbi <bobbi_fox at harvard.edu> wrote:

> In the course of adapting ArchivesSpace to Harvard?s needs, we?ve ended up
> with some very weedy controlled values lists (extent type > 200 values! --
> of course, some of them need to be removed) with arbitrary positioning.
> Our support team is tasked with the job of wrangling the lists with a
> defined order, and the interactive ?move up/down one position at a time,
> wait for the server to refresh, etc.? is really tedious.
>
>
>
> Has anyone written a script/created a plugin that would do this with less
> effort?  I?m inclined to do it at the mysql level, rather than write an
> extension to the backend/controller/enumeration.rb, but maybe someone has
> done this already?
>
>
>
> Thanks,
>
> Bobbi
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171018/9367a928/attachment.html>

From sdm7g at virginia.edu  Wed Oct 18 15:29:34 2017
From: sdm7g at virginia.edu (Majewski, Steven (sdm7g))
Date: Wed, 18 Oct 2017 19:29:34 +0000
Subject: [Archivesspace_Users_Group] batch re-ordering of controlled
	value	lists; script/plugin, anyone?
In-Reply-To: <BN6PR07MB3492EB22E765B19088165F10904D0@BN6PR07MB3492.namprd07.prod.outlook.com>
References: <BN6PR07MB3492EB22E765B19088165F10904D0@BN6PR07MB3492.namprd07.prod.outlook.com>
Message-ID: <330E3F6E-D351-47D9-9876-EDDACF295015@virginia.edu>


It looks like the positioning would be very simple to do in mysql as you only have to modify the position value in the table ? no complicated joins required. You could do it interactively with a GUI frontend like Sequel Pro or MySQLWorkbench. Just make sure you don?t leave any duplicate positions. 

If you already have a table of enum values and new positions, and you want to do it programmatically, then you can load those pairs as a temporary table, and create a function return position given value string, and use that function in your update statement rather than try to explicitly iterate over the tables. 

Merging enumeration values, on the other hand, is more complicated, and I would leave it to the frontend/backend, and not try MySQL surgery. 

We are doing a similar controlled value cleanup. 
The issue we?re having is that we have several repositories, and the frontend view and list of number of related items and links are repository based, so cleanup requires tediously switching between repositories trying to find the resources that are still linked to those values. 

Does the merge operation also only merge enumeration_values for the current repository ?  
( I *think* that is the case, but I?m not sure. ) 

Perhaps, if you?re logged in on an admin account, it should have an option for searching across repositories. 


? Steve Majewski


> On Oct 18, 2017, at 2:06 PM, Fox, Bobbi <bobbi_fox at harvard.edu> wrote:
> 
> In the course of adapting ArchivesSpace to Harvard?s needs, we?ve ended up with some very weedy controlled values lists (extent type > 200 values! -- of course, some of them need to be removed) with arbitrary positioning.  Our support team is tasked with the job of wrangling the lists with a defined order, and the interactive ?move up/down one position at a time, wait for the server to refresh, etc.? is really tedious.
>  
> Has anyone written a script/created a plugin that would do this with less effort?  I?m inclined to do it at the mysql level, rather than write an extension to the backend/controller/enumeration.rb, but maybe someone has done this already?
>  
> Thanks,
> Bobbi
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org <mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group <http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171018/3eb9ed91/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4943 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171018/3eb9ed91/attachment.bin>

From alicia.detelich at yale.edu  Wed Oct 18 16:00:16 2017
From: alicia.detelich at yale.edu (Detelich, Alicia)
Date: Wed, 18 Oct 2017 20:00:16 +0000
Subject: [Archivesspace_Users_Group] batch re-ordering of
 controlled	value lists; script/plugin, anyone?
Message-ID: <MWHPR08MB348590BAEF08F3FCE73997618E4D0@MWHPR08MB3485.namprd08.prod.outlook.com>

Hi Bobbi,

In case you want to avoid making the change via the database, I have a python script that will do what you are looking for, using a CSV as input. If you can get a list of enumeration value URIs from the database and output it to a CSV, using something like:

select CONCAT('/config/enumeration_values/', ev.id) as URI
                , position
                , value
from enumeration_value ev
WHERE ev.enumeration_id = whatever the enumeration is for extent types in your instance

you can then change the positions in the 2nd column to whatever you want, and use that CSV as the input for the script at this link:
https://github.com/ucancallmealicia/archivesspace-api-public/blob/master/update_enum_val_positions.py

I haven?t used this script in production, but it has worked perfectly well for me when playing around with our test data.

Hope this helps.

Alicia

Alicia Detelich
Archivist
Manuscripts and Archives
Yale University Libraries
alicia.detelich at yale.edu

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven (sdm7g)
Sent: Wednesday, October 18, 2017 3:30 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] batch re-ordering of controlled value lists; script/plugin, anyone?


It looks like the positioning would be very simple to do in mysql as you only have to modify the position value in the table ? no complicated joins required. You could do it interactively with a GUI frontend like Sequel Pro or MySQLWorkbench. Just make sure you don?t leave any duplicate positions.

If you already have a table of enum values and new positions, and you want to do it programmatically, then you can load those pairs as a temporary table, and create a function return position given value string, and use that function in your update statement rather than try to explicitly iterate over the tables.

Merging enumeration values, on the other hand, is more complicated, and I would leave it to the frontend/backend, and not try MySQL surgery.

We are doing a similar controlled value cleanup.
The issue we?re having is that we have several repositories, and the frontend view and list of number of related items and links are repository based, so cleanup requires tediously switching between repositories trying to find the resources that are still linked to those values.

Does the merge operation also only merge enumeration_values for the current repository ?
( I *think* that is the case, but I?m not sure. )

Perhaps, if you?re logged in on an admin account, it should have an option for searching across repositories.


? Steve Majewski


On Oct 18, 2017, at 2:06 PM, Fox, Bobbi <bobbi_fox at harvard.edu<mailto:bobbi_fox at harvard.edu>> wrote:

In the course of adapting ArchivesSpace to Harvard?s needs, we?ve ended up with some very weedy controlled values lists (extent type > 200 values! -- of course, some of them need to be removed) with arbitrary positioning.  Our support team is tasked with the job of wrangling the lists with a defined order, and the interactive ?move up/down one position at a time, wait for the server to refresh, etc.? is really tedious.

Has anyone written a script/created a plugin that would do this with less effort?  I?m inclined to do it at the mysql level, rather than write an extension to the backend/controller/enumeration.rb, but maybe someone has done this already?

Thanks,
Bobbi
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171018/ed914261/attachment.html>

From alicia.detelich at yale.edu  Wed Oct 18 16:28:19 2017
From: alicia.detelich at yale.edu (Detelich, Alicia)
Date: Wed, 18 Oct 2017 20:28:19 +0000
Subject: [Archivesspace_Users_Group] batch re-ordering of
	controlled	value	lists; script/plugin, anyone?
In-Reply-To: <330E3F6E-D351-47D9-9876-EDDACF295015@virginia.edu>
References: <BN6PR07MB3492EB22E765B19088165F10904D0@BN6PR07MB3492.namprd07.prod.outlook.com>
 <330E3F6E-D351-47D9-9876-EDDACF295015@virginia.edu>
Message-ID: <MWHPR08MB3485E603E91EFC17E0BFCEA38E4D0@MWHPR08MB3485.namprd08.prod.outlook.com>

Hi Steve,

I agree that being able to search across repositories would be a very useful option for admin users. As a workaround, I have some queries that will find all resource or archival object records (can also be extended to digital objects, accessions, etc.) that are linked to a certain enumeration. I have one for extent types here - https://github.com/ucancallmealicia/archivesspace-sql/blob/master/extent_type_rec_links.sql. I can also try to dig up the one I have for container profiles if you?d like - it generally follows the same process, just using different tables.

Alicia

Alicia Detelich
Archivist
Manuscripts and Archives
Yale University Libraries
alicia.detelich at yale.edu

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven (sdm7g)
Sent: Wednesday, October 18, 2017 3:30 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] batch re-ordering of controlled value lists; script/plugin, anyone?


It looks like the positioning would be very simple to do in mysql as you only have to modify the position value in the table ? no complicated joins required. You could do it interactively with a GUI frontend like Sequel Pro or MySQLWorkbench. Just make sure you don?t leave any duplicate positions.

If you already have a table of enum values and new positions, and you want to do it programmatically, then you can load those pairs as a temporary table, and create a function return position given value string, and use that function in your update statement rather than try to explicitly iterate over the tables.

Merging enumeration values, on the other hand, is more complicated, and I would leave it to the frontend/backend, and not try MySQL surgery.

We are doing a similar controlled value cleanup.
The issue we?re having is that we have several repositories, and the frontend view and list of number of related items and links are repository based, so cleanup requires tediously switching between repositories trying to find the resources that are still linked to those values.

Does the merge operation also only merge enumeration_values for the current repository ?
( I *think* that is the case, but I?m not sure. )

Perhaps, if you?re logged in on an admin account, it should have an option for searching across repositories.


? Steve Majewski


On Oct 18, 2017, at 2:06 PM, Fox, Bobbi <bobbi_fox at harvard.edu<mailto:bobbi_fox at harvard.edu>> wrote:

In the course of adapting ArchivesSpace to Harvard?s needs, we?ve ended up with some very weedy controlled values lists (extent type > 200 values! -- of course, some of them need to be removed) with arbitrary positioning.  Our support team is tasked with the job of wrangling the lists with a defined order, and the interactive ?move up/down one position at a time, wait for the server to refresh, etc.? is really tedious.

Has anyone written a script/created a plugin that would do this with less effort?  I?m inclined to do it at the mysql level, rather than write an extension to the backend/controller/enumeration.rb, but maybe someone has done this already?

Thanks,
Bobbi
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171018/cdde1e1f/attachment.html>

From sdm7g at virginia.edu  Wed Oct 18 17:39:04 2017
From: sdm7g at virginia.edu (Majewski, Steven (sdm7g))
Date: Wed, 18 Oct 2017 21:39:04 +0000
Subject: [Archivesspace_Users_Group] batch re-ordering
	of	controlled	value	lists; script/plugin, anyone?
In-Reply-To: <MWHPR08MB3485E603E91EFC17E0BFCEA38E4D0@MWHPR08MB3485.namprd08.prod.outlook.com>
References: <BN6PR07MB3492EB22E765B19088165F10904D0@BN6PR07MB3492.namprd07.prod.outlook.com>
 <330E3F6E-D351-47D9-9876-EDDACF295015@virginia.edu>
 <MWHPR08MB3485E603E91EFC17E0BFCEA38E4D0@MWHPR08MB3485.namprd08.prod.outlook.com>
Message-ID: <62D4392D-6F82-4B82-9FA7-62D9460195F5@virginia.edu>


Yes. I can also get the info by either directly querying Solr via the Solr console with query params I pulled from the staff interface links:

extent_type_enum_s:arbitrary_unit OR processing_total_extent_type_enum_s:arbitrary_unit

( and usually adding field list params to limit the output per hit, and increasing rows to get more hits returned. ) 


It also looks like it works to grab the query params from the staff interface search, append them to the backend host base search URL as params, and append ?&page=1? param ( and maybe also &page_size=$whatever ).


Just need to figure out how to add this to the frontend. 

? Steve


> On Oct 18, 2017, at 4:28 PM, Detelich, Alicia <alicia.detelich at yale.edu> wrote:
> 
> Hi Steve,
>  
> I agree that being able to search across repositories would be a very useful option for admin users. As a workaround, I have some queries that will find all resource or archival object records (can also be extended to digital objects, accessions, etc.) that are linked to a certain enumeration. I have one for extent types here - https://github.com/ucancallmealicia/archivesspace-sql/blob/master/extent_type_rec_links.sql <https://github.com/ucancallmealicia/archivesspace-sql/blob/master/extent_type_rec_links.sql>. I can also try to dig up the one I have for container profiles if you?d like - it generally follows the same process, just using different tables.
>  
> Alicia
>  
> Alicia Detelich
> Archivist
> Manuscripts and Archives
> Yale University Libraries
> alicia.detelich at yale.edu <mailto:alicia.detelich at yale.edu>
>  
> From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org]On Behalf Of Majewski, Steven (sdm7g)
> Sent: Wednesday, October 18, 2017 3:30 PM
> To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
> Subject: Re: [Archivesspace_Users_Group] batch re-ordering of controlled value lists; script/plugin, anyone?
>  
>  
> It looks like the positioning would be very simple to do in mysql as you only have to modify the position value in the table ? no complicated joins required. You could do it interactively with a GUI frontend like Sequel Pro or MySQLWorkbench. Just make sure you don?t leave any duplicate positions. 
>  
> If you already have a table of enum values and new positions, and you want to do it programmatically, then you can load those pairs as a temporary table, and create a function return position given value string, and use that function in your update statement rather than try to explicitly iterate over the tables. 
>  
> Merging enumeration values, on the other hand, is more complicated, and I would leave it to the frontend/backend, and not try MySQL surgery. 
>  
> We are doing a similar controlled value cleanup. 
> The issue we?re having is that we have several repositories, and the frontend view and list of number of related items and links are repository based, so cleanup requires tediously switching between repositories trying to find the resources that are still linked to those values. 
>  
> Does the merge operation also only merge enumeration_values for the current repository ?  
> ( I *think* that is the case, but I?m not sure. ) 
>  
> Perhaps, if you?re logged in on an admin account, it should have an option for searching across repositories.  
>  
>  
> ? Steve Majewski
>  
>  
> On Oct 18, 2017, at 2:06 PM, Fox, Bobbi <bobbi_fox at harvard.edu <mailto:bobbi_fox at harvard.edu>> wrote:
>  
> In the course of adapting ArchivesSpace to Harvard?s needs, we?ve ended up with some very weedy controlled values lists (extent type > 200 values! -- of course, some of them need to be removed) with arbitrary positioning.  Our support team is tasked with the job of wrangling the lists with a defined order, and the interactive ?move up/down one position at a time, wait for the server to refresh, etc.? is really tedious.
>  
> Has anyone written a script/created a plugin that would do this with less effort?  I?m inclined to do it at the mysql level, rather than write an extension to the backend/controller/enumeration.rb, but maybe someone has done this already?
>  
> Thanks,
> Bobbi
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org <mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group <http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group>
>  
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171018/83851fb6/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4943 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171018/83851fb6/attachment.bin>

From CurbowJ at bvu.edu  Thu Oct 19 13:56:10 2017
From: CurbowJ at bvu.edu (Joan Curbow)
Date: Thu, 19 Oct 2017 17:56:10 +0000
Subject: [Archivesspace_Users_Group] Voila! You can already search within a
	collection
Message-ID: <CY1PR05MB2362C2FA34FB089B7597E549B5420@CY1PR05MB2362.namprd05.prod.outlook.com>

Boy, do I feel dumb. I answered my own question from a couple of days ago. You CAN search within a collection, and it should have been the first thing I tried, but, of course, I didn?t.

Ctrl-F, the old standby, works like a charm. A lovely extra search box appears, and you can type in a search term, and it will tell you how many instances appear within that collection, and hitting enter will take you to each instance. WONDERFUL!!

Just thought I?d share.

Sincerely,

Joan Curbow
Reference Librarian and Archivist
Buena Vista University Library
Buena Vista University
610 West Fourth Street
Storm Lake, Iowa  50588
712.749.2094
www.library.bvu.edu<http://www.library.bvu.edu>??






-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171019/174386b6/attachment.html>

From ltang5 at lib.msu.edu  Thu Oct 19 14:09:52 2017
From: ltang5 at lib.msu.edu (Tang, Lydia)
Date: Thu, 19 Oct 2017 18:09:52 +0000
Subject: [Archivesspace_Users_Group] Voila! You can already search
 within a collection
In-Reply-To: <CY1PR05MB2362C2FA34FB089B7597E549B5420@CY1PR05MB2362.namprd05.prod.outlook.com>
References: <CY1PR05MB2362C2FA34FB089B7597E549B5420@CY1PR05MB2362.namprd05.prod.outlook.com>
Message-ID: <9DDC5E98-81A6-4EBE-B905-96B7E4F05052@lib.msu.edu>

Thanks, Joan!  I am not sure if that works on a Mac but that function would be handy.  On a Mac, I can control F to find anything on the collection and series-levels, but anything further nested is a no-go for me, at least, that?s how it seems.
Lydia
From: <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Joan Curbow <CurbowJ at bvu.edu>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Date: Thursday, October 19, 2017 at 1:56 PM
To: "archivesspace_users_group at lyralists.lyrasis.org" <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Voila! You can already search within a collection

Boy, do I feel dumb. I answered my own question from a couple of days ago. You CAN search within a collection, and it should have been the first thing I tried, but, of course, I didn?t.

Ctrl-F, the old standby, works like a charm. A lovely extra search box appears, and you can type in a search term, and it will tell you how many instances appear within that collection, and hitting enter will take you to each instance. WONDERFUL!!

Just thought I?d share.

Sincerely,

Joan Curbow
Reference Librarian and Archivist
Buena Vista University Library
Buena Vista University
610 West Fourth Street
Storm Lake, Iowa  50588
712.749.2094
www.library.bvu.edu<http://www.library.bvu.edu>??







From CurbowJ at bvu.edu  Thu Oct 19 14:12:10 2017
From: CurbowJ at bvu.edu (Joan Curbow)
Date: Thu, 19 Oct 2017 18:12:10 +0000
Subject: [Archivesspace_Users_Group] Voila! You can already search
 within a collection
In-Reply-To: <9DDC5E98-81A6-4EBE-B905-96B7E4F05052@lib.msu.edu>
References: <CY1PR05MB2362C2FA34FB089B7597E549B5420@CY1PR05MB2362.namprd05.prod.outlook.com>
 <9DDC5E98-81A6-4EBE-B905-96B7E4F05052@lib.msu.edu>
Message-ID: <CY1PR05MB23626C6607FF20E93A7A5748B5420@CY1PR05MB2362.namprd05.prod.outlook.com>

Ah, yes, well Macs do their own thing, don't they? I have one at home, which I really love, but, at work, I am happy to have a PC.

Joan

-----Original Message-----
From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Tang, Lydia
Sent: Thursday, October 19, 2017 1:10 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Voila! You can already search within a collection

Thanks, Joan!  I am not sure if that works on a Mac but that function would be handy.  On a Mac, I can control F to find anything on the collection and series-levels, but anything further nested is a no-go for me, at least, that?s how it seems.
Lydia
From: <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Joan Curbow <CurbowJ at bvu.edu>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Date: Thursday, October 19, 2017 at 1:56 PM
To: "archivesspace_users_group at lyralists.lyrasis.org" <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Voila! You can already search within a collection

Boy, do I feel dumb. I answered my own question from a couple of days ago. You CAN search within a collection, and it should have been the first thing I tried, but, of course, I didn?t.

Ctrl-F, the old standby, works like a charm. A lovely extra search box appears, and you can type in a search term, and it will tell you how many instances appear within that collection, and hitting enter will take you to each instance. WONDERFUL!!

Just thought I?d share.

Sincerely,

Joan Curbow
Reference Librarian and Archivist
Buena Vista University Library
Buena Vista University
610 West Fourth Street
Storm Lake, Iowa  50588
712.749.2094
www.library.bvu.edu<http://www.library.bvu.edu>??






_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

From lwsellar at ncsu.edu  Thu Oct 19 14:35:59 2017
From: lwsellar at ncsu.edu (Linda Sellars)
Date: Thu, 19 Oct 2017 14:35:59 -0400
Subject: [Archivesspace_Users_Group] Voila! You can already search
 within a collection
In-Reply-To: <9DDC5E98-81A6-4EBE-B905-96B7E4F05052@lib.msu.edu>
References: <CY1PR05MB2362C2FA34FB089B7597E549B5420@CY1PR05MB2362.namprd05.prod.outlook.com>
 <9DDC5E98-81A6-4EBE-B905-96B7E4F05052@lib.msu.edu>
Message-ID: <CAFKYgO1OLxbWeHeSBC1xK_gTsw83CbDaZMG+wn4K3_u0ARXjKQ@mail.gmail.com>

For me, control-f searches whatever is visible on the screen (including
stuff that would be visible if I scroll down). So if I open all the series
and subseries so that I can see the list of components, control-f will
search that list. If I want to search a big collection, I start opening the
series from the bottom so that I don't have to wait for each series to open
completely before I can click on the next one. If you have a lot of
nesting, it can take a while to do this and it's easy to miss a subseries
so that you are not searching whatever is in that one. For the most part,
it works pretty well.

On Thu, Oct 19, 2017 at 2:09 PM, Tang, Lydia <ltang5 at lib.msu.edu> wrote:

> Thanks, Joan!  I am not sure if that works on a Mac but that function
> would be handy.  On a Mac, I can control F to find anything on the
> collection and series-levels, but anything further nested is a no-go for
> me, at least, that?s how it seems.
> Lydia
> From: <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf
> of Joan Curbow <CurbowJ at bvu.edu>
> Reply-To: Archivesspace Users Group <archivesspace_users_group@
> lyralists.lyrasis.org>
> Date: Thursday, October 19, 2017 at 1:56 PM
> To: "archivesspace_users_group at lyralists.lyrasis.org" <
> archivesspace_users_group at lyralists.lyrasis.org>
> Subject: [Archivesspace_Users_Group] Voila! You can already search within
> a collection
>
> Boy, do I feel dumb. I answered my own question from a couple of days ago.
> You CAN search within a collection, and it should have been the first thing
> I tried, but, of course, I didn?t.
>
> Ctrl-F, the old standby, works like a charm. A lovely extra search box
> appears, and you can type in a search term, and it will tell you how many
> instances appear within that collection, and hitting enter will take you to
> each instance. WONDERFUL!!
>
> Just thought I?d share.
>
> Sincerely,
>
> Joan Curbow
> Reference Librarian and Archivist
> Buena Vista University Library
> Buena Vista University
> 610 West Fourth Street
> Storm Lake, Iowa  50588
> 712.749.2094
> www.library.bvu.edu<http://www.library.bvu.edu>??
>
>
>
>
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>



-- 
Linda Sellars
Head of Technical Services for Special Collections
Special Collections Research Center, NCSU Libraries
lwsellar at ncsu.edu
919-515-8120
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171019/ebf97dfd/attachment.html>

From Christine.Kim at lyrasis.org  Thu Oct 19 15:25:24 2017
From: Christine.Kim at lyrasis.org (Christine Kim)
Date: Thu, 19 Oct 2017 19:25:24 +0000
Subject: [Archivesspace_Users_Group] Webinar Announcement: ArchivesSpace PUI
 Overview and Implementation Strategies - Oct. 26
Message-ID: <MWHPR08MB2495786BE3854B2B14C67B4EF5420@MWHPR08MB2495.namprd08.prod.outlook.com>

ArchivesSpace PUI Overview and Implementation Strategies

When: Thursday, October 26, 2017
Time: 1:00 p.m. - 2:30 p.m. EST (10:00 a.m. - 11:30 a.m. PST)
Where: Webinar at http://lyrasis.adobeconnect.com/rnz7zrtmy04h/
No registration required. The session is limited to the first 100 participants. Please feel free to host a webinar viewing group. The webinar will be recorded and available for viewing at a later date.

Webinar description:
Mark Custer and Susan Pyzynski were deeply entrenched in the public interface as they led the community effort of the Public User Interface Enhancement Working Group to shape this essential access point for archival collections. Now they have moved onto their next great challenge - implementing the PUI at their own institutions. Mark and Susan will each share the strategies they have created to roll out the new PUI. Both institutions aim to be using the new PUI by early next year.

Grand Valley State University has been using the ArchivesSpace PUI since 2014 and have already rolled out the new public interface. Annie Benefiel and Leigh Rupinski will share valuable insight on how the PUI has affected their day-to-day responsibilities of providing access to finding aids, as well as public reception and adapting their instruction for students and researchers.

Please join us on October 26 at 1-2:30 EST as Mark, Susan, Annie, and Leigh as they share their experiences. Please feel free to bring any questions you have on the new public interface!

Presenters:
Mark Custer is an archivist and metadata coordinator at the Beinecke Rare Book & Manuscript Library. He has been heavily involved with the implementation of ArchivesSpace at Yale University, and he is the former chair of the ArchivesSpace Public User Interface Enhancement Project. Mark is a graduate of the School of Information Studies at Syracuse University.

Susan Pyzynski is the Associate Librarian of Houghton Library for Technical Services, Harvard University. Previously, she was the Librarian for Special Collections and Digital Initiatives at Brandeis University. She is leading a project to replace Harvard's archival discovery system.

Annie Benefiel is the Archivist for Collection Management at Grand Valley State University. She oversees the accessioning, processing, and preservation of archival and manuscript collections and manages metadata for archival and digital collections in the Special Collections & University Archives.

Leigh Rupinski is Archivist for Public Services & Community Engagement at Grand Valley State University. She is responsible for instruction, reference, assessment, and other outreach activities for Special Collections & University Archives.

Who should attend:
Everyone interested in learning about the new ArchivesSpace public user interface.

Questions?
Please contact Kim at christine.kim at lyrasis.org<mailto:christine.kim at lyrasis.org>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171019/4d8ab179/attachment.html>

From ludwigpossie at weber.edu  Mon Oct 23 14:14:31 2017
From: ludwigpossie at weber.edu (Ludwig Possie)
Date: Mon, 23 Oct 2017 12:14:31 -0600
Subject: [Archivesspace_Users_Group] Upgrading from 1.09
Message-ID: <CA+OpDmYcQ2ju+JbL5aU_6TtxxJvMu4GRkfUveALGe4i+U26xbg@mail.gmail.com>

I'm trying to upgrade our current version of ArchivesSpace 1.0.9 to the
latest version.  Is it safe to make the jump from 1.09 to 2.2.0?  If not
are there any suggestion on what order I should run the upgrade?

Looking at the available releases the oldest available version is 2.0.0.
How safe is it to make the jump from 1.0.9 to 2.0.0?  Thx.

-- 
Ludwig Possi?
Systems Admin
Stewart Library
Weber State University
801-626-8093
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171023/feb6ff7d/attachment.html>

From sdm7g at virginia.edu  Mon Oct 23 14:39:21 2017
From: sdm7g at virginia.edu (Majewski, Steven (sdm7g))
Date: Mon, 23 Oct 2017 18:39:21 +0000
Subject: [Archivesspace_Users_Group] Upgrading from 1.09
In-Reply-To: <CA+OpDmYcQ2ju+JbL5aU_6TtxxJvMu4GRkfUveALGe4i+U26xbg@mail.gmail.com>
References: <CA+OpDmYcQ2ju+JbL5aU_6TtxxJvMu4GRkfUveALGe4i+U26xbg@mail.gmail.com>
Message-ID: <568CF232-FE69-42D0-94E2-E97164D92606@virginia.edu>

Older releases ARE available ? you just have click thru to the next page (at the bottom). 

[ Is there a way to filter out the pre-releases from GitHub /releases?  I don?t see anything in the API. ] 

I would advise migrating to 1.5.x first and verifying that the container conversion process has no errors before upgrading to 2.0 or 2.1.  ( If there are any issues with the conversion, I found it somewhat more difficult to find and fix them in 2.0 than in 1.5.x ) 

? Steve Majewski


> On Oct 23, 2017, at 2:14 PM, Ludwig Possie <ludwigpossie at weber.edu> wrote:
> 
> I'm trying to upgrade our current version of ArchivesSpace 1.0.9 to the latest version.  Is it safe to make the jump from 1.09 to 2.2.0?  If not are there any suggestion on what order I should run the upgrade?
> 
> Looking at the available releases the oldest available version is 2.0.0.  How safe is it to make the jump from 1.0.9 to 2.0.0?  Thx.
> 
> -- 
> Ludwig Possi?
> Systems Admin
> Stewart Library
> Weber State University
> 801-626-8093
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171023/3b9b5107/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4943 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171023/3b9b5107/attachment.bin>

From christine.dibella at lyrasis.org  Mon Oct 23 15:03:01 2017
From: christine.dibella at lyrasis.org (Christine Di Bella)
Date: Mon, 23 Oct 2017 19:03:01 +0000
Subject: [Archivesspace_Users_Group] Upgrading from 1.09
In-Reply-To: <568CF232-FE69-42D0-94E2-E97164D92606@virginia.edu>
References: <CA+OpDmYcQ2ju+JbL5aU_6TtxxJvMu4GRkfUveALGe4i+U26xbg@mail.gmail.com>
 <568CF232-FE69-42D0-94E2-E97164D92606@virginia.edu>
Message-ID: <MWHPR08MB3456E2A94158AF79050DA3FFF1460@MWHPR08MB3456.namprd08.prod.outlook.com>

Dear Ludwig,

ArchivesSpace v1.0.9 came out in May 2014, and, due to various data model changes since then, you will have to make a couple stops along the way to get to 2.2.0. The upgrading documentation at https://github.com/archivesspace/archivesspace/blob/master/UPGRADING.md explains both general and special considerations for moving from version to version.

For your particular upgrade, there will be at least two steps, 1.0.9 to a version from 1.5.0 to 2.0.1 (Steve suggests a 1.5.x version will be best), then 2.2.0 to get to the most current version. With the upgrade to 2.0.1, you?ll be moving to the newer container model, and will want to pay particular attention to the information in the special upgrade instructions at https://github.com/archivesspace/archivesspace/blob/master/UPGRADING_1.5.0.md. We do maintain all of our releases on Github (https://github.com/archivesspace/archivesspace/releases), so getting the intermediate releases will not be a problem.

Because it?s quite a big jump, you may want to first upgrade from 1.0.9 to 1.4.2, then the 1.5.0 to 2.0.1 version of your choice to make the container management upgrade, then 2.0.1 to 2.2.0 to get to the most current version. But maybe do a trial or two of each to see which has more satisfying results.

In either case, you?ll want to have your archivists check the data between upgrades to make sure that what they?re seeing is what they expect to see, and check your logs if it isn?t. You can also reach out to the program team at ArchivesSpaceHome at lyrasis.org<mailto:ArchivesSpaceHome at lyrasis.org> at any point if you?d like to put in a technical support ticket for additional assistance.

Please let us ? and the list ? know if you have other questions and how it goes. I?m not aware of anyone who has made the upgrade from this early a version recently, but I?m sure you?re not alone in running an older version of ArchivesSpace, so whatever is learned during your upgrade is sure to help others.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)

[ASpaceOrgHomeMedium]



From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Majewski, Steven (sdm7g)
Sent: Monday, October 23, 2017 2:39 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Upgrading from 1.09

Older releases ARE available ? you just have click thru to the next page (at the bottom).

[ Is there a way to filter out the pre-releases from GitHub /releases?  I don?t see anything in the API. ]

I would advise migrating to 1.5.x first and verifying that the container conversion process has no errors before upgrading to 2.0 or 2.1.  ( If there are any issues with the conversion, I found it somewhat more difficult to find and fix them in 2.0 than in 1.5.x )

? Steve Majewski


On Oct 23, 2017, at 2:14 PM, Ludwig Possie <ludwigpossie at weber.edu<mailto:ludwigpossie at weber.edu>> wrote:

I'm trying to upgrade our current version of ArchivesSpace 1.0.9 to the latest version.  Is it safe to make the jump from 1.09 to 2.2.0?  If not are there any suggestion on what order I should run the upgrade?

Looking at the available releases the oldest available version is 2.0.0.  How safe is it to make the jump from 1.0.9 to 2.0.0?  Thx.

--
Ludwig Possi?
Systems Admin
Stewart Library
Weber State University
801-626-8093
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171023/be86da81/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 6608 bytes
Desc: image001.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171023/be86da81/attachment.jpg>

From dfwalton at ua.edu  Mon Oct 23 16:03:32 2017
From: dfwalton at ua.edu (Walton, Donnelly)
Date: Mon, 23 Oct 2017 20:03:32 +0000
Subject: [Archivesspace_Users_Group] "We're sorry,
 something went wrong" after requesting material via ArchivesSpace
In-Reply-To: <BN6PR11MB1442E536A7F886A236D2BC0695660@BN6PR11MB1442.namprd11.prod.outlook.com>
References: <942417AC-8949-4787-96BC-084E8FA17FDF@lib.msu.edu>
 <BN6PR11MB1442956C8B117C022A76AD7695660@BN6PR11MB1442.namprd11.prod.outlook.com>
 <BN3PR08MB130394A46BBCED1593BAC8F88C660@BN3PR08MB1303.namprd08.prod.outlook.com>
 <BN6PR11MB1442E536A7F886A236D2BC0695660@BN6PR11MB1442.namprd11.prod.outlook.com>
Message-ID: <e13866dad49445808232314644651aa5@ua.edu>

We have recently upgraded to 2.1.2 and are doing a soft launch of the PUI.  Where do we go to setup the feature and tell the system where to send the emails?

Many thanks,
Donnelly

Donnelly Lancaster Walton
Archival Access Coordinator, Special Collections
University Libraries
The University of Alabama<https://www.ua.edu/>
W. S. Hoole Library, Mary Harmon Bryant Hall
Box 870266
Tuscaloosa, AL 35487
Office 205-348-0505<tel:205-348-0505>
dfwalton at ua.edu<mailto:dfwalton at ua.edu> | https://www.lib.ua.edu/libraries/hoole/
[The University of Alabama]<https://www.ua.edu/>



From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Kevin Clair
Sent: Thursday, September 21, 2017 4:39 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] "We're sorry, something went wrong" after requesting material via ArchivesSpace

We?ve been able to receive the e-mail confirmations ArchivesSpace sends, both with my personal e-mail and with LibAnswers. It?s only when it tries to render request_received_email.html that it throws the error.  -k

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Custer, Mark
Sent: Thursday, September 21, 2017 3:31 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] "We're sorry, something went wrong" after requesting material via ArchivesSpace


All,



I wish that I could offer technical advice on how to get things set up, but unfortunately I'm of no use in this case.  I do know that this feature used to be configured on our Test Corpus site, though, and that it functioned as expected at that time.



Here's what a message would look like that's sent to a patron (as you can see, it doesn?t include ALL of the data, like what the staff would receive), and they shouldn?t see an error message when requesting after everything has been configured to allow email requesting:



Thank you for your request
Record Requested
Title: Watercolor of Brassie fly nymph (fishing fly)
URL: http://aspace.hudmol.com:7310/repositories/14/digital_objects/4375<https://urldefense.proofpoint.com/v2/url?u=http-3A__aspace.hudmol.com-3A7310_repositories_14_digital-5Fobjects_4375&d=DwMCaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=PjInOOP-yhZdvfCxvJExNB_3mSrTAYOjE-Ld3wjgoMo&m=hES0nr_7CQRdsaxxcbpbcujfoSJVVVtSbikTnQDfBMQ&s=fEcKFYM5n4pdR51TDuNa_20WsC4Rr2r-cKOf4FBNyuk&e=>
Your Details
Name: m
Email: mark.custer at yale.edu<mailto:mark.custer at yale.edu>
Date:
Notes for Staff:



I don?t believe that the email that was sent to staff ever had a specialized template, like this one, however.  It was just meant to be a proof of concept showing how all of the request data could be sent in an email message in order to fulfill the user story about allowing researchers to make requests directly from the PUI.



Hopefully others will be able to weigh in soon with more detailed instructions how to get this configured properly.  I seem to remember that with the Gmail account that we used for testing, Gmail had to be told to allow the use of unsecured apps (though I?m not sure why exactly that was or might be).



Just so that I?m clear, though? Lydia, Kevin: it sounds like you have it configured to receive emails okay, but the emails to whomever requested the material is not being sent/received.  Is that correct?



Mark







-----Original Message-----
From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Kevin Clair
Sent: Thursday, 21 September, 2017 5:15 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] "We're sorry, something went wrong" after requesting material via ArchivesSpace



We see similar behavior, and have turned off requesting on the public site because of it. The e-mail requests go through but the users see the error page instead of a confirmation. From the logs:







INFO: I, [2017-09-21T15:08:03.838360 #4548]  INFO -- : [5c583ccc-1669-40c4-9f90-81f09fac562b] Started POST "/fill_request" for 192.168.123.1 at 2017-09-21 15:08:03 -0600







[the e-mail successfully sends here; log output omitted]







Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log



INFO: I, [2017-09-21T15:08:09.740133 #4548]  INFO -- : [5c583ccc-1669-40c4-9f90-81f09fac562b] Completed 500 Internal Server Error in 5862ms







Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log



INFO: F, [2017-09-21T15:08:09.791554 #4548] FATAL -- : [5c583ccc-1669-40c4-9f90-81f09fac562b]







Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log



INFO: F, [2017-09-21T15:08:09.797765 #4548] FATAL -- : [5c583ccc-1669-40c4-9f90-81f09fac562b] ActionView::Template::Error (undefined method `app_prefix' for #<#<Class:0x46d13c0a>:0x59036603>):







Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log



INFO: F, [2017-09-21T15:08:09.809421 #4548] FATAL -- : [5c583ccc-1669-40c4-9f90-81f09fac562b]     4:   <h2>Record Requested</h2>



[5c583ccc-1669-40c4-9f90-81f09fac562b]     5:   <strong>Title</strong>: <%= @request.title %><br>



[5c583ccc-1669-40c4-9f90-81f09fac562b]     6:   <% url = "#{AppConfig[:public_proxy_url].sub(/\/^/, '')}#{@request.request_uri}<mailto:%7d#{@request.request_uri}>" %>



[5c583ccc-1669-40c4-9f90-81f09fac562b]     7:   <strong>URL</strong>: <%= link_to url, app_prefix(url) %>



[5c583ccc-1669-40c4-9f90-81f09fac562b]     8: </div>



[5c583ccc-1669-40c4-9f90-81f09fac562b]     9:



[5c583ccc-1669-40c4-9f90-81f09fac562b]    10: <div class="user">







Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log



INFO: F, [2017-09-21T15:08:09.810141 #4548] FATAL -- : [5c583ccc-1669-40c4-9f90-81f09fac562b]







Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log



INFO: F, [2017-09-21T15:08:09.810661 #4548] FATAL -- : [5c583ccc-1669-40c4-9f90-81f09fac562b] app/views/request_mailer/request_received_email.html.erb:7:in `_app_views_request_mailer_request_received_email_html_erb___227123848_2378'



[5c583ccc-1669-40c4-9f90-81f09fac562b] app/mailers/request_mailer.rb:7:in `request_received_email'



[5c583ccc-1669-40c4-9f90-81f09fac562b] app/controllers/requests_controller.rb:11:in `make_request'







-k







-----Original Message-----



From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Tang, Lydia



Sent: Thursday, September 21, 2017 1:19 PM



To: 'archivesspace_users_group at lyralists.lyrasis.org'



Subject: [Archivesspace_Users_Group] "We're sorry, something went wrong" after requesting material via ArchivesSpace







Hello, we recently upgraded from 2.1.1 from 1.5.3.  With our users taking advantage of the request feature through our PUI, they have received this ?We?re sorry something went wrong? message after submitting their request.  Is this normal?  Is there a tweak we need to fill in order to gracefully conclude the request and return to the PUI?



Thanks!



Lydia



_______________________________________________

Archivesspace_Users_Group mailing list

Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>

https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwIGaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=yCOvlNmPPowIK_FHWplCUKa3UJhEsCZ5AWPTGq2qjMk&s=blzfAbR70wCLQrOIDae9pDrRNAZ_79j4aYMufxVfe2w&e=
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171023/7f6120be/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 6052 bytes
Desc: image001.gif
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171023/7f6120be/attachment.gif>

From smithkr at mit.edu  Tue Oct 24 14:02:43 2017
From: smithkr at mit.edu (Kari R Smith)
Date: Tue, 24 Oct 2017 18:02:43 +0000
Subject: [Archivesspace_Users_Group] Having trouble with permission to
	Manage Top Containers
Message-ID: <29F559819ACA9A4FBF208407D4B63ABB01401E3228@OC11expo28.exchange.mit.edu>

Hello,
We have a permission group with:
create/update top container records  &
create/update/delete container profile records

However, users with this permission group do not have Manage Top Container as an option in the cogwheel menu to the right of the Repo Name.

Thoughts?  We are hosted by LYRASIS and recently upgraded to 2.1.7. Does it take a long time for the permissions to be changed? We did this on Friday and again yesterday afternoon but no changes for that user.

Thanks for suggestions, help.
Kari


--------------------------------------------------------------------------
Kari R. Smith
Institute Archivist and Program Head, Digital Archives
Institute Archives & Special Collections, MIT Libraries
Massachusetts Institute of Technology, Cambridge, Massachusetts 02139
IASC office: 617.258.5568  http://libraries.mit.edu/archives/
she | her | hers   @karirene69  [smithkr at mit.edu]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171024/2b922cee/attachment.html>

From lmcphee at ucsd.edu  Tue Oct 24 14:14:09 2017
From: lmcphee at ucsd.edu (McPhee, Laurel)
Date: Tue, 24 Oct 2017 18:14:09 +0000
Subject: [Archivesspace_Users_Group] Having trouble with permission
	to	Manage Top Containers
In-Reply-To: <29F559819ACA9A4FBF208407D4B63ABB01401E3228@OC11expo28.exchange.mit.edu>
References: <29F559819ACA9A4FBF208407D4B63ABB01401E3228@OC11expo28.exchange.mit.edu>
Message-ID: <DM5PR04MB095425F535C719D0CC58C828DB470@DM5PR04MB0954.namprd04.prod.outlook.com>

Hi Kari,

We experienced this, and through trial and error discovered (I think) that there is a logic mismatch at work in those permissions. The only way someone can see the Manage Top Container option through the cogwheel is if they also have a the "Manage this Repository (change groups and other settings)" box checked. This has caused us some inconvenience because if we want someone to be able to create/update/delete top containers, it stands to reason we would also like them to be able to use the Manage Top Containers tool and all its functionality. But you have to basically make them a repository manager to do so, which is a whole other layer of permissions.

An issue (if it hasn't already been reported) for the Staff Interface group? I'd love to stand corrected though and learn if I am missing another obvious option here, or if there is other reasoning at work.

Laurel

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Kari R Smith
Sent: Tuesday, October 24, 2017 11:03 AM
To: Archivesspace Users Group (archivesspace_users_group at lyralists.lyrasis.org) <archivesspace_users_group at lyralists.lyrasis.org>
Cc: archivesspace at googlegroups.com
Subject: [Archivesspace_Users_Group] Having trouble with permission to Manage Top Containers

Hello,
We have a permission group with:
create/update top container records  &
create/update/delete container profile records

However, users with this permission group do not have Manage Top Container as an option in the cogwheel menu to the right of the Repo Name.

Thoughts?  We are hosted by LYRASIS and recently upgraded to 2.1.7. Does it take a long time for the permissions to be changed? We did this on Friday and again yesterday afternoon but no changes for that user.

Thanks for suggestions, help.
Kari


--------------------------------------------------------------------------
Kari R. Smith
Institute Archivist and Program Head, Digital Archives
Institute Archives & Special Collections, MIT Libraries
Massachusetts Institute of Technology, Cambridge, Massachusetts 02139
IASC office: 617.258.5568  http://libraries.mit.edu/archives/
she | her | hers   @karirene69  [smithkr at mit.edu]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171024/ae4db2a1/attachment.html>

From christine.dibella at lyrasis.org  Tue Oct 24 14:20:46 2017
From: christine.dibella at lyrasis.org (Christine Di Bella)
Date: Tue, 24 Oct 2017 18:20:46 +0000
Subject: [Archivesspace_Users_Group] Having trouble with
	permission	to	Manage Top Containers
In-Reply-To: <DM5PR04MB095425F535C719D0CC58C828DB470@DM5PR04MB0954.namprd04.prod.outlook.com>
References: <29F559819ACA9A4FBF208407D4B63ABB01401E3228@OC11expo28.exchange.mit.edu>
 <DM5PR04MB095425F535C719D0CC58C828DB470@DM5PR04MB0954.namprd04.prod.outlook.com>
Message-ID: <MWHPR08MB34561B72C2480060621416F6F1470@MWHPR08MB3456.namprd08.prod.outlook.com>

Hi Kari and Laurel,

There is a separate permission for delete/bulk update top container records (bulk update is the equivalent to the Manage Top Containers area) - it appearing for users with this level of permissions was fixed in https://archivesspace.atlassian.net/browse/AR-1559. If you assign that permission to a user, do they get that menu item?

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)

[ASpaceOrgHomeMedium]



From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of McPhee, Laurel
Sent: Tuesday, October 24, 2017 2:14 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Having trouble with permission to Manage Top Containers

Hi Kari,

We experienced this, and through trial and error discovered (I think) that there is a logic mismatch at work in those permissions. The only way someone can see the Manage Top Container option through the cogwheel is if they also have a the "Manage this Repository (change groups and other settings)" box checked. This has caused us some inconvenience because if we want someone to be able to create/update/delete top containers, it stands to reason we would also like them to be able to use the Manage Top Containers tool and all its functionality. But you have to basically make them a repository manager to do so, which is a whole other layer of permissions.

An issue (if it hasn't already been reported) for the Staff Interface group? I'd love to stand corrected though and learn if I am missing another obvious option here, or if there is other reasoning at work.

Laurel

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Kari R Smith
Sent: Tuesday, October 24, 2017 11:03 AM
To: Archivesspace Users Group (archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>) <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Cc: archivesspace at googlegroups.com<mailto:archivesspace at googlegroups.com>
Subject: [Archivesspace_Users_Group] Having trouble with permission to Manage Top Containers

Hello,
We have a permission group with:
create/update top container records  &
create/update/delete container profile records

However, users with this permission group do not have Manage Top Container as an option in the cogwheel menu to the right of the Repo Name.

Thoughts?  We are hosted by LYRASIS and recently upgraded to 2.1.7. Does it take a long time for the permissions to be changed? We did this on Friday and again yesterday afternoon but no changes for that user.

Thanks for suggestions, help.
Kari


--------------------------------------------------------------------------
Kari R. Smith
Institute Archivist and Program Head, Digital Archives
Institute Archives & Special Collections, MIT Libraries
Massachusetts Institute of Technology, Cambridge, Massachusetts 02139
IASC office: 617.258.5568  http://libraries.mit.edu/archives/
she | her | hers   @karirene69  [smithkr at mit.edu]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171024/d230e441/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 6608 bytes
Desc: image001.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171024/d230e441/attachment.jpg>

From christine.dibella at lyrasis.org  Tue Oct 24 14:27:52 2017
From: christine.dibella at lyrasis.org (Christine Di Bella)
Date: Tue, 24 Oct 2017 18:27:52 +0000
Subject: [Archivesspace_Users_Group] "We're sorry,
 something went wrong" after requesting material via ArchivesSpace
In-Reply-To: <e13866dad49445808232314644651aa5@ua.edu>
References: <942417AC-8949-4787-96BC-084E8FA17FDF@lib.msu.edu>
 <BN6PR11MB1442956C8B117C022A76AD7695660@BN6PR11MB1442.namprd11.prod.outlook.com>
 <BN3PR08MB130394A46BBCED1593BAC8F88C660@BN3PR08MB1303.namprd08.prod.outlook.com>
 <BN6PR11MB1442E536A7F886A236D2BC0695660@BN6PR11MB1442.namprd11.prod.outlook.com>
 <e13866dad49445808232314644651aa5@ua.edu>
Message-ID: <MWHPR08MB345652024E097D443F33B73AF1470@MWHPR08MB3456.namprd08.prod.outlook.com>

Hi Donnelly,

These settings are controlled by options in the config.rb file on your ArchivesSpace server. A bug and some improvements with the email requesting feature on the PUI were resolved in version 2.2.0, so if you upgrade to that version, if should work correctly. An improvement that was made for 2.2.0 was that if you have a contact email address in a repository record, it can be used as the email address for requests (https://github.com/archivesspace/archivesspace/pull/979) rather than having to specify an email address separately. You will still need to enable the requesting feature and associated settings in the config file, however.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)

[ASpaceOrgHomeMedium]



From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Walton, Donnelly
Sent: Monday, October 23, 2017 4:04 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] "We're sorry, something went wrong" after requesting material via ArchivesSpace

We have recently upgraded to 2.1.2 and are doing a soft launch of the PUI.  Where do we go to setup the feature and tell the system where to send the emails?

Many thanks,
Donnelly

Donnelly Lancaster Walton
Archival Access Coordinator, Special Collections
University Libraries
The University of Alabama<https://www.ua.edu/>
W. S. Hoole Library, Mary Harmon Bryant Hall
Box 870266
Tuscaloosa, AL 35487
Office 205-348-0505<tel:205-348-0505>
dfwalton at ua.edu<mailto:dfwalton at ua.edu> | https://www.lib.ua.edu/libraries/hoole/
[The University of Alabama]<https://www.ua.edu/>



From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Kevin Clair
Sent: Thursday, September 21, 2017 4:39 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] "We're sorry, something went wrong" after requesting material via ArchivesSpace

We?ve been able to receive the e-mail confirmations ArchivesSpace sends, both with my personal e-mail and with LibAnswers. It?s only when it tries to render request_received_email.html that it throws the error.  -k

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Custer, Mark
Sent: Thursday, September 21, 2017 3:31 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] "We're sorry, something went wrong" after requesting material via ArchivesSpace


All,



I wish that I could offer technical advice on how to get things set up, but unfortunately I'm of no use in this case.  I do know that this feature used to be configured on our Test Corpus site, though, and that it functioned as expected at that time.



Here's what a message would look like that's sent to a patron (as you can see, it doesn?t include ALL of the data, like what the staff would receive), and they shouldn?t see an error message when requesting after everything has been configured to allow email requesting:



Thank you for your request
Record Requested
Title: Watercolor of Brassie fly nymph (fishing fly)
URL: http://aspace.hudmol.com:7310/repositories/14/digital_objects/4375<https://urldefense.proofpoint.com/v2/url?u=http-3A__aspace.hudmol.com-3A7310_repositories_14_digital-5Fobjects_4375&d=DwMCaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=PjInOOP-yhZdvfCxvJExNB_3mSrTAYOjE-Ld3wjgoMo&m=hES0nr_7CQRdsaxxcbpbcujfoSJVVVtSbikTnQDfBMQ&s=fEcKFYM5n4pdR51TDuNa_20WsC4Rr2r-cKOf4FBNyuk&e=>
Your Details
Name: m
Email: mark.custer at yale.edu<mailto:mark.custer at yale.edu>
Date:
Notes for Staff:



I don?t believe that the email that was sent to staff ever had a specialized template, like this one, however.  It was just meant to be a proof of concept showing how all of the request data could be sent in an email message in order to fulfill the user story about allowing researchers to make requests directly from the PUI.



Hopefully others will be able to weigh in soon with more detailed instructions how to get this configured properly.  I seem to remember that with the Gmail account that we used for testing, Gmail had to be told to allow the use of unsecured apps (though I?m not sure why exactly that was or might be).



Just so that I?m clear, though? Lydia, Kevin: it sounds like you have it configured to receive emails okay, but the emails to whomever requested the material is not being sent/received.  Is that correct?



Mark







-----Original Message-----
From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Kevin Clair
Sent: Thursday, 21 September, 2017 5:15 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] "We're sorry, something went wrong" after requesting material via ArchivesSpace



We see similar behavior, and have turned off requesting on the public site because of it. The e-mail requests go through but the users see the error page instead of a confirmation. From the logs:







INFO: I, [2017-09-21T15:08:03.838360 #4548]  INFO -- : [5c583ccc-1669-40c4-9f90-81f09fac562b] Started POST "/fill_request" for 192.168.123.1 at 2017-09-21 15:08:03 -0600







[the e-mail successfully sends here; log output omitted]







Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log



INFO: I, [2017-09-21T15:08:09.740133 #4548]  INFO -- : [5c583ccc-1669-40c4-9f90-81f09fac562b] Completed 500 Internal Server Error in 5862ms







Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log



INFO: F, [2017-09-21T15:08:09.791554 #4548] FATAL -- : [5c583ccc-1669-40c4-9f90-81f09fac562b]







Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log



INFO: F, [2017-09-21T15:08:09.797765 #4548] FATAL -- : [5c583ccc-1669-40c4-9f90-81f09fac562b] ActionView::Template::Error (undefined method `app_prefix' for #<#<Class:0x46d13c0a>:0x59036603>):







Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log



INFO: F, [2017-09-21T15:08:09.809421 #4548] FATAL -- : [5c583ccc-1669-40c4-9f90-81f09fac562b]     4:   <h2>Record Requested</h2>



[5c583ccc-1669-40c4-9f90-81f09fac562b]     5:   <strong>Title</strong>: <%= @request.title %><br>



[5c583ccc-1669-40c4-9f90-81f09fac562b]     6:   <% url = "#{AppConfig[:public_proxy_url].sub(/\/^/, '')}#{@request.request_uri}<mailto:%7d#{@request.request_uri}>" %>



[5c583ccc-1669-40c4-9f90-81f09fac562b]     7:   <strong>URL</strong>: <%= link_to url, app_prefix(url) %>



[5c583ccc-1669-40c4-9f90-81f09fac562b]     8: </div>



[5c583ccc-1669-40c4-9f90-81f09fac562b]     9:



[5c583ccc-1669-40c4-9f90-81f09fac562b]    10: <div class="user">







Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log



INFO: F, [2017-09-21T15:08:09.810141 #4548] FATAL -- : [5c583ccc-1669-40c4-9f90-81f09fac562b]







Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log



INFO: F, [2017-09-21T15:08:09.810661 #4548] FATAL -- : [5c583ccc-1669-40c4-9f90-81f09fac562b] app/views/request_mailer/request_received_email.html.erb:7:in `_app_views_request_mailer_request_received_email_html_erb___227123848_2378'



[5c583ccc-1669-40c4-9f90-81f09fac562b] app/mailers/request_mailer.rb:7:in `request_received_email'



[5c583ccc-1669-40c4-9f90-81f09fac562b] app/controllers/requests_controller.rb:11:in `make_request'







-k







-----Original Message-----



From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Tang, Lydia



Sent: Thursday, September 21, 2017 1:19 PM



To: 'archivesspace_users_group at lyralists.lyrasis.org'



Subject: [Archivesspace_Users_Group] "We're sorry, something went wrong" after requesting material via ArchivesSpace







Hello, we recently upgraded from 2.1.1 from 1.5.3.  With our users taking advantage of the request feature through our PUI, they have received this ?We?re sorry something went wrong? message after submitting their request.  Is this normal?  Is there a tweak we need to fill in order to gracefully conclude the request and return to the PUI?



Thanks!



Lydia



_______________________________________________

Archivesspace_Users_Group mailing list

Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>

https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwIGaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=yCOvlNmPPowIK_FHWplCUKa3UJhEsCZ5AWPTGq2qjMk&s=blzfAbR70wCLQrOIDae9pDrRNAZ_79j4aYMufxVfe2w&e=
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171024/4cc6fcbf/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.gif
Type: image/gif
Size: 6052 bytes
Desc: image004.gif
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171024/4cc6fcbf/attachment.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 6608 bytes
Desc: image003.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171024/4cc6fcbf/attachment.jpg>

From rachel.searcy at nyu.edu  Tue Oct 24 14:30:36 2017
From: rachel.searcy at nyu.edu (Rachel Aileen Searcy)
Date: Tue, 24 Oct 2017 14:30:36 -0400
Subject: [Archivesspace_Users_Group] Having trouble with permission to
 Manage Top Containers
In-Reply-To: <MWHPR08MB34561B72C2480060621416F6F1470@MWHPR08MB3456.namprd08.prod.outlook.com>
References: <29F559819ACA9A4FBF208407D4B63ABB01401E3228@OC11expo28.exchange.mit.edu>
 <DM5PR04MB095425F535C719D0CC58C828DB470@DM5PR04MB0954.namprd04.prod.outlook.com>
 <MWHPR08MB34561B72C2480060621416F6F1470@MWHPR08MB3456.namprd08.prod.outlook.com>
Message-ID: <CAGFAsrMGjsBwKnZCZgMUA09549xUbK9CPTMYVMWb78HRJGEgBg@mail.gmail.com>

Hi everyone,

We also experienced this issue and submitted the original ticket for
AR-1559. We discovered that users who have these container-related
permissions (but not permissions to manage the repository) were able to
navigate to the manage top containers page through their browser address
bar (i.e. http://sandbox.archivesspace.org/top_containers) even if "Manage
Top Containers" does not appear in the gear icon drop-down menu. At that
point it become less of a blocker for people, albeit not ideal. Maybe that
will work for you as well.

Best,
Rachel

On Tue, Oct 24, 2017 at 2:20 PM, Christine Di Bella <
christine.dibella at lyrasis.org> wrote:

> Hi Kari and Laurel,
>
>
>
> There is a separate permission for delete/bulk update top container
> records (bulk update is the equivalent to the Manage Top Containers area) ?
> it appearing for users with this level of permissions was fixed in
> https://archivesspace.atlassian.net/browse/AR-1559. If you assign that
> permission to a user, do they get that menu item?
>
>
>
> Christine
>
>
>
> Christine Di Bella
>
> ArchivesSpace Program Manager
>
> christine.dibella at lyrasis.org
>
> 800.999.8558 x2905 <(800)%20999-8558>
>
> 678-235-2905 <(678)%20235-2905>
>
> cdibella13 (Skype)
>
>
>
> [image: ASpaceOrgHomeMedium]
>
>
>
>
>
>
>
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:
> archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *McPhee,
> Laurel
> *Sent:* Tuesday, October 24, 2017 2:14 PM
> *To:* Archivesspace Users Group <archivesspace_users_group@
> lyralists.lyrasis.org>
> *Subject:* Re: [Archivesspace_Users_Group] Having trouble with permission
> to Manage Top Containers
>
>
>
> Hi Kari,
>
>
>
> We experienced this, and through trial and error discovered (I think) that
> there is a logic mismatch at work in those permissions. The only way
> someone can see the Manage Top Container option through the cogwheel is if
> they also have a the ?Manage this Repository (change groups and other
> settings)? box checked. This has caused us some inconvenience because if we
> want someone to be able to create/update/delete top containers, it stands
> to reason we would also like them to be able to use the Manage Top
> Containers tool and all its functionality. But you have to basically make
> them a repository manager to do so, which is a whole other layer of
> permissions.
>
>
>
> An issue (if it hasn?t already been reported) for the Staff Interface
> group? I?d love to stand corrected though and learn if I am missing another
> obvious option here, or if there is other reasoning at work.
>
>
>
> Laurel
>
>
>
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [
> mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org
> <archivesspace_users_group-bounces at lyralists.lyrasis.org>] *On Behalf Of *Kari
> R Smith
> *Sent:* Tuesday, October 24, 2017 11:03 AM
> *To:* Archivesspace Users Group (archivesspace_users_group@
> lyralists.lyrasis.org) <archivesspace_users_group at lyralists.lyrasis.org>
> *Cc:* archivesspace at googlegroups.com
> *Subject:* [Archivesspace_Users_Group] Having trouble with permission to
> Manage Top Containers
>
>
>
> Hello,
>
> We have a permission group with:
>
> create/update top container records  &
>
> create/update/delete container profile records
>
>
>
> However, users with this permission group do not have Manage Top Container
> as an option in the cogwheel menu to the right of the Repo Name.
>
>
>
> Thoughts?  We are hosted by LYRASIS and recently upgraded to 2.1.7. Does
> it take a long time for the permissions to be changed? We did this on
> Friday and again yesterday afternoon but no changes for that user.
>
>
>
> Thanks for suggestions, help.
>
> Kari
>
>
>
>
>
> --------------------------------------------------------------------------
>
> Kari R. Smith
>
> Institute Archivist and Program Head, Digital Archives
>
> Institute Archives & Special Collections, MIT Libraries
>
> Massachusetts Institute of Technology, Cambridge, Massachusetts 02139
>
> IASC office: 617.258.5568 <(617)%20258-5568>  http://libraries.mit.edu/
> archives/
>
> she | her | hers   @karirene69  [smithkr at mit.edu]
>
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>


-- 
Rachel Searcy
Accessioning Archivist, Archival Collections Management
New York University Libraries
212.998.2539 | rachel.searcy at nyu.edu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171024/5eb902a9/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 6608 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171024/5eb902a9/attachment.jpg>

From lmcphee at ucsd.edu  Tue Oct 24 14:33:32 2017
From: lmcphee at ucsd.edu (McPhee, Laurel)
Date: Tue, 24 Oct 2017 18:33:32 +0000
Subject: [Archivesspace_Users_Group] Having trouble
	with	permission	to	Manage Top Containers
In-Reply-To: <MWHPR08MB34561B72C2480060621416F6F1470@MWHPR08MB3456.namprd08.prod.outlook.com>
References: <29F559819ACA9A4FBF208407D4B63ABB01401E3228@OC11expo28.exchange.mit.edu>
 <DM5PR04MB095425F535C719D0CC58C828DB470@DM5PR04MB0954.namprd04.prod.outlook.com>
 <MWHPR08MB34561B72C2480060621416F6F1470@MWHPR08MB3456.namprd08.prod.outlook.com>
Message-ID: <DM5PR04MB095450D69BBA6FD8385C1FF7DB470@DM5PR04MB0954.namprd04.prod.outlook.com>

Yes, it works now (for us). Thank you! We're still kicking the tires on our newly upgraded instance (v.2.1.2) and learning what has been fixed and updated. :)

Laurel

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Christine Di Bella
Sent: Tuesday, October 24, 2017 11:21 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Having trouble with permission to Manage Top Containers

Hi Kari and Laurel,

There is a separate permission for delete/bulk update top container records (bulk update is the equivalent to the Manage Top Containers area) - it appearing for users with this level of permissions was fixed in https://archivesspace.atlassian.net/browse/AR-1559. If you assign that permission to a user, do they get that menu item?

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)

[ASpaceOrgHomeMedium]



From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of McPhee, Laurel
Sent: Tuesday, October 24, 2017 2:14 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Having trouble with permission to Manage Top Containers

Hi Kari,

We experienced this, and through trial and error discovered (I think) that there is a logic mismatch at work in those permissions. The only way someone can see the Manage Top Container option through the cogwheel is if they also have a the "Manage this Repository (change groups and other settings)" box checked. This has caused us some inconvenience because if we want someone to be able to create/update/delete top containers, it stands to reason we would also like them to be able to use the Manage Top Containers tool and all its functionality. But you have to basically make them a repository manager to do so, which is a whole other layer of permissions.

An issue (if it hasn't already been reported) for the Staff Interface group? I'd love to stand corrected though and learn if I am missing another obvious option here, or if there is other reasoning at work.

Laurel

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Kari R Smith
Sent: Tuesday, October 24, 2017 11:03 AM
To: Archivesspace Users Group (archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>) <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Cc: archivesspace at googlegroups.com<mailto:archivesspace at googlegroups.com>
Subject: [Archivesspace_Users_Group] Having trouble with permission to Manage Top Containers

Hello,
We have a permission group with:
create/update top container records  &
create/update/delete container profile records

However, users with this permission group do not have Manage Top Container as an option in the cogwheel menu to the right of the Repo Name.

Thoughts?  We are hosted by LYRASIS and recently upgraded to 2.1.7. Does it take a long time for the permissions to be changed? We did this on Friday and again yesterday afternoon but no changes for that user.

Thanks for suggestions, help.
Kari


--------------------------------------------------------------------------
Kari R. Smith
Institute Archivist and Program Head, Digital Archives
Institute Archives & Special Collections, MIT Libraries
Massachusetts Institute of Technology, Cambridge, Massachusetts 02139
IASC office: 617.258.5568  http://libraries.mit.edu/archives/
she | her | hers   @karirene69  [smithkr at mit.edu]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171024/256ddc46/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 4009 bytes
Desc: image002.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171024/256ddc46/attachment.jpg>

From bthomas at tsl.texas.gov  Tue Oct 24 16:04:27 2017
From: bthomas at tsl.texas.gov (Brian Thomas)
Date: Tue, 24 Oct 2017 20:04:27 +0000
Subject: [Archivesspace_Users_Group] Top-Container restrictions
Message-ID: <CY4PR1601MB13491471309A5D18AAD35BE3FA470@CY4PR1601MB1349.namprd16.prod.outlook.com>

Is there a non-API way to note that a top-container is restricted? I see this looks like it should be an option since it is a listed field in the container management, but there is nothing in the top-container record data entry form or update after-the-fact to actually note that a container is restricted.

Brian Thomas
Electronic Records Specialist
Texas State Library and Archives Commission
1201 Brazos Street
Austin, TX 78701
PH: (512) 475-3374
e-mail: bthomas at tsl.texas.gov
tsl.texas.gov<http://tsl.texas.gov/>
[cid:image001.jpg at 01D029A2.37194C70]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171024/a3e21cb2/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 5314 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171024/a3e21cb2/attachment.png>

From smithkr at mit.edu  Tue Oct 24 17:02:40 2017
From: smithkr at mit.edu (Kari R Smith)
Date: Tue, 24 Oct 2017 21:02:40 +0000
Subject: [Archivesspace_Users_Group] Top-Container restrictions
In-Reply-To: <CY4PR1601MB13491471309A5D18AAD35BE3FA470@CY4PR1601MB1349.namprd16.prod.outlook.com>
References: <CY4PR1601MB13491471309A5D18AAD35BE3FA470@CY4PR1601MB1349.namprd16.prod.outlook.com>
Message-ID: <29F559819ACA9A4FBF208407D4B63ABB01401E4AD7@OC11expo28.exchange.mit.edu>

Following up on Brian's question is mine:

How can you make a Top Container restricted?  I've tried restricting content (series or file level item) in a Resource record that is associated with a Top Container (doesn't carry over t the Top Container) and I see no way to do this within a Top container record.

Thanks for all help!

--------------------------------------------------------------------------
Kari R. Smith
Institute Archivist and Program Head, Digital Archives
Institute Archives & Special Collections, MIT Libraries
Massachusetts Institute of Technology, Cambridge, Massachusetts 02139
IASC office: 617.258.5568  http://libraries.mit.edu/archives/
she | her | hers   @karirene69  [smithkr at mit.edu]

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Brian Thomas
Sent: Tuesday, October 24, 2017 4:04 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Top-Container restrictions

Is there a non-API way to note that a top-container is restricted? I see this looks like it should be an option since it is a listed field in the container management, but there is nothing in the top-container record data entry form or update after-the-fact to actually note that a container is restricted.

Brian Thomas
Electronic Records Specialist
Texas State Library and Archives Commission
1201 Brazos Street
Austin, TX 78701
PH: (512) 475-3374
e-mail: bthomas at tsl.texas.gov
tsl.texas.gov<http://tsl.texas.gov/>
[cid:image001.jpg at 01D029A2.37194C70]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171024/f0f86ab2/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 5314 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171024/f0f86ab2/attachment.png>

From smithkr at mit.edu  Tue Oct 24 17:05:14 2017
From: smithkr at mit.edu (Kari R Smith)
Date: Tue, 24 Oct 2017 21:05:14 +0000
Subject: [Archivesspace_Users_Group] Having
	trouble	with	permission	to	Manage Top Containers
In-Reply-To: <DM5PR04MB095450D69BBA6FD8385C1FF7DB470@DM5PR04MB0954.namprd04.prod.outlook.com>
References: <29F559819ACA9A4FBF208407D4B63ABB01401E3228@OC11expo28.exchange.mit.edu>
 <DM5PR04MB095425F535C719D0CC58C828DB470@DM5PR04MB0954.namprd04.prod.outlook.com>
 <MWHPR08MB34561B72C2480060621416F6F1470@MWHPR08MB3456.namprd08.prod.outlook.com>
 <DM5PR04MB095450D69BBA6FD8385C1FF7DB470@DM5PR04MB0954.namprd04.prod.outlook.com>
Message-ID: <29F559819ACA9A4FBF208407D4B63ABB01401E4B2D@OC11expo28.exchange.mit.edu>

Hi Christina -
Yes, if we assign them Bulk permissions they can use the Manage Top Containers module.  But we don't want our Reference staff having access to Bulk delete options and permissions - and yet that module is the only one where they can download a complete set of the box/barcodes, etc. data.

Hm.    Kari

--------------------------------------------------------------------------
Kari R. Smith
Institute Archivist and Program Head, Digital Archives
Institute Archives & Special Collections, MIT Libraries
Massachusetts Institute of Technology, Cambridge, Massachusetts 02139
IASC office: 617.258.5568  http://libraries.mit.edu/archives/
she | her | hers   @karirene69  [smithkr at mit.edu]

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of McPhee, Laurel
Sent: Tuesday, October 24, 2017 2:34 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Having trouble with permission to Manage Top Containers

Yes, it works now (for us). Thank you! We're still kicking the tires on our newly upgraded instance (v.2.1.2) and learning what has been fixed and updated. :)

Laurel

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Christine Di Bella
Sent: Tuesday, October 24, 2017 11:21 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Having trouble with permission to Manage Top Containers

Hi Kari and Laurel,

There is a separate permission for delete/bulk update top container records (bulk update is the equivalent to the Manage Top Containers area) - it appearing for users with this level of permissions was fixed in https://archivesspace.atlassian.net/browse/AR-1559. If you assign that permission to a user, do they get that menu item?

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)

[ASpaceOrgHomeMedium]



From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of McPhee, Laurel
Sent: Tuesday, October 24, 2017 2:14 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Having trouble with permission to Manage Top Containers

Hi Kari,

We experienced this, and through trial and error discovered (I think) that there is a logic mismatch at work in those permissions. The only way someone can see the Manage Top Container option through the cogwheel is if they also have a the "Manage this Repository (change groups and other settings)" box checked. This has caused us some inconvenience because if we want someone to be able to create/update/delete top containers, it stands to reason we would also like them to be able to use the Manage Top Containers tool and all its functionality. But you have to basically make them a repository manager to do so, which is a whole other layer of permissions.

An issue (if it hasn't already been reported) for the Staff Interface group? I'd love to stand corrected though and learn if I am missing another obvious option here, or if there is other reasoning at work.

Laurel

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Kari R Smith
Sent: Tuesday, October 24, 2017 11:03 AM
To: Archivesspace Users Group (archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>) <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Cc: archivesspace at googlegroups.com<mailto:archivesspace at googlegroups.com>
Subject: [Archivesspace_Users_Group] Having trouble with permission to Manage Top Containers

Hello,
We have a permission group with:
create/update top container records  &
create/update/delete container profile records

However, users with this permission group do not have Manage Top Container as an option in the cogwheel menu to the right of the Repo Name.

Thoughts?  We are hosted by LYRASIS and recently upgraded to 2.1.7. Does it take a long time for the permissions to be changed? We did this on Friday and again yesterday afternoon but no changes for that user.

Thanks for suggestions, help.
Kari


--------------------------------------------------------------------------
Kari R. Smith
Institute Archivist and Program Head, Digital Archives
Institute Archives & Special Collections, MIT Libraries
Massachusetts Institute of Technology, Cambridge, Massachusetts 02139
IASC office: 617.258.5568  http://libraries.mit.edu/archives/
she | her | hers   @karirene69  [smithkr at mit.edu]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171024/798f3a4b/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 4009 bytes
Desc: image001.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171024/798f3a4b/attachment-0001.jpg>

From dfwalton at ua.edu  Tue Oct 24 18:00:30 2017
From: dfwalton at ua.edu (Walton, Donnelly)
Date: Tue, 24 Oct 2017 22:00:30 +0000
Subject: [Archivesspace_Users_Group] "We're sorry,
 something went wrong" after requesting material via ArchivesSpace
In-Reply-To: <MWHPR08MB345652024E097D443F33B73AF1470@MWHPR08MB3456.namprd08.prod.outlook.com>
References: <942417AC-8949-4787-96BC-084E8FA17FDF@lib.msu.edu>
 <BN6PR11MB1442956C8B117C022A76AD7695660@BN6PR11MB1442.namprd11.prod.outlook.com>
 <BN3PR08MB130394A46BBCED1593BAC8F88C660@BN3PR08MB1303.namprd08.prod.outlook.com>
 <BN6PR11MB1442E536A7F886A236D2BC0695660@BN6PR11MB1442.namprd11.prod.outlook.com>
 <e13866dad49445808232314644651aa5@ua.edu>
 <MWHPR08MB345652024E097D443F33B73AF1470@MWHPR08MB3456.namprd08.prod.outlook.com>
Message-ID: <ae428b50252146d7b9af69f370bf7ddc@ua.edu>

Christine,

Thanks!  This was very helpful.

Donnelly

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Christine Di Bella
Sent: Tuesday, October 24, 2017 1:28 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] "We're sorry, something went wrong" after requesting material via ArchivesSpace

Hi Donnelly,

These settings are controlled by options in the config.rb file on your ArchivesSpace server. A bug and some improvements with the email requesting feature on the PUI were resolved in version 2.2.0, so if you upgrade to that version, if should work correctly. An improvement that was made for 2.2.0 was that if you have a contact email address in a repository record, it can be used as the email address for requests (https://github.com/archivesspace/archivesspace/pull/979) rather than having to specify an email address separately. You will still need to enable the requesting feature and associated settings in the config file, however.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)

[ASpaceOrgHomeMedium]



From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Walton, Donnelly
Sent: Monday, October 23, 2017 4:04 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] "We're sorry, something went wrong" after requesting material via ArchivesSpace

We have recently upgraded to 2.1.2 and are doing a soft launch of the PUI.  Where do we go to setup the feature and tell the system where to send the emails?

Many thanks,
Donnelly

Donnelly Lancaster Walton
Archival Access Coordinator, Special Collections
University Libraries
The University of Alabama<https://www.ua.edu/>
W. S. Hoole Library, Mary Harmon Bryant Hall
Box 870266
Tuscaloosa, AL 35487
Office 205-348-0505<tel:205-348-0505>
dfwalton at ua.edu<mailto:dfwalton at ua.edu> | https://www.lib.ua.edu/libraries/hoole/
[The University of Alabama]<https://www.ua.edu/>



From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Kevin Clair
Sent: Thursday, September 21, 2017 4:39 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] "We're sorry, something went wrong" after requesting material via ArchivesSpace

We?ve been able to receive the e-mail confirmations ArchivesSpace sends, both with my personal e-mail and with LibAnswers. It?s only when it tries to render request_received_email.html that it throws the error.  -k

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Custer, Mark
Sent: Thursday, September 21, 2017 3:31 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] "We're sorry, something went wrong" after requesting material via ArchivesSpace


All,



I wish that I could offer technical advice on how to get things set up, but unfortunately I'm of no use in this case.  I do know that this feature used to be configured on our Test Corpus site, though, and that it functioned as expected at that time.



Here's what a message would look like that's sent to a patron (as you can see, it doesn?t include ALL of the data, like what the staff would receive), and they shouldn?t see an error message when requesting after everything has been configured to allow email requesting:



Thank you for your request
Record Requested
Title: Watercolor of Brassie fly nymph (fishing fly)
URL: http://aspace.hudmol.com:7310/repositories/14/digital_objects/4375<https://urldefense.proofpoint.com/v2/url?u=http-3A__aspace.hudmol.com-3A7310_repositories_14_digital-5Fobjects_4375&d=DwMCaQ&c=-dg2m7zWuuDZ0MUcV7Sdqw&r=PjInOOP-yhZdvfCxvJExNB_3mSrTAYOjE-Ld3wjgoMo&m=hES0nr_7CQRdsaxxcbpbcujfoSJVVVtSbikTnQDfBMQ&s=fEcKFYM5n4pdR51TDuNa_20WsC4Rr2r-cKOf4FBNyuk&e=>
Your Details
Name: m
Email: mark.custer at yale.edu<mailto:mark.custer at yale.edu>
Date:
Notes for Staff:



I don?t believe that the email that was sent to staff ever had a specialized template, like this one, however.  It was just meant to be a proof of concept showing how all of the request data could be sent in an email message in order to fulfill the user story about allowing researchers to make requests directly from the PUI.



Hopefully others will be able to weigh in soon with more detailed instructions how to get this configured properly.  I seem to remember that with the Gmail account that we used for testing, Gmail had to be told to allow the use of unsecured apps (though I?m not sure why exactly that was or might be).



Just so that I?m clear, though? Lydia, Kevin: it sounds like you have it configured to receive emails okay, but the emails to whomever requested the material is not being sent/received.  Is that correct?



Mark







-----Original Message-----
From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Kevin Clair
Sent: Thursday, 21 September, 2017 5:15 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] "We're sorry, something went wrong" after requesting material via ArchivesSpace



We see similar behavior, and have turned off requesting on the public site because of it. The e-mail requests go through but the users see the error page instead of a confirmation. From the logs:







INFO: I, [2017-09-21T15:08:03.838360 #4548]  INFO -- : [5c583ccc-1669-40c4-9f90-81f09fac562b] Started POST "/fill_request" for 192.168.123.1 at 2017-09-21 15:08:03 -0600







[the e-mail successfully sends here; log output omitted]







Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log



INFO: I, [2017-09-21T15:08:09.740133 #4548]  INFO -- : [5c583ccc-1669-40c4-9f90-81f09fac562b] Completed 500 Internal Server Error in 5862ms







Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log



INFO: F, [2017-09-21T15:08:09.791554 #4548] FATAL -- : [5c583ccc-1669-40c4-9f90-81f09fac562b]







Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log



INFO: F, [2017-09-21T15:08:09.797765 #4548] FATAL -- : [5c583ccc-1669-40c4-9f90-81f09fac562b] ActionView::Template::Error (undefined method `app_prefix' for #<#<Class:0x46d13c0a>:0x59036603>):







Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log



INFO: F, [2017-09-21T15:08:09.809421 #4548] FATAL -- : [5c583ccc-1669-40c4-9f90-81f09fac562b]     4:   <h2>Record Requested</h2>



[5c583ccc-1669-40c4-9f90-81f09fac562b]     5:   <strong>Title</strong>: <%= @request.title %><br>



[5c583ccc-1669-40c4-9f90-81f09fac562b]     6:   <% url = "#{AppConfig[:public_proxy_url].sub(/\/^/, '')}#{@request.request_uri}<mailto:%7d#{@request.request_uri}>" %>



[5c583ccc-1669-40c4-9f90-81f09fac562b]     7:   <strong>URL</strong>: <%= link_to url, app_prefix(url) %>



[5c583ccc-1669-40c4-9f90-81f09fac562b]     8: </div>



[5c583ccc-1669-40c4-9f90-81f09fac562b]     9:



[5c583ccc-1669-40c4-9f90-81f09fac562b]    10: <div class="user">







Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log



INFO: F, [2017-09-21T15:08:09.810141 #4548] FATAL -- : [5c583ccc-1669-40c4-9f90-81f09fac562b]







Sep 21, 2017 3:08:09 PM org.eclipse.jetty.server.handler.ContextHandler$Context log



INFO: F, [2017-09-21T15:08:09.810661 #4548] FATAL -- : [5c583ccc-1669-40c4-9f90-81f09fac562b] app/views/request_mailer/request_received_email.html.erb:7:in `_app_views_request_mailer_request_received_email_html_erb___227123848_2378'



[5c583ccc-1669-40c4-9f90-81f09fac562b] app/mailers/request_mailer.rb:7:in `request_received_email'



[5c583ccc-1669-40c4-9f90-81f09fac562b] app/controllers/requests_controller.rb:11:in `make_request'







-k







-----Original Message-----



From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Tang, Lydia



Sent: Thursday, September 21, 2017 1:19 PM



To: 'archivesspace_users_group at lyralists.lyrasis.org'



Subject: [Archivesspace_Users_Group] "We're sorry, something went wrong" after requesting material via ArchivesSpace







Hello, we recently upgraded from 2.1.1 from 1.5.3.  With our users taking advantage of the request feature through our PUI, they have received this ?We?re sorry something went wrong? message after submitting their request.  Is this normal?  Is there a tweak we need to fill in order to gracefully conclude the request and return to the PUI?



Thanks!



Lydia



_______________________________________________

Archivesspace_Users_Group mailing list

Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>

https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwIGaQ&c=cjytLXgP8ixuoHflwc-poQ&r=7Ez68qVcrmRD6nn1FqwoHBDEOxeRUCPm3xGvnFT0zjU&m=yCOvlNmPPowIK_FHWplCUKa3UJhEsCZ5AWPTGq2qjMk&s=blzfAbR70wCLQrOIDae9pDrRNAZ_79j4aYMufxVfe2w&e=
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171024/97db545c/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 4014 bytes
Desc: image001.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171024/97db545c/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.gif
Type: image/gif
Size: 6052 bytes
Desc: image002.gif
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171024/97db545c/attachment.gif>

From mcallahan at smith.edu  Tue Oct 24 19:22:58 2017
From: mcallahan at smith.edu (Maureen Callahan)
Date: Tue, 24 Oct 2017 19:22:58 -0400
Subject: [Archivesspace_Users_Group] Top-Container restrictions
In-Reply-To: <29F559819ACA9A4FBF208407D4B63ABB01401E4AD7@OC11expo28.exchange.mit.edu>
References: <CY4PR1601MB13491471309A5D18AAD35BE3FA470@CY4PR1601MB1349.namprd16.prod.outlook.com>
 <29F559819ACA9A4FBF208407D4B63ABB01401E4AD7@OC11expo28.exchange.mit.edu>
Message-ID: <CAH0VKbC+b65bLZnAi8K-eQyqGg5v4xUkJTZOsF74DWf15NxpFw@mail.gmail.com>

I'm glad you all asked about this! In short, containers aren't restricted,
materials are. These material restrictions are then associated with
containers.

I made a video about how it works here (a couple of years ago, but the
functionality hasn't changed), which I hope you all enjoy.
https://youtu.be/biCDhkbBSng

Maureen

On Tue, Oct 24, 2017 at 5:02 PM, Kari R Smith <smithkr at mit.edu> wrote:

> Following up on Brian?s question is mine:
>
>
>
> How can you make a Top Container restricted?  I?ve tried restricting
> content (series or file level item) in a Resource record that is associated
> with a Top Container (doesn?t carry over t the Top Container) and I see no
> way to do this within a Top container record.
>
>
>
> Thanks for all help!
>
>
>
> --------------------------------------------------------------------------
>
> Kari R. Smith
>
> Institute Archivist and Program Head, Digital Archives
>
> Institute Archives & Special Collections, MIT Libraries
>
> Massachusetts Institute of Technology, Cambridge, Massachusetts 02139
>
> IASC office: 617.258.5568 <(617)%20258-5568>  http://libraries.mit.edu/
> archives/
>
> she | her | hers   @karirene69  [smithkr at mit.edu]
>
>
>
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:
> archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Brian
> Thomas
> *Sent:* Tuesday, October 24, 2017 4:04 PM
> *To:* Archivesspace Users Group <archivesspace_users_group@
> lyralists.lyrasis.org>
> *Subject:* [Archivesspace_Users_Group] Top-Container restrictions
>
>
>
> Is there a non-API way to note that a top-container is restricted? I see
> this looks like it should be an option since it is a listed field in the
> container management, but there is nothing in the top-container record data
> entry form or update after-the-fact to actually note that a container is
> restricted.
>
>
>
> Brian Thomas
>
> Electronic Records Specialist
>
> Texas State Library and Archives Commission
>
> 1201 Brazos Street
>
> Austin, TX 78701
>
> PH: (512) 475-3374
>
> e-mail: bthomas at tsl.texas.gov
>
> tsl.texas.gov
>
> [image: cid:image001.jpg at 01D029A2.37194C70]
>
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>


-- 
Maureen Callahan
Sophia Smith Collection Archivist
Smith College Special Collections
Northampton, Massachusetts 01063
T. 413 585 2981 C. 215.863.1860
mcallahan at smith.edu

Pronouns: she/her/hers

Facebook: https://www.facebook.com/SophiaSmithCollection/
Instagram: https://www.instagram.com/smithlibraries/
Twitter: https://twitter.com/archivalagents

*Please note*. Smith College Special Collections is now housed at Young
Library
<https://www.smith.edu/libraries/about/new-neilson/wheres-my-library>.
Learn more about renovations to Neilson Library here
<https://www.smith.edu/libraries/about/new-neilson>.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171024/549be929/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 5314 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171024/549be929/attachment.png>

From christine.dibella at lyrasis.org  Wed Oct 25 08:36:30 2017
From: christine.dibella at lyrasis.org (Christine Di Bella)
Date: Wed, 25 Oct 2017 12:36:30 +0000
Subject: [Archivesspace_Users_Group]
	Having	trouble	with	permission	to	Manage Top Containers
In-Reply-To: <29F559819ACA9A4FBF208407D4B63ABB01401E4B2D@OC11expo28.exchange.mit.edu>
References: <29F559819ACA9A4FBF208407D4B63ABB01401E3228@OC11expo28.exchange.mit.edu>
 <DM5PR04MB095425F535C719D0CC58C828DB470@DM5PR04MB0954.namprd04.prod.outlook.com>
 <MWHPR08MB34561B72C2480060621416F6F1470@MWHPR08MB3456.namprd08.prod.outlook.com>
 <DM5PR04MB095450D69BBA6FD8385C1FF7DB470@DM5PR04MB0954.namprd04.prod.outlook.com>
 <29F559819ACA9A4FBF208407D4B63ABB01401E4B2D@OC11expo28.exchange.mit.edu>
Message-ID: <MWHPR08MB345629EC887369133E835B7DF1440@MWHPR08MB3456.namprd08.prod.outlook.com>

Hi Kari,

Megan Mummey of University of Kentucky recently filed a feature request for what it sounds like is your issue: https://archivesspace.atlassian.net/browse/AR-1923. Feel free to add to the comments if this is something you think would also be helpful to you.

In general, it sounds like people may be interested in views that make it easier to see the locations for top containers, for individual containers as well as a group of containers, and there may be some differences in what is needed depending on whether or not people use the public interface. (For people who don't use the public interface, it may be that Manage Top Containers is best for that now, but it could be that something else is preferable that is only focused on location information, rather than the other functions Manage Top Containers is intended to provide.)

The Staff Interface Enhancement group has been working on a variety of recommendations, which they are in the process of finalizing and expect to have ready to distribute for feedback very soon. Be looking for messages on that early in November, and feel free to provide ideas to the group at any point before or after that. The group's wiki pages start at https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/103454069/Staff+Interface+Enhancement+Working+Group and Lydia Tang (ltang at msu.edu<mailto:ltang at msu.edu> ) is the leader.

Christine

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Kari R Smith
Sent: Tuesday, October 24, 2017 5:05 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Having trouble with permission to Manage Top Containers

Hi Christina -
Yes, if we assign them Bulk permissions they can use the Manage Top Containers module.  But we don't want our Reference staff having access to Bulk delete options and permissions - and yet that module is the only one where they can download a complete set of the box/barcodes, etc. data.

Hm.    Kari

--------------------------------------------------------------------------
Kari R. Smith
Institute Archivist and Program Head, Digital Archives
Institute Archives & Special Collections, MIT Libraries
Massachusetts Institute of Technology, Cambridge, Massachusetts 02139
IASC office: 617.258.5568  http://libraries.mit.edu/archives/
she | her | hers   @karirene69  [smithkr at mit.edu]

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of McPhee, Laurel
Sent: Tuesday, October 24, 2017 2:34 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Having trouble with permission to Manage Top Containers

Yes, it works now (for us). Thank you! We're still kicking the tires on our newly upgraded instance (v.2.1.2) and learning what has been fixed and updated. :)

Laurel

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Christine Di Bella
Sent: Tuesday, October 24, 2017 11:21 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Having trouble with permission to Manage Top Containers

Hi Kari and Laurel,

There is a separate permission for delete/bulk update top container records (bulk update is the equivalent to the Manage Top Containers area) - it appearing for users with this level of permissions was fixed in https://archivesspace.atlassian.net/browse/AR-1559. If you assign that permission to a user, do they get that menu item?

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)

[ASpaceOrgHomeMedium]



From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of McPhee, Laurel
Sent: Tuesday, October 24, 2017 2:14 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Having trouble with permission to Manage Top Containers

Hi Kari,

We experienced this, and through trial and error discovered (I think) that there is a logic mismatch at work in those permissions. The only way someone can see the Manage Top Container option through the cogwheel is if they also have a the "Manage this Repository (change groups and other settings)" box checked. This has caused us some inconvenience because if we want someone to be able to create/update/delete top containers, it stands to reason we would also like them to be able to use the Manage Top Containers tool and all its functionality. But you have to basically make them a repository manager to do so, which is a whole other layer of permissions.

An issue (if it hasn't already been reported) for the Staff Interface group? I'd love to stand corrected though and learn if I am missing another obvious option here, or if there is other reasoning at work.

Laurel

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Kari R Smith
Sent: Tuesday, October 24, 2017 11:03 AM
To: Archivesspace Users Group (archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>) <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Cc: archivesspace at googlegroups.com<mailto:archivesspace at googlegroups.com>
Subject: [Archivesspace_Users_Group] Having trouble with permission to Manage Top Containers

Hello,
We have a permission group with:
create/update top container records  &
create/update/delete container profile records

However, users with this permission group do not have Manage Top Container as an option in the cogwheel menu to the right of the Repo Name.

Thoughts?  We are hosted by LYRASIS and recently upgraded to 2.1.7. Does it take a long time for the permissions to be changed? We did this on Friday and again yesterday afternoon but no changes for that user.

Thanks for suggestions, help.
Kari


--------------------------------------------------------------------------
Kari R. Smith
Institute Archivist and Program Head, Digital Archives
Institute Archives & Special Collections, MIT Libraries
Massachusetts Institute of Technology, Cambridge, Massachusetts 02139
IASC office: 617.258.5568  http://libraries.mit.edu/archives/
she | her | hers   @karirene69  [smithkr at mit.edu]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171025/ea3a78c2/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 4009 bytes
Desc: image001.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171025/ea3a78c2/attachment.jpg>

From bthomas at tsl.texas.gov  Wed Oct 25 09:28:01 2017
From: bthomas at tsl.texas.gov (Brian Thomas)
Date: Wed, 25 Oct 2017 13:28:01 +0000
Subject: [Archivesspace_Users_Group] Top-Container restrictions
In-Reply-To: <CAH0VKbC+b65bLZnAi8K-eQyqGg5v4xUkJTZOsF74DWf15NxpFw@mail.gmail.com>
References: <CY4PR1601MB13491471309A5D18AAD35BE3FA470@CY4PR1601MB1349.namprd16.prod.outlook.com>
 <29F559819ACA9A4FBF208407D4B63ABB01401E4AD7@OC11expo28.exchange.mit.edu>
 <CAH0VKbC+b65bLZnAi8K-eQyqGg5v4xUkJTZOsF74DWf15NxpFw@mail.gmail.com>
Message-ID: <CY4PR1601MB13490085B36B7C3C0508E314FA440@CY4PR1601MB1349.namprd16.prod.outlook.com>

I watched the video, tried some stuff out and I saw that worked on the resources level (thank you for pointing to that resource). If I update the Rights statement in accessions with restrictions information it doesn?t look like that is carrying over into the top-containers being listed as attached to the accession. Is that not a current functionality?

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Maureen Callahan
Sent: Tuesday, October 24, 2017 6:23 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Top-Container restrictions

I'm glad you all asked about this! In short, containers aren't restricted, materials are. These material restrictions are then associated with containers.

I made a video about how it works here (a couple of years ago, but the functionality hasn't changed), which I hope you all enjoy. https://youtu.be/biCDhkbBSng

Maureen

On Tue, Oct 24, 2017 at 5:02 PM, Kari R Smith <smithkr at mit.edu<mailto:smithkr at mit.edu>> wrote:
Following up on Brian?s question is mine:

How can you make a Top Container restricted?  I?ve tried restricting content (series or file level item) in a Resource record that is associated with a Top Container (doesn?t carry over t the Top Container) and I see no way to do this within a Top container record.

Thanks for all help!

--------------------------------------------------------------------------
Kari R. Smith
Institute Archivist and Program Head, Digital Archives
Institute Archives & Special Collections, MIT Libraries
Massachusetts Institute of Technology, Cambridge, Massachusetts 02139
IASC office: 617.258.5568<tel:(617)%20258-5568>  http://libraries.mit.edu/archives/
she | her | hers   @karirene69  [smithkr at mit.edu<http://mit.edu>]

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>] On Behalf Of Brian Thomas
Sent: Tuesday, October 24, 2017 4:04 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] Top-Container restrictions

Is there a non-API way to note that a top-container is restricted? I see this looks like it should be an option since it is a listed field in the container management, but there is nothing in the top-container record data entry form or update after-the-fact to actually note that a container is restricted.

Brian Thomas
Electronic Records Specialist
Texas State Library and Archives Commission
1201 Brazos Street
Austin, TX 78701
PH: (512) 475-3374<tel:(512)%20475-3374>
e-mail: bthomas at tsl.texas.gov<http://bthomas at tsl.texas.gov>
tsl.texas.gov<http://tsl.texas.gov/>
[cid:image001.jpg at 01D029A2.37194C70]


_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group



--
Maureen Callahan
Sophia Smith Collection Archivist
Smith College Special Collections
Northampton, Massachusetts 01063
T. 413 585 2981 C. 215.863.1860
mcallahan at smith.edu<mailto:mcallahan at smith.edu>

Pronouns: she/her/hers

Facebook: https://www.facebook.com/SophiaSmithCollection/
Instagram: https://www.instagram.com/smithlibraries/
Twitter: https://twitter.com/archivalagents

Please note. Smith College Special Collections is now housed at Young Library<https://www.smith.edu/libraries/about/new-neilson/wheres-my-library>. Learn more about renovations to Neilson Library here<https://www.smith.edu/libraries/about/new-neilson>.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171025/7922f202/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 5314 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171025/7922f202/attachment.png>

From mcallahan at smith.edu  Wed Oct 25 09:33:46 2017
From: mcallahan at smith.edu (Maureen Callahan)
Date: Wed, 25 Oct 2017 09:33:46 -0400
Subject: [Archivesspace_Users_Group] Top-Container restrictions
In-Reply-To: <CY4PR1601MB13490085B36B7C3C0508E314FA440@CY4PR1601MB1349.namprd16.prod.outlook.com>
References: <CY4PR1601MB13491471309A5D18AAD35BE3FA470@CY4PR1601MB1349.namprd16.prod.outlook.com>
 <29F559819ACA9A4FBF208407D4B63ABB01401E4AD7@OC11expo28.exchange.mit.edu>
 <CAH0VKbC+b65bLZnAi8K-eQyqGg5v4xUkJTZOsF74DWf15NxpFw@mail.gmail.com>
 <CY4PR1601MB13490085B36B7C3C0508E314FA440@CY4PR1601MB1349.namprd16.prod.outlook.com>
Message-ID: <CAH0VKbAuU2-Smqy-NYkwjnxWucacjNvnio1TA6ZQViE6O_2SLg@mail.gmail.com>

The restrictions aren't governed by rights subrecords, they're governed by
conditions governing access and conditions governing use (this is because
the rights subrecord is based on the PREMIS model and is for digital
preservation use, not for archival description, which is governed by DACS).
Try applying the same restrictions as conditions governing access or
conditions governing use restrictions and give it a shot.

MC

On Wed, Oct 25, 2017 at 9:28 AM, Brian Thomas <bthomas at tsl.texas.gov> wrote:

> I watched the video, tried some stuff out and I saw that worked on the
> resources level (thank you for pointing to that resource). If I update the
> Rights statement in accessions with restrictions information it doesn?t
> look like that is carrying over into the top-containers being listed as
> attached to the accession. Is that not a current functionality?
>
>
>
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:
> archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Maureen
> Callahan
> *Sent:* Tuesday, October 24, 2017 6:23 PM
> *To:* Archivesspace Users Group
> *Subject:* Re: [Archivesspace_Users_Group] Top-Container restrictions
>
>
>
> I'm glad you all asked about this! In short, containers aren't restricted,
> materials are. These material restrictions are then associated with
> containers.
>
>
>
> I made a video about how it works here (a couple of years ago, but the
> functionality hasn't changed), which I hope you all enjoy.
> https://youtu.be/biCDhkbBSng
>
>
>
> Maureen
>
>
>
> On Tue, Oct 24, 2017 at 5:02 PM, Kari R Smith <smithkr at mit.edu> wrote:
>
> Following up on Brian?s question is mine:
>
>
>
> How can you make a Top Container restricted?  I?ve tried restricting
> content (series or file level item) in a Resource record that is associated
> with a Top Container (doesn?t carry over t the Top Container) and I see no
> way to do this within a Top container record.
>
>
>
> Thanks for all help!
>
>
>
> --------------------------------------------------------------------------
>
> Kari R. Smith
>
> Institute Archivist and Program Head, Digital Archives
>
> Institute Archives & Special Collections, MIT Libraries
>
> Massachusetts Institute of Technology, Cambridge, Massachusetts 02139
>
> IASC office: 617.258.5568 <(617)%20258-5568>  http://libraries.mit.edu/
> archives/
>
> she | her | hers   @karirene69  [smithkr at mit.edu]
>
>
>
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:
> archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Brian
> Thomas
> *Sent:* Tuesday, October 24, 2017 4:04 PM
> *To:* Archivesspace Users Group <archivesspace_users_group@
> lyralists.lyrasis.org>
> *Subject:* [Archivesspace_Users_Group] Top-Container restrictions
>
>
>
> Is there a non-API way to note that a top-container is restricted? I see
> this looks like it should be an option since it is a listed field in the
> container management, but there is nothing in the top-container record data
> entry form or update after-the-fact to actually note that a container is
> restricted.
>
>
>
> Brian Thomas
>
> Electronic Records Specialist
>
> Texas State Library and Archives Commission
>
> 1201 Brazos Street
>
> Austin, TX 78701
>
> PH: (512) 475-3374
>
> e-mail: bthomas at tsl.texas.gov
>
> tsl.texas.gov
>
> [image: cid:image001.jpg at 01D029A2.37194C70]
>
>
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>
>
>
>
> --
>
> Maureen Callahan
> Sophia Smith Collection Archivist
> Smith College Special Collections
> Northampton, Massachusetts 01063
> T. 413 585 2981 <(413)%20585-2981> C. 215.863.1860 <(215)%20863-1860>
> mcallahan at smith.edu
>
>
>
> Pronouns: she/her/hers
>
> Facebook: https://www.facebook.com/SophiaSmithCollection/
> Instagram: https://www.instagram.com/smithlibraries/
> Twitter: https://twitter.com/archivalagents
>
>
> *Please note*. Smith College Special Collections is now housed at Young
> Library
> <https://www.smith.edu/libraries/about/new-neilson/wheres-my-library>.
> Learn more about renovations to Neilson Library here
> <https://www.smith.edu/libraries/about/new-neilson>.
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>


-- 
Maureen Callahan
Sophia Smith Collection Archivist
Smith College Special Collections
Northampton, Massachusetts 01063
T. 413 585 2981 C. 215.863.1860
mcallahan at smith.edu

Pronouns: she/her/hers

Facebook: https://www.facebook.com/SophiaSmithCollection/
Instagram: https://www.instagram.com/smithlibraries/
Twitter: https://twitter.com/archivalagents

*Please note*. Smith College Special Collections is now housed at Young
Library
<https://www.smith.edu/libraries/about/new-neilson/wheres-my-library>.
Learn more about renovations to Neilson Library here
<https://www.smith.edu/libraries/about/new-neilson>.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171025/cde7e4b8/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 5314 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171025/cde7e4b8/attachment.png>

From bthomas at tsl.texas.gov  Wed Oct 25 09:39:03 2017
From: bthomas at tsl.texas.gov (Brian Thomas)
Date: Wed, 25 Oct 2017 13:39:03 +0000
Subject: [Archivesspace_Users_Group] Top-Container restrictions
In-Reply-To: <CAH0VKbAuU2-Smqy-NYkwjnxWucacjNvnio1TA6ZQViE6O_2SLg@mail.gmail.com>
References: <CY4PR1601MB13491471309A5D18AAD35BE3FA470@CY4PR1601MB1349.namprd16.prod.outlook.com>
 <29F559819ACA9A4FBF208407D4B63ABB01401E4AD7@OC11expo28.exchange.mit.edu>
 <CAH0VKbC+b65bLZnAi8K-eQyqGg5v4xUkJTZOsF74DWf15NxpFw@mail.gmail.com>
 <CY4PR1601MB13490085B36B7C3C0508E314FA440@CY4PR1601MB1349.namprd16.prod.outlook.com>
 <CAH0VKbAuU2-Smqy-NYkwjnxWucacjNvnio1TA6ZQViE6O_2SLg@mail.gmail.com>
Message-ID: <CY4PR1601MB1349DC0BCA9B08C288EBA7E2FA440@CY4PR1601MB1349.namprd16.prod.outlook.com>

Adding a conditions governing access or use note is not an option in Accessions. And checking the boxes in basic information does not carry over into top-containers.

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Maureen Callahan
Sent: Wednesday, October 25, 2017 8:34 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Top-Container restrictions

The restrictions aren't governed by rights subrecords, they're governed by conditions governing access and conditions governing use (this is because the rights subrecord is based on the PREMIS model and is for digital preservation use, not for archival description, which is governed by DACS). Try applying the same restrictions as conditions governing access or conditions governing use restrictions and give it a shot.

MC

On Wed, Oct 25, 2017 at 9:28 AM, Brian Thomas <bthomas at tsl.texas.gov<mailto:bthomas at tsl.texas.gov>> wrote:
I watched the video, tried some stuff out and I saw that worked on the resources level (thank you for pointing to that resource). If I update the Rights statement in accessions with restrictions information it doesn?t look like that is carrying over into the top-containers being listed as attached to the accession. Is that not a current functionality?

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>] On Behalf Of Maureen Callahan
Sent: Tuesday, October 24, 2017 6:23 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Top-Container restrictions

I'm glad you all asked about this! In short, containers aren't restricted, materials are. These material restrictions are then associated with containers.

I made a video about how it works here (a couple of years ago, but the functionality hasn't changed), which I hope you all enjoy. https://youtu.be/biCDhkbBSng

Maureen

On Tue, Oct 24, 2017 at 5:02 PM, Kari R Smith <smithkr at mit.edu<mailto:smithkr at mit.edu>> wrote:
Following up on Brian?s question is mine:

How can you make a Top Container restricted?  I?ve tried restricting content (series or file level item) in a Resource record that is associated with a Top Container (doesn?t carry over t the Top Container) and I see no way to do this within a Top container record.

Thanks for all help!

--------------------------------------------------------------------------
Kari R. Smith
Institute Archivist and Program Head, Digital Archives
Institute Archives & Special Collections, MIT Libraries
Massachusetts Institute of Technology, Cambridge, Massachusetts 02139
IASC office: 617.258.5568<tel:(617)%20258-5568>  http://libraries.mit.edu/archives/
she | her | hers   @karirene69  [smithkr at mit.edu<http://mit.edu>]

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>] On Behalf Of Brian Thomas
Sent: Tuesday, October 24, 2017 4:04 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] Top-Container restrictions

Is there a non-API way to note that a top-container is restricted? I see this looks like it should be an option since it is a listed field in the container management, but there is nothing in the top-container record data entry form or update after-the-fact to actually note that a container is restricted.

Brian Thomas
Electronic Records Specialist
Texas State Library and Archives Commission
1201 Brazos Street
Austin, TX 78701
PH: (512) 475-3374<tel:(512)%20475-3374>
e-mail: bthomas at tsl.texas.gov<http://bthomas at tsl.texas.gov>
tsl.texas.gov<http://tsl.texas.gov/>
[cid:image001.jpg at 01D029A2.37194C70]


_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group



--
Maureen Callahan
Sophia Smith Collection Archivist
Smith College Special Collections
Northampton, Massachusetts 01063
T. 413 585 2981<tel:(413)%20585-2981> C. 215.863.1860<tel:(215)%20863-1860>
mcallahan at smith.edu<mailto:mcallahan at smith.edu>

Pronouns: she/her/hers

Facebook: https://www.facebook.com/SophiaSmithCollection/
Instagram: https://www.instagram.com/smithlibraries/
Twitter: https://twitter.com/archivalagents

Please note. Smith College Special Collections is now housed at Young Library<https://www.smith.edu/libraries/about/new-neilson/wheres-my-library>. Learn more about renovations to Neilson Library here<https://www.smith.edu/libraries/about/new-neilson>.

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group



--
Maureen Callahan
Sophia Smith Collection Archivist
Smith College Special Collections
Northampton, Massachusetts 01063
T. 413 585 2981 C. 215.863.1860
mcallahan at smith.edu<mailto:mcallahan at smith.edu>

Pronouns: she/her/hers

Facebook: https://www.facebook.com/SophiaSmithCollection/
Instagram: https://www.instagram.com/smithlibraries/
Twitter: https://twitter.com/archivalagents

Please note. Smith College Special Collections is now housed at Young Library<https://www.smith.edu/libraries/about/new-neilson/wheres-my-library>. Learn more about renovations to Neilson Library here<https://www.smith.edu/libraries/about/new-neilson>.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171025/d61de0f8/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 5314 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171025/d61de0f8/attachment.png>

From mcallahan at smith.edu  Wed Oct 25 09:47:34 2017
From: mcallahan at smith.edu (Maureen Callahan)
Date: Wed, 25 Oct 2017 09:47:34 -0400
Subject: [Archivesspace_Users_Group] Top-Container restrictions
In-Reply-To: <CY4PR1601MB1349DC0BCA9B08C288EBA7E2FA440@CY4PR1601MB1349.namprd16.prod.outlook.com>
References: <CY4PR1601MB13491471309A5D18AAD35BE3FA470@CY4PR1601MB1349.namprd16.prod.outlook.com>
 <29F559819ACA9A4FBF208407D4B63ABB01401E4AD7@OC11expo28.exchange.mit.edu>
 <CAH0VKbC+b65bLZnAi8K-eQyqGg5v4xUkJTZOsF74DWf15NxpFw@mail.gmail.com>
 <CY4PR1601MB13490085B36B7C3C0508E314FA440@CY4PR1601MB1349.namprd16.prod.outlook.com>
 <CAH0VKbAuU2-Smqy-NYkwjnxWucacjNvnio1TA6ZQViE6O_2SLg@mail.gmail.com>
 <CY4PR1601MB1349DC0BCA9B08C288EBA7E2FA440@CY4PR1601MB1349.namprd16.prod.outlook.com>
Message-ID: <CAH0VKbBX3iuEu__kx-KRZmZWDkU0uYxXfoVyzG7rsp7u=s=GCQ@mail.gmail.com>

I'm sorry, it skipped my notice that you were talking about accessions in
your second message. It's a good point and kind of weird that resources
have structured notes but accessions have a whole other field type (this is
a weird thing generally). You're right that the way to associate
restrictions with top containers is through those notes, and it's not
currently possible to do that with accession records.

MC

On Wed, Oct 25, 2017 at 9:39 AM, Brian Thomas <bthomas at tsl.texas.gov> wrote:

> Adding a conditions governing access or use note is not an option in
> Accessions. And checking the boxes in basic information does not carry over
> into top-containers.
>
>
>
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:
> archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Maureen
> Callahan
> *Sent:* Wednesday, October 25, 2017 8:34 AM
>
> *To:* Archivesspace Users Group
> *Subject:* Re: [Archivesspace_Users_Group] Top-Container restrictions
>
>
>
> The restrictions aren't governed by rights subrecords, they're governed by
> conditions governing access and conditions governing use (this is because
> the rights subrecord is based on the PREMIS model and is for digital
> preservation use, not for archival description, which is governed by DACS).
> Try applying the same restrictions as conditions governing access or
> conditions governing use restrictions and give it a shot.
>
>
>
> MC
>
>
>
> On Wed, Oct 25, 2017 at 9:28 AM, Brian Thomas <bthomas at tsl.texas.gov>
> wrote:
>
> I watched the video, tried some stuff out and I saw that worked on the
> resources level (thank you for pointing to that resource). If I update the
> Rights statement in accessions with restrictions information it doesn?t
> look like that is carrying over into the top-containers being listed as
> attached to the accession. Is that not a current functionality?
>
>
>
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:
> archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Maureen
> Callahan
> *Sent:* Tuesday, October 24, 2017 6:23 PM
> *To:* Archivesspace Users Group
> *Subject:* Re: [Archivesspace_Users_Group] Top-Container restrictions
>
>
>
> I'm glad you all asked about this! In short, containers aren't restricted,
> materials are. These material restrictions are then associated with
> containers.
>
>
>
> I made a video about how it works here (a couple of years ago, but the
> functionality hasn't changed), which I hope you all enjoy.
> https://youtu.be/biCDhkbBSng
>
>
>
> Maureen
>
>
>
> On Tue, Oct 24, 2017 at 5:02 PM, Kari R Smith <smithkr at mit.edu> wrote:
>
> Following up on Brian?s question is mine:
>
>
>
> How can you make a Top Container restricted?  I?ve tried restricting
> content (series or file level item) in a Resource record that is associated
> with a Top Container (doesn?t carry over t the Top Container) and I see no
> way to do this within a Top container record.
>
>
>
> Thanks for all help!
>
>
>
> --------------------------------------------------------------------------
>
> Kari R. Smith
>
> Institute Archivist and Program Head, Digital Archives
>
> Institute Archives & Special Collections, MIT Libraries
>
> Massachusetts Institute of Technology, Cambridge, Massachusetts 02139
>
> IASC office: 617.258.5568 <(617)%20258-5568>  http://libraries.mit.edu/
> archives/
>
> she | her | hers   @karirene69  [smithkr at mit.edu]
>
>
>
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:
> archivesspace_users_group-bounces at lyralists.lyrasis.org] *On Behalf Of *Brian
> Thomas
> *Sent:* Tuesday, October 24, 2017 4:04 PM
> *To:* Archivesspace Users Group <archivesspace_users_group@
> lyralists.lyrasis.org>
> *Subject:* [Archivesspace_Users_Group] Top-Container restrictions
>
>
>
> Is there a non-API way to note that a top-container is restricted? I see
> this looks like it should be an option since it is a listed field in the
> container management, but there is nothing in the top-container record data
> entry form or update after-the-fact to actually note that a container is
> restricted.
>
>
>
> Brian Thomas
>
> Electronic Records Specialist
>
> Texas State Library and Archives Commission
>
> 1201 Brazos Street
>
> Austin, TX 78701
>
> PH: (512) 475-3374
>
> e-mail: bthomas at tsl.texas.gov
>
> tsl.texas.gov
>
> [image: cid:image001.jpg at 01D029A2.37194C70]
>
>
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>
>
>
>
> --
>
> Maureen Callahan
> Sophia Smith Collection Archivist
> Smith College Special Collections
> Northampton, Massachusetts 01063
> T. 413 585 2981 <(413)%20585-2981> C. 215.863.1860 <(215)%20863-1860>
> mcallahan at smith.edu
>
>
>
> Pronouns: she/her/hers
>
> Facebook: https://www.facebook.com/SophiaSmithCollection/
> Instagram: https://www.instagram.com/smithlibraries/
> Twitter: https://twitter.com/archivalagents
>
>
> *Please note*. Smith College Special Collections is now housed at Young
> Library
> <https://www.smith.edu/libraries/about/new-neilson/wheres-my-library>.
> Learn more about renovations to Neilson Library here
> <https://www.smith.edu/libraries/about/new-neilson>.
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>
>
>
>
> --
>
> Maureen Callahan
> Sophia Smith Collection Archivist
> Smith College Special Collections
> Northampton, Massachusetts 01063
> T. 413 585 2981 <(413)%20585-2981> C. 215.863.1860 <(215)%20863-1860>
> mcallahan at smith.edu
>
>
>
> Pronouns: she/her/hers
>
> Facebook: https://www.facebook.com/SophiaSmithCollection/
> Instagram: https://www.instagram.com/smithlibraries/
> Twitter: https://twitter.com/archivalagents
>
>
> *Please note*. Smith College Special Collections is now housed at Young
> Library
> <https://www.smith.edu/libraries/about/new-neilson/wheres-my-library>.
> Learn more about renovations to Neilson Library here
> <https://www.smith.edu/libraries/about/new-neilson>.
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>


-- 
Maureen Callahan
Sophia Smith Collection Archivist
Smith College Special Collections
Northampton, Massachusetts 01063
T. 413 585 2981 C. 215.863.1860
mcallahan at smith.edu

Pronouns: she/her/hers

Facebook: https://www.facebook.com/SophiaSmithCollection/
Instagram: https://www.instagram.com/smithlibraries/
Twitter: https://twitter.com/archivalagents

*Please note*. Smith College Special Collections is now housed at Young
Library
<https://www.smith.edu/libraries/about/new-neilson/wheres-my-library>.
Learn more about renovations to Neilson Library here
<https://www.smith.edu/libraries/about/new-neilson>.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171025/5ebf65c4/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 5314 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171025/5ebf65c4/attachment.png>

From Christine.Kim at lyrasis.org  Wed Oct 25 20:39:17 2017
From: Christine.Kim at lyrasis.org (Christine Kim)
Date: Thu, 26 Oct 2017 00:39:17 +0000
Subject: [Archivesspace_Users_Group] Webinar Announcement: ArchivesSpace
 PUI Overview and Implementation Strategies - Oct. 26
In-Reply-To: <MWHPR08MB2495786BE3854B2B14C67B4EF5420@MWHPR08MB2495.namprd08.prod.outlook.com>
References: <MWHPR08MB2495786BE3854B2B14C67B4EF5420@MWHPR08MB2495.namprd08.prod.outlook.com>
Message-ID: <BD1B8881-2AFC-472A-A7A7-737E3FED8AF3@lyrasis.org>

Reminder ? Join us for the ArchivesSpace PUI Overview and Implementation Strategies webinar tomorrow, October 26! Details: http://archivesspace.org/webinar-pui/

Sent: Thursday, October 19, 2017 12:25 PM
Subject: Webinar Announcement: ArchivesSpace PUI Overview and Implementation Strategies - Oct. 26

ArchivesSpace PUI Overview and Implementation Strategies

When: Thursday, October 26, 2017
Time: 1:00 p.m. ? 2:30 p.m. EST (10:00 a.m. ? 11:30 a.m. PST)
Where: Webinar at http://lyrasis.adobeconnect.com/rnz7zrtmy04h/
Dial-in only option: 888-354-0094 -- Access code is 731627
No registration required. The session is limited to the first 100 participants. Please feel free to host a webinar viewing group. The webinar will be recorded and available for viewing at a later date.

Webinar description:
Mark Custer and Susan Pyzynski were deeply entrenched in the public interface as they led the community effort of the Public User Interface Enhancement Working Group to shape this essential access point for archival collections. Now they have moved onto their next great challenge ? implementing the PUI at their own institutions. Mark and Susan will each share the strategies they have created to roll out the new PUI. Both institutions aim to be using the new PUI by early next year.

Grand Valley State University has been using the ArchivesSpace PUI since 2014 and have already rolled out the new public interface. Annie Benefiel and Leigh Rupinski will share valuable insight on how the PUI has affected their day-to-day responsibilities of providing access to finding aids, as well as public reception and adapting their instruction for students and researchers.

Please join us on October 26 at 1-2:30 EST as Mark, Susan, Annie, and Leigh as they share their experiences. Please feel free to bring any questions you have on the new public interface!

Presenters:
Mark Custer is an archivist and metadata coordinator at the Beinecke Rare Book & Manuscript Library. He has been heavily involved with the implementation of ArchivesSpace at Yale University, and he is the former chair of the ArchivesSpace Public User Interface Enhancement Project. Mark is a graduate of the School of Information Studies at Syracuse University.

Susan Pyzynski is the Associate Librarian of Houghton Library for Technical Services, Harvard University. Previously, she was the Librarian for Special Collections and Digital Initiatives at Brandeis University. She is leading a project to replace Harvard's archival discovery system.

Annie Benefiel is the Archivist for Collection Management at Grand Valley State University. She oversees the accessioning, processing, and preservation of archival and manuscript collections and manages metadata for archival and digital collections in the Special Collections & University Archives.

Leigh Rupinski is Archivist for Public Services & Community Engagement at Grand Valley State University. She is responsible for instruction, reference, assessment, and other outreach activities for Special Collections & University Archives.

Who should attend:
Everyone interested in learning about the new ArchivesSpace public user interface.

Questions?
Please contact Kim at christine.kim at lyrasis.org<mailto:christine.kim at lyrasis.org>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171026/afe27431/attachment.html>

From bobbi_fox at harvard.edu  Thu Oct 26 10:43:16 2017
From: bobbi_fox at harvard.edu (Fox, Bobbi)
Date: Thu, 26 Oct 2017 14:43:16 +0000
Subject: [Archivesspace_Users_Group] New version of A plugin to support bulk
 uploading of Archival Objects via Excel Spreadsheet
Message-ID: <BN6PR07MB349272F1AE494808192063F890450@BN6PR07MB3492.namprd07.prod.outlook.com>

Good morning,

This message is for those who are using, or thinking of using, our plugin, aspace-import-excel, that adds and/or inserts a set of Archival Objects  from an Excel Spreadsheet (see original announcement below).

While I've been making incremental bug fixes along the way, the sharp-eyed archivists at Harvard's Baker Library noticed a major flaw: the plugin was not honoring the "Restrictions Apply?" flag if it was set to true.

V1.5 (https://github.com/harvard-library/aspace-import-excel/releases/tag/v1.5 ) addresses that flaw, so if you are using (or planning to use) the "Restrictions Apply?" flag, please download and install this Release.

Cheers,
Bobbi Fox, Maintainer
Library Technology Services
Harvard University




From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Fox, Bobbi
Sent: Friday, July 14, 2017 3:44 PM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] A plugin to support bulk uploading of Archival Objects via Excel Spreadsheet

Library Technology Services, which supports the Harvard Library, is pleased to announce the availability of a new plugin, aspace-import-excel, available on GitHub at https://github.com/harvard-library/aspace-import-excel<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_harvard-2Dlibrary_aspace-2Dimport-2Dexcel&d=DwMFAg&c=WO-RGvefibhHBZq3fL85hQ&r=5xWUzLrZrVLeTqs3CDoeRpPtLv1fRM04CCu4TDULrSY&m=VDeZTKvOdMA9ZMbFHCvH9yJVV-frn-Gl_Eb-h9cFl7A&s=eYLbYZkxBN-gM8dcth42UN4U2jqif7APsdEMK8NCBPo&e=> .

Using the provided spreadsheet template, users can go to  a Resource, and either add or insert the set of  Archival Objects that have been defined in the spreadsheet.

Please note carefully the following paragraph in the README:

                The intention is not to completely reproduce a Finding Aid as presented in an EAD XML, or to allow for every permutation of Archival Object creation within ArchivesSpace. We are aiming for the "80% rule"; that is, at least 80% of the work that would be done interactively can be replaced by an excel spreadsheet; additional refinements to individual archival objects (such as addition of agents-as-subjects, assignment of locations to top-level containers, etc.) would take place interactively.


Installation information is on the main README file, with User Documentation at https://github.com/harvard-library/aspace-import-excel/blob/master/user_documentation/USER_DOCUMENTATION.md<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_harvard-2Dlibrary_aspace-2Dimport-2Dexcel_blob_master_user-5Fdocumentation_USER-5FDOCUMENTATION.md&d=DwMFAg&c=WO-RGvefibhHBZq3fL85hQ&r=5xWUzLrZrVLeTqs3CDoeRpPtLv1fRM04CCu4TDULrSY&m=VDeZTKvOdMA9ZMbFHCvH9yJVV-frn-Gl_Eb-h9cFl7A&s=IzC35XyPVdNuLRuJ5da-N43k7lJWm5ThDpGty2MLoP4&e=> , including workflow, step by step usage, and extensive (exhaustive? :-) explanation of the Spreadsheet Template.

This plugin was designed to aid the Harvard Library archival community, but we hope that it may be useful to other archivists in the ArchivesSpace community.

Pull requests welcome.  If you encounter problems, please create an issue on the GitHub repository.

Cheers,
Bobbi Fox, Maintainer



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171026/ed35c050/attachment.html>

From cpeterson at smith.edu  Thu Oct 26 10:54:50 2017
From: cpeterson at smith.edu (Christie Peterson)
Date: Thu, 26 Oct 2017 14:54:50 +0000
Subject: [Archivesspace_Users_Group] Accessions of rare books in AS?
Message-ID: <CAFy-AYJri0003ziAdvak=pi9upnQ=73Bn8m4YKTtHSyXOHn1Jw@mail.gmail.com>

Hello ASpace Users,

Are you using ASpace to track accessions of rare books, both purchased and
gifts?

We're in a moment of rethinking our workflows and tools for our rare book
acquisitions, and considering replacing the paper accessions log with
ASpace.

Since this is bibliographic material and ASpace is designed primarily for
archival/manuscript collections it's a bit of a shoehorn, but not, I think,
a ridiculous one. We would probably need some user-defined fields for
acquisition fund, for example, and we wouldn't require lots of the fields
we do require for accessions of archival materials.

So, if you are using ASpace this way, what has your experience been? How
did you need to modify it in order to bend it to this purpose?

Thanks in advance,

Christie Peterson


-- 
?
Christie S. Peterson

Head of Technical Services for Special Collections
Smith College
Northampton, Mass.
413-585-2996
cpeterson at smith.edu

pronouns: she/her/hers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171026/a9a4222e/attachment.html>

From Joshua.D.Shaw at dartmouth.edu  Thu Oct 26 11:00:18 2017
From: Joshua.D.Shaw at dartmouth.edu (Joshua D. Shaw)
Date: Thu, 26 Oct 2017 15:00:18 +0000
Subject: [Archivesspace_Users_Group] Accessions of rare books in AS?
In-Reply-To: <CAFy-AYJri0003ziAdvak=pi9upnQ=73Bn8m4YKTtHSyXOHn1Jw@mail.gmail.com>
References: <CAFy-AYJri0003ziAdvak=pi9upnQ=73Bn8m4YKTtHSyXOHn1Jw@mail.gmail.com>
Message-ID: <CY4PR03MB3077E543889B5C6834249E31AB450@CY4PR03MB3077.namprd03.prod.outlook.com>

Hi Christie-


This plugin developed by HM for Yale: https://github.com/hudmol/payments_module seems like it might do a bunch of what your looking for as far as the funds tracking goes. We use it at Dartmouth to track manuscript purchases, but I don't think it'd be too much of a stretch to use it for books or other purchases.


Joshua

________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Christie Peterson <cpeterson at smith.edu>
Sent: Thursday, October 26, 2017 10:54:50 AM
To: Archivesspace Users Group
Subject: [Archivesspace_Users_Group] Accessions of rare books in AS?

Hello ASpace Users,

Are you using ASpace to track accessions of rare books, both purchased and gifts?

We're in a moment of rethinking our workflows and tools for our rare book acquisitions, and considering replacing the paper accessions log with ASpace.

Since this is bibliographic material and ASpace is designed primarily for archival/manuscript collections it's a bit of a shoehorn, but not, I think, a ridiculous one. We would probably need some user-defined fields for acquisition fund, for example, and we wouldn't require lots of the fields we do require for accessions of archival materials.

So, if you are using ASpace this way, what has your experience been? How did you need to modify it in order to bend it to this purpose?

Thanks in advance,

Christie Peterson


--
?
Christie S. Peterson

Head of Technical Services for Special Collections
Smith College
Northampton, Mass.
413-585-2996
cpeterson at smith.edu<mailto:cpeterson at smith.edu>

pronouns: she/her/hers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171026/f99a00d7/attachment.html>

From VivianLea.Solek at Kofc.Org  Thu Oct 26 11:04:55 2017
From: VivianLea.Solek at Kofc.Org (VivianLea.Solek at Kofc.Org)
Date: Thu, 26 Oct 2017 11:04:55 -0400
Subject: [Archivesspace_Users_Group] Accessions of rare books in AS?
In-Reply-To: <CAFy-AYJri0003ziAdvak=pi9upnQ=73Bn8m4YKTtHSyXOHn1Jw@mail.gmail.com>
References: <CAFy-AYJri0003ziAdvak=pi9upnQ=73Bn8m4YKTtHSyXOHn1Jw@mail.gmail.com>
Message-ID: <OF8B7E2A64.3D03BAB0-ON852581C5.0052C03B-852581C5.0052D946@kofc.org>

Please post answers to the list -- or copy me on your response to Christie.  Christie, I'm still working on data conversion,
but I have both records/manuscripts and rare books, both of which will be entered into AS.  If you can, please share any
off-list responses you get.

Best,
VivianLea

VivianLea Solek
Archivist
Knights of Columbus Supreme Council Archives

Knights of Columbus Museum
1 State Street
New Haven, CT 06511-6702
Phone 203 752-4578
Fax 203 865-0351



From:	Christie Peterson <cpeterson at smith.edu>
To:	Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>,
Date:	10/26/2017 10:55 AM
Subject:	[Archivesspace_Users_Group] Accessions of rare books in AS?
Sent by:	archivesspace_users_group-bounces at lyralists.lyrasis.org



Hello ASpace Users,

Are you using ASpace to track accessions of rare books, both purchased and gifts?

We're in a moment of rethinking our workflows and tools for our rare book acquisitions, and considering replacing the paper
accessions log with ASpace.

Since this is bibliographic material and ASpace is designed primarily for archival/manuscript collections it's a bit of a
shoehorn, but not, I think, a ridiculous one. We would probably need some user-defined fields for acquisition fund, for
example, and we wouldn't require lots of the fields we do require for accessions of archival materials.

So, if you are using ASpace this way, what has your experience been? How did you need to modify it in order to bend it to
this purpose?

Thanks in advance,

Christie Peterson


--
?
Christie S. Peterson

Head of Technical Services for Special Collections
Smith College
Northampton, Mass.
413-585-2996
cpeterson at smith.edu

pronouns: she/her/hers_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org
https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwICAg&c=C90XguLnqhMT2ADRaOs3gQ&r=balEICFvGrVJ8Sr6vcdFtVtZaJWT42A5myJ4zXSQILc&m=SimhD_yUOHVwKv26a7-MtWXo8Q2nJeCD8a975QKF3nc&s=t96TIHHSje-ZoxJrqMd88YQfQEvEPUrZq2mJUkkulmI&e=


CONFIDENTIALITY NOTICE: This message and any attachments may contain confidential, proprietary or legally privileged information and is intended only for the use of the addressee or addressees named above for its intended purpose.  If you are not the intended recipient of this message, this message constitutes notice that any review, retransmission, distribution, copying or other use or taking any action in reliance on the information in this message and its attachments, is prohibited.  If you receive this communication in error, please immediately advise the sender by reply e-mail and delete this message and its attachments from your system without keeping a copy.  Unless expressly stated in this e-mail, nothing in this message may be construed as a digital or electronic signature.  Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171026/00eb5ef8/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171026/00eb5ef8/attachment.gif>

From cpeterson at smith.edu  Thu Oct 26 11:15:09 2017
From: cpeterson at smith.edu (Christie Peterson)
Date: Thu, 26 Oct 2017 15:15:09 +0000
Subject: [Archivesspace_Users_Group] Accessions of rare books in AS?
In-Reply-To: <CY4PR03MB3077E543889B5C6834249E31AB450@CY4PR03MB3077.namprd03.prod.outlook.com>
References: <CAFy-AYJri0003ziAdvak=pi9upnQ=73Bn8m4YKTtHSyXOHn1Jw@mail.gmail.com>
 <CY4PR03MB3077E543889B5C6834249E31AB450@CY4PR03MB3077.namprd03.prod.outlook.com>
Message-ID: <CAFy-AYJppvqM1ZzsiDMyfNA5u+BTcPVdKMgrtCvY2kkivpmnUQ@mail.gmail.com>

Thanks, Joshua.

Is there documentation of the data model and interface for this plugin
anywhere? Google seems to be failing me on that.

Best,

Christie


>
> --
?
Christie S. Peterson

Head of Technical Services for Special Collections
Smith College
Northampton, Mass.
413-585-2996
cpeterson at smith.edu

pronouns: she/her/hers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171026/39d12402/attachment.html>

From Joshua.D.Shaw at dartmouth.edu  Thu Oct 26 11:29:00 2017
From: Joshua.D.Shaw at dartmouth.edu (Joshua D. Shaw)
Date: Thu, 26 Oct 2017 15:29:00 +0000
Subject: [Archivesspace_Users_Group] Accessions of rare books in AS?
In-Reply-To: <CAFy-AYJppvqM1ZzsiDMyfNA5u+BTcPVdKMgrtCvY2kkivpmnUQ@mail.gmail.com>
References: <CAFy-AYJri0003ziAdvak=pi9upnQ=73Bn8m4YKTtHSyXOHn1Jw@mail.gmail.com>
 <CY4PR03MB3077E543889B5C6834249E31AB450@CY4PR03MB3077.namprd03.prod.outlook.com>,
 <CAFy-AYJppvqM1ZzsiDMyfNA5u+BTcPVdKMgrtCvY2kkivpmnUQ@mail.gmail.com>
Message-ID: <CY4PR03MB30779FEB61F48E5F53BA57B4AB450@CY4PR03MB3077.namprd03.prod.outlook.com>

This page (down at the bottom) gives a visual of the plugin interface: https://guides.library.yale.edu/archivesspace/ArchivesSpaceAccessioning


Yale might have some documentation on the development process/spec that would give the data model details... which would be nicer than pouring over the code...


Joshua

________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Christie Peterson <cpeterson at smith.edu>
Sent: Thursday, October 26, 2017 11:15:09 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Accessions of rare books in AS?

Thanks, Joshua.

Is there documentation of the data model and interface for this plugin anywhere? Google seems to be failing me on that.

Best,

Christie



--
?
Christie S. Peterson

Head of Technical Services for Special Collections
Smith College
Northampton, Mass.
413-585-2996
cpeterson at smith.edu<mailto:cpeterson at smith.edu>

pronouns: she/her/hers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171026/4cd7bc5e/attachment.html>

From mary.caldera at yale.edu  Thu Oct 26 11:32:06 2017
From: mary.caldera at yale.edu (Caldera, Mary)
Date: Thu, 26 Oct 2017 15:32:06 +0000
Subject: [Archivesspace_Users_Group] Accessions of rare books in AS?
In-Reply-To: <CY4PR03MB30779FEB61F48E5F53BA57B4AB450@CY4PR03MB3077.namprd03.prod.outlook.com>
References: <CAFy-AYJri0003ziAdvak=pi9upnQ=73Bn8m4YKTtHSyXOHn1Jw@mail.gmail.com>
 <CY4PR03MB3077E543889B5C6834249E31AB450@CY4PR03MB3077.namprd03.prod.outlook.com>,
 <CAFy-AYJppvqM1ZzsiDMyfNA5u+BTcPVdKMgrtCvY2kkivpmnUQ@mail.gmail.com>
 <CY4PR03MB30779FEB61F48E5F53BA57B4AB450@CY4PR03MB3077.namprd03.prod.outlook.com>
Message-ID: <CY1PR08MB1895A96623CDDEC70A6E08F5E4450@CY1PR08MB1895.namprd08.prod.outlook.com>

Hi, here is a summary<https://guides.library.yale.edu/ld.php?content_id=11942208> of the scope of work. -- Mary

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Joshua D. Shaw
Sent: Thursday, October 26, 2017 11:29 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Accessions of rare books in AS?


This page (down at the bottom) gives a visual of the plugin interface: https://guides.library.yale.edu/archivesspace/ArchivesSpaceAccessioning



Yale might have some documentation on the development process/spec that would give the data model details... which would be nicer than pouring over the code...



Joshua

________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Christie Peterson <cpeterson at smith.edu<mailto:cpeterson at smith.edu>>
Sent: Thursday, October 26, 2017 11:15:09 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Accessions of rare books in AS?

Thanks, Joshua.

Is there documentation of the data model and interface for this plugin anywhere? Google seems to be failing me on that.

Best,

Christie


--
?
Christie S. Peterson

Head of Technical Services for Special Collections
Smith College
Northampton, Mass.
413-585-2996
cpeterson at smith.edu<mailto:cpeterson at smith.edu>

pronouns: she/her/hers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171026/38cd6453/attachment.html>

From mblair1 at stedwards.edu  Thu Oct 26 12:39:33 2017
From: mblair1 at stedwards.edu (Megan Blair)
Date: Thu, 26 Oct 2017 11:39:33 -0500
Subject: [Archivesspace_Users_Group] Accessions of rare books in AS?
In-Reply-To: <OF8B7E2A64.3D03BAB0-ON852581C5.0052C03B-852581C5.0052D946@kofc.org>
References: <CAFy-AYJri0003ziAdvak=pi9upnQ=73Bn8m4YKTtHSyXOHn1Jw@mail.gmail.com>
 <OF8B7E2A64.3D03BAB0-ON852581C5.0052C03B-852581C5.0052D946@kofc.org>
Message-ID: <CAHMBTNkQu5TmsyFQcRqFSW0gor6u7Sv-hs4e8PUuKPjyFwn3bQ@mail.gmail.com>

Hi,

We are also looking at Archivesspace to also be where we put are Rare
Books, so any responses shared to the list would be greatly appreciated.

Thanks!
Megan

On Thu, Oct 26, 2017 at 10:04 AM, <VivianLea.Solek at kofc.org> wrote:

> Please post answers to the list -- or copy me on your response to
> Christie.  Christie, I'm still working on data conversion, but I have both
> records/manuscripts and rare books, both of which will be entered into AS.
> If you can, please share any off-list responses you get.
>
> Best,
> VivianLea
>
> VivianLea Solek
> Archivist
> Knights of Columbus Supreme Council Archives
>
> Knights of Columbus Museum
> 1 State Street
> New Haven, CT 06511-6702
> Phone 203 752-4578 <(203)%20752-4578>
> Fax 203 865-0351 <(203)%20865-0351>
>
> [image: Inactive hide details for Christie Peterson ---10/26/2017 10:55:08
> AM---Hello ASpace Users, Are you using ASpace to track acces]Christie
> Peterson ---10/26/2017 10:55:08 AM---Hello ASpace Users, Are you using
> ASpace to track accessions of rare books, both purchased and
>
> From: Christie Peterson <cpeterson at smith.edu>
> To: Archivesspace Users Group <archivesspace_users_group@
> lyralists.lyrasis.org>,
> Date: 10/26/2017 10:55 AM
> Subject: [Archivesspace_Users_Group] Accessions of rare books in AS?
> Sent by: archivesspace_users_group-bounces at lyralists.lyrasis.org
> ------------------------------
>
>
>
> Hello ASpace Users,
>
> Are you using ASpace to track accessions of rare books, both purchased and
> gifts?
>
> We're in a moment of rethinking our workflows and tools for our rare book
> acquisitions, and considering replacing the paper accessions log with
> ASpace.
>
> Since this is bibliographic material and ASpace is designed primarily for
> archival/manuscript collections it's a bit of a shoehorn, but not, I think,
> a ridiculous one. We would probably need some user-defined fields for
> acquisition fund, for example, and we wouldn't require lots of the fields
> we do require for accessions of archival materials.
>
> So, if you are using ASpace this way, what has your experience been? How
> did you need to modify it in order to bend it to this purpose?
>
> Thanks in advance,
>
> Christie Peterson
>
>
> --
> ?
> Christie S. Peterson
>
> Head of Technical Services for Special Collections
> Smith College
> Northampton, Mass.
> 413-585-2996 <(413)%20585-2996>
> *cpeterson at smith.edu* <cpeterson at smith.edu>
>
> pronouns: she/her/hers_______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> https://urldefense.proofpoint.com/v2/url?u=http-3A__
> lyralists.lyrasis.org_mailman_listinfo_archivesspace-
> 5Fusers-5Fgroup&d=DwICAg&c=C90XguLnqhMT2ADRaOs3gQ&r=
> balEICFvGrVJ8Sr6vcdFtVtZaJWT42A5myJ4zXSQILc&m=SimhD_yUOHVwKv26a7-
> MtWXo8Q2nJeCD8a975QKF3nc&s=t96TIHHSje-ZoxJrqMd88YQfQEvEPUrZq2mJUkkulmI&e=
>
> CONFIDENTIALITY NOTICE: This message and any attachments may contain
> confidential, proprietary or legally privileged information and is intended
> only for the use of the addressee or addressees named above for its
> intended purpose. If you are not the intended recipient of this message,
> this message constitutes notice that any review, retransmission,
> distribution, copying or other use or taking any action in reliance on the
> information in this message and its attachments, is prohibited. If you
> receive this communication in error, please immediately advise the sender
> by reply e-mail and delete this message and its attachments from your
> system without keeping a copy. Unless expressly stated in this e-mail,
> nothing in this message may be construed as a digital or electronic
> signature. Thank you.
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>


-- 
Megan M. Blair
Archivist and Public Services Librarian
Munday Library
St. Edward's University
3001 S. Congress Ave.
Austin, TX 78704
512.428.1047
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171026/27050202/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171026/27050202/attachment.gif>

From prom at illinois.edu  Thu Oct 26 15:22:52 2017
From: prom at illinois.edu (Prom, Christopher John)
Date: Thu, 26 Oct 2017 19:22:52 +0000
Subject: [Archivesspace_Users_Group] Entity relationship model?
In-Reply-To: <CAHMBTNkQu5TmsyFQcRqFSW0gor6u7Sv-hs4e8PUuKPjyFwn3bQ@mail.gmail.com>
References: <CAFy-AYJri0003ziAdvak=pi9upnQ=73Bn8m4YKTtHSyXOHn1Jw@mail.gmail.com>
 <OF8B7E2A64.3D03BAB0-ON852581C5.0052C03B-852581C5.0052D946@kofc.org>
 <CAHMBTNkQu5TmsyFQcRqFSW0gor6u7Sv-hs4e8PUuKPjyFwn3bQ@mail.gmail.com>
Message-ID: <C2634D9E-C3B4-441F-AA54-A6777121824C@illinois.edu>

Hi everyone,

I am wondering if anyone has tried to complete an entity relationship model for ASpace, using mysql workbench or something similar?

I am aware of the architecture overview and the API documentation?which are both very useful--but really more interested in how the data tables relate to each other in mysql.

thanks in advance for any help that you might be able to provide,


Chris

Christopher J. Prom, PhD
Andrew S. G. Turyn Professor
Assistant University Archivist
146 Library
1408 W. Gregory Drive
Urbana, IL 61801

prom at illinois.edu<mailto:prom at illinois.edu>
217 244 2052

http://archivalconnections.org


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171026/b008e55a/attachment.html>

From laney.mcglohon at lyrasis.org  Thu Oct 26 15:45:05 2017
From: laney.mcglohon at lyrasis.org (Laney McGlohon)
Date: Thu, 26 Oct 2017 19:45:05 +0000
Subject: [Archivesspace_Users_Group] Entity relationship model?
Message-ID: <DDE0CED8-CC86-42BB-AC4C-5A48FC0F9BA5@lyrasis.org>

Hey Chris,

I generated one using mysql workbench for ASpace version 2.1.0. I have attached it to this email.

Please let me know if you have any questions.

Best,
Laney

Laney McGlohon
ArchivesSpace Tech Lead
laney.mcglohon at lyrasis.org<mailto:laney.mcglohon at lyrasis.org>
800.999.8558 x2927
laneymcglohon Skype



From: <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of "Prom, Christopher John" <prom at illinois.edu>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Date: Thursday, October 26, 2017 at 3:22 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Entity relationship model?

Hi everyone,

I am wondering if anyone has tried to complete an entity relationship model for ASpace, using mysql workbench or something similar?

I am aware of the architecture overview and the API documentation?which are both very useful--but really more interested in how the data tables relate to each other in mysql.

thanks in advance for any help that you might be able to provide,


Chris

Christopher J. Prom, PhD
Andrew S. G. Turyn Professor
Assistant University Archivist
146 Library
1408 W. Gregory Drive
Urbana, IL 61801

prom at illinois.edu<mailto:prom at illinois.edu>
217 244 2052
http://archivalconnections.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171026/9b783bec/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ASpaceRel2.1.0.mwb
Type: application/octet-stream
Size: 263052 bytes
Desc: ASpaceRel2.1.0.mwb
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171026/9b783bec/attachment-0001.obj>

From prom at illinois.edu  Thu Oct 26 15:47:25 2017
From: prom at illinois.edu (Prom, Christopher John)
Date: Thu, 26 Oct 2017 19:47:25 +0000
Subject: [Archivesspace_Users_Group] Entity relationship model?
In-Reply-To: <DDE0CED8-CC86-42BB-AC4C-5A48FC0F9BA5@lyrasis.org>
References: <DDE0CED8-CC86-42BB-AC4C-5A48FC0F9BA5@lyrasis.org>
Message-ID: <C89C2BD2-FB90-470D-A27D-4B797FA74CB5@illinois.edu>

Thanks Laney.  This is great. I was just about to see if I could reverse engineer one, and I assume that the DB structure hasn't really changed in the latest version, so I'll work with this and touch base if I have any questions.

Thanks,

Chris

On Oct 26, 2017, at 2:45 PM, Laney McGlohon <laney.mcglohon at lyrasis.org<mailto:laney.mcglohon at lyrasis.org>> wrote:

Hey Chris,

I generated one using mysql workbench for ASpace version 2.1.0. I have attached it to this email.

Please let me know if you have any questions.

Best,
Laney

Laney McGlohon
ArchivesSpace Tech Lead
laney.mcglohon at lyrasis.org<mailto:laney.mcglohon at lyrasis.org>
800.999.8558 x2927
laneymcglohon Skype



From: <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of "Prom, Christopher John" <prom at illinois.edu<mailto:prom at illinois.edu>>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Date: Thursday, October 26, 2017 at 3:22 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] Entity relationship model?

Hi everyone,

I am wondering if anyone has tried to complete an entity relationship model for ASpace, using mysql workbench or something similar?

I am aware of the architecture overview and the API documentation?which are both very useful--but really more interested in how the data tables relate to each other in mysql.

thanks in advance for any help that you might be able to provide,


Chris

Christopher J. Prom, PhD
Andrew S. G. Turyn Professor
Assistant University Archivist
146 Library
1408 W. Gregory Drive
Urbana, IL 61801

prom at illinois.edu<mailto:prom at illinois.edu>
217 244 2052
http://archivalconnections.org<http://archivalconnections.org/>

<ASpaceRel2.1.0.mwb>_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171026/ae6b72ce/attachment.html>

From michael.rush at yale.edu  Fri Oct 27 08:59:52 2017
From: michael.rush at yale.edu (Rush, Michael)
Date: Fri, 27 Oct 2017 12:59:52 +0000
Subject: [Archivesspace_Users_Group] Accessions of rare books in AS?
In-Reply-To: <CY1PR08MB1895A96623CDDEC70A6E08F5E4450@CY1PR08MB1895.namprd08.prod.outlook.com>
References: <CAFy-AYJri0003ziAdvak=pi9upnQ=73Bn8m4YKTtHSyXOHn1Jw@mail.gmail.com>
 <CY4PR03MB3077E543889B5C6834249E31AB450@CY4PR03MB3077.namprd03.prod.outlook.com>,
 <CAFy-AYJppvqM1ZzsiDMyfNA5u+BTcPVdKMgrtCvY2kkivpmnUQ@mail.gmail.com>
 <CY4PR03MB30779FEB61F48E5F53BA57B4AB450@CY4PR03MB3077.namprd03.prod.outlook.com>
 <CY1PR08MB1895A96623CDDEC70A6E08F5E4450@CY1PR08MB1895.namprd08.prod.outlook.com>
Message-ID: <SN2PR0801MB2303C3C4B7A94975FEFC9A13E45A0@SN2PR0801MB2303.namprd08.prod.outlook.com>

All,

Following up on this thread, I can say a bit more here about the Yale Payments Module plugin, as I was the lead person for delineating the functional requirements.

The spec that Mary shared is still mostly up-to-date, but the plugin has evolved a bit since then. The most recent release (https://github.com/hudmol/payments_module/releases/tag/v2.1.x-1.2), for example, re-orders some of the fields based on our experience of using the plugin for a few years, makes a few other cosmetic changes, and most importantly changes the amount fields from text to decimal. It also requires ASpace 2.0 or higher.

The basic data model that any accession may have zero or one payment summary record. That payment summary record has three fields: Total Price, Currency, and an ?In Lot? Boolean (which we use to designate when an accession represents more than one line item from an invoice, or when one line item from an invoice has been split into multiple accessions). Each payment summary may have zero or more payment records associated with it. Each payment record may contain the following fields: Payment Date, Invoice Number, Fund Code, Amount, USD Equivalent Amount, Authorizer [meaning which curator OKed the payment], and Note. We often pay for significant purchases in installments, or pay for single purchases on multiple funds, hence the need to record multiple payments. All fields in the payment summary and the payment record are optional.

I should note that the Payment Module plugin also adds several fields to advanced search, like Fund Code, Payment Date, and Invoice Number.

Circling back to using ASpace for rare book accessions, a former colleague and I put a lot of thought into how we might do that. We have a large volume of rare book accessioning and ultimately that effort got shelved, but we did give it a lot of thought, and even developed some plugins to support it, most notably the OCLC record importer ( https://github.com/hudmol/aspace_oclc) and a modified import map for MARCXML to Acessions (https://github.com/hudmol/yale_marcxml2accession_extras). We have never used these in production and so I?m certain they would need to be updated before use with the current version of ASpace. Basically we mapped our current dbText-based book accessioning db to ASpace with a mix of regular and user defined fields. From a data perspective it would have worked fine ? for us the challenge was the feeling that the ASpace interface wouldn?t be sufficiently flexible or efficient to represent an improvement over the currently used system. But if you have a more modest volume of rare book accessions, I?m certain ASpace can be adapted to the task.

Happy to answer more questions or chat offline if that would be helpful.

Mike

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Caldera, Mary
Sent: Thursday, October 26, 2017 11:32 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Accessions of rare books in AS?

Hi, here is a summary<https://guides.library.yale.edu/ld.php?content_id=11942208> of the scope of work. -- Mary

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Joshua D. Shaw
Sent: Thursday, October 26, 2017 11:29 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Accessions of rare books in AS?


This page (down at the bottom) gives a visual of the plugin interface: https://guides.library.yale.edu/archivesspace/ArchivesSpaceAccessioning



Yale might have some documentation on the development process/spec that would give the data model details... which would be nicer than pouring over the code...



Joshua

________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Christie Peterson <cpeterson at smith.edu<mailto:cpeterson at smith.edu>>
Sent: Thursday, October 26, 2017 11:15:09 AM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Accessions of rare books in AS?

Thanks, Joshua.

Is there documentation of the data model and interface for this plugin anywhere? Google seems to be failing me on that.

Best,

Christie


--
?
Christie S. Peterson

Head of Technical Services for Special Collections
Smith College
Northampton, Mass.
413-585-2996
cpeterson at smith.edu<mailto:cpeterson at smith.edu>

pronouns: she/her/hers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171027/708541b8/attachment.html>

From s.innes at auckland.ac.nz  Mon Oct 30 16:31:56 2017
From: s.innes at auckland.ac.nz (Stephen Innes)
Date: Mon, 30 Oct 2017 20:31:56 +0000
Subject: [Archivesspace_Users_Group] Customizing the Public Interface PDF
In-Reply-To: <9d4f60c461c04cd8959f9b15b7ce821f@evcspmbx05.ads.northwestern.edu>
References: <b6cd71c071f34dc2ad99e56665094c58@evcspmbx05.ads.northwestern.edu>, 
 <DM5PR13MB17211659AC9E67A31F2712888F9C0@DM5PR13MB1721.namprd13.prod.outlook.com>
 <BN3PR08MB1303E2D149E5E6D2262766968C9C0@BN3PR08MB1303.namprd08.prod.outlook.com>
 <9d4f60c461c04cd8959f9b15b7ce821f@evcspmbx05.ads.northwestern.edu>
Message-ID: <42c964faf0f741389fc0e391db03a11f@uxcn13-ogg-c.UoA.auckland.ac.nz>

I have a further question regarding the PUI PDF processing. We have just implemented v2.2.0 which is working very well, but have encountered  a problem with the PDF generated from the Print button. The PDF includes a lot of EAD tags for formatting such as:

The Holloway Press Launch. Includes copy of <span class="italic emph">The
University of Auckland News</span> article &quot;Press keeps alive
traditional printing techniques&quot;, published in Vol. 24, No. 10, Nov/Dec
1994, p 27., Oct 1994

Instead of:



The Holloway Press Launch. Includes copy of The University of Auckland News article "Press keeps alive traditional printing techniques", published in Vol. 24, No. 10, Nov/Dec 1994, p 27.


This seems to be a similar issue to AR-1851. Should I post a new ticket?

Regards,

Stephen Innes


Stephen Innes (ALIANZA)
Special Collections Manager
General Library, Te Herenga M?tauranga Wh?nui
The University of Auckland
Private Bag 92019
Auckland 1142
New Zealand
Telephone (649) 373-7599 ext. 88062 | Fax (649) 373-7565
Website: http://www.library.auckland.ac.nz/about-us/collections/special-collections/general-library
Online exhibition: Special Collections First World War Centenary 2014-2018<http://www.specialcollections.auckland.ac.nz/ww1-centenary>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171030/a8216a47/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pdf-tags.PNG
Type: image/png
Size: 67019 bytes
Desc: pdf-tags.PNG
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171030/a8216a47/attachment.png>

From laurie.arp at lyrasis.org  Tue Oct 31 12:09:20 2017
From: laurie.arp at lyrasis.org (Laurie Arp)
Date: Tue, 31 Oct 2017 16:09:20 +0000
Subject: [Archivesspace_Users_Group] ArchivesSpace board update
Message-ID: <BN6PR08MB2865085B2BF322574A50C1DB8A5E0@BN6PR08MB2865.namprd08.prod.outlook.com>

Distributing for Carol Mandel...



Dear ArchivesSpace members,

I am writing to report on the ArchivesSpace Governance Board 1st Quarter meeting, which was held in Chicago on Sept 8th.

We were pleased to welcome new board members:


  *   Nicholas Zmijewski, Industrial Archives & Library, representing the very small membership level
  *   Peter Carini, Dartmouth College, representing the medium membership level
  *   Gordon Daines, Brigham Young University, representing the large membership level
  *   Tammy Dearie, University of California, San Diego, replacing Brian Schottlaender who retired in July

We reviewed the continued dedicated work of the Technical Advisory Council and User Advisory Council and thank the members for their strong participation. The operations update highlighted progress in development, especially the contributions from several ArchivesSpace member institutions that sponsored or contributed important functionality.  The board is also encouraged by the creation of and continued progress by the core committers group.

The board is making progress on several important foundation documents.  Work continues on the bylaws review and the organizational home agreement.  In addition the board is working on reviewing and updating a mission statement, guiding principles and financial reserve policy.  An updated membership agreement policy was approved.  We are also initiating a review of the Registered Service Provider (RSP) program to ensure it meets the needs of ArchivesSpace members and other users.

In closing, I am very happy to report that the ArchivesSpace membership organization continues to be vital and growing, with members making contributions to all facets of the program.

The Board welcomes your communications and comments. Thank you for your continuing support and ongoing participation in the community we have created together.

Respectfully,

Carol A. Mandel
Chair, ArchivesSpace Governance Board
Dean, Division of Libraries, New York University


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20171031/3c34f510/attachment.html>