[Archivesspace_Users_Group] Seeking feedback on tickets by Feb. 1

[Tang, Lydia]

Hello all!


The Development Prioritization and Usability sub-teams have prepared a brief 
list of tickets that we are seeking community feedback on!


Please feel free to comment on these tickets and/or discuss them on the list.  
These tickets may be complex and/or have a high impact on the program, so we 
definitely would appreciate your thoughts on these!


  *   Geolocation: https://archivesspace.atlassian.net/browse/ANW-357
  *   Moving sidebar tree to the left: 
https://archivesspace.atlassian.net/browse/ANW-769
  *   Downloading PDF from any view of the collection:

https://archivesspace.atlassian.net/browse/ANW-773


Thank you for your feedback and consideration!  We’ll send a reminder after the 
new year, with the hope of finalizing feedback by the beginning of February.

Lydia Tang and Maggie Hughes

~ on behalf of the Development Prioritization and Usability subteams


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

Re: [Archivesspace_Users_Group] Seeking feedback on tickets by Feb. 1

[Natalie Adams]

Dear Lydia,

I don’t seem to be able to add a comment directly on the ticket, but I would 
like to comment on:


  *   Downloading PDF from any view of the collection:
https://archivesspace.atlassian.net/browse/ANW-773

We are implementing one instance of AS for the University Library and 29 
partner organisations in Cambridge. Some of the resources will be huge, 
multi-level descriptions (eg the University archives – see skeleton record here 
https://arcspace-pub.lib.cam.ac.uk/repositories/2/resources/7) and what would 
be really helpful to us would be the ability to download a pdf of sections of 
the resource (ie at levels below the resource). I understand that the PDF 
generator works using EAD and this is why it is only possible to generate a PDF 
of a complete finding aid but thought it would be worth adding a note about 
this.
Best wishes,

Natalie


Natalie Adams
Systems Archivist
Cambridge University Library
West Road
Cambridge
Cambridge, CB3 9DR
Tel 01223 766377
www.lib.cam.ac.uk/
Normal working days are Monday to Thursday.


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Tang, 
Lydia
Sent: 16 December 2019 21:41
To: archivesspace_users_group@lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Seeking feedback on tickets by Feb. 1


Hello all!


The Development Prioritization and Usability sub-teams have prepared a brief 
list of tickets that we are seeking community feedback on!


Please feel free to comment on these tickets and/or discuss them on the list.  
These tickets may be complex and/or have a high impact on the program, so we 
definitely would appreciate your thoughts on these!


  *   Geolocation: https://archivesspace.atlassian.net/browse/ANW-357
  *   Moving sidebar tree to the left: 
https://archivesspace.atlassian.net/browse/ANW-769
  *   Downloading PDF from any view of the collection:

https://archivesspace.atlassian.net/browse/ANW-773


Thank you for your feedback and consideration!  We’ll send a reminder after the 
new year, with the hope of finalizing feedback by the beginning of February.

Lydia Tang and Maggie Hughes

~ on behalf of the Development Prioritization and Usability subteams


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

[Archivesspace_Users_Group] Using ArchivesSpace for collection management: need trigger dates in the future

[Natalie Adams]

Dear all,

We are relatively new to ArchivesSpace and are currently exploring using the 
collection management functions in AS with a view to producing local guidelines 
for archivists working in the Cambridge University Library and partner 
organisations. Our ideal is that AS becomes the one (and only) place for notes 
and documentation about collection management.

One of the issues we are seeking to accommodate is using AS to prompt us about 
dates for future action. Here are a couple of scenarios of the type of thing we 
would like to do:-


1)  Produce reports of future dates when archival material is due to be 
opened or reviewed


2)  Produce reports of future dates to prompt action by the repository eg 
get back in touch with a depositor to remind them to return deed of a gift



For scenario 1, we've been exploring adding dates to resource/resource 
component descriptions in the 'conditions governing access' note field and 
linking the resource/resource component to an Assessment record. Our tech team 
wrote us a report which could pull together any resource/resource with a date 
in the 'conditions governing access' field. This looks like it will work well.



For scenario 2, we're a little stuck. We think it would be helpful to be able 
to include a future date to an assessment record, but I wondered whether any 
other AS users out there have come up with different solutions to this. I am 
sorry if I have missed anything obvious but would be very grateful for any help 
or advice. It would also be interesting to know whether other repositories 
would be interested in amending the assessment record in this way.



Best wishes,



Natalie

Natalie Adams
Systems Archivist
Cambridge University Library
West Road
Cambridge
Cambridge, CB3 9DR
Tel 01223 766377
www.lib.cam.ac.uk/
Normal working days are Monday to Thursday.

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

[Archivesspace_Users_Group] Webinar Announcement: Integrating ArchivesSpace and Aviary

[Jessica Crouch]

Webinar Announcement: Integrating ArchivesSpace and Aviary

ArchivesSpace is pleased to announce the fourth webinar in our series focused 
on Integrations with ArchivesSpace.  Each webinar in this series will highlight 
an integration with another application used in archives that ArchivesSpace 
members have worked on or requested.  The webinar series will feature both open 
source and proprietary systems.

Our fourth webinar in this series will feature an integration with the 
audiovisual publishing platform, 
Aviary.

When: January 15, 2020
Time: 2:00 p.m. – 3:00 p.m. ET (11:00 a.m. – noon PT; 7 p.m. – 8 p.m. GMT)
Where: Zoom
https://lyrasis.zoom.us/j/108009089

One tap mobile
+19292056099,,108009089# US (New York)
+16699006833,,108009089# US (San Jose)

Dial by your location
+1 929 205 6099 US (New York)
+1 669 900 6833 US (San Jose)
888 475 4499 US Toll-free
877 853 5257 US Toll-free
Meeting ID: 108 009 089
Find your local number: https://zoom.us/u/awkFNWPxh

Webinar description:
This webinar will be recorded and made available on the ArchivesSpace YouTube 
channel.
In this webinar, Bertram Lyons (Aviary) will provide an overview of Aviary, 
highlighting access controls, accessibility and compliance.   He will also 
demonstrate how Aviary integrates with ArchivesSpace and how this integration 
benefits archivists, specifically archivists from smaller organizations.
Kevin Glick (Yale University Libraries) will present on Yale’s integration of 
ArchivesSpace and Aviary.  The presentation will highlight how Yale recognized 
the need for this integration within the libraries and both their vision and 
their experience implementing this integration. Kevin will also offer 
recommendations to other users considering integration.
Presenters:
Bertram Lyons specializes in the acquisition, management, and preservation of 
documentary, research, and cultural heritage collections. He has developed 
tools, policies, and partnerships around the development and management of 
analog and digital archival collections. For fifteen years, Bert has worked as 
an archivist for extensive archives, first at the Alan Lomax Archive and most 
recently at the American Folklife Center (AFC) at the Library of Congress. Bert 
is active with professional archival organizations including the International 
Association of Sound and Audiovisual Archives, the Society of American 
Archivists, the Association of Recorded Sound Collections, and the Association 
of Moving Image Archivists. He has also received certification from the Academy 
of Certified Archivists and is a graduate of the Archives Leadership Institute. 
He holds an MA in museum studies with a focus in American studies and archival 
theory from the University of Kansas.

Kevin Glick is Head of Digitization and Digital Preservation and Archivist in 
Yale University Library’s Manuscripts & Archives, where he currently focuses on 
digitization, digital libraries, and other technology issues in special 
collections and archives. In addition, Kevin manages the architecture of the 
Fortunoff Video Archive for Holocaust Testimony's digital preservation and 
access systems as well as digitization of all materials related to the 
collection.

Who should attend:
Anyone interested in possibilities for integrating ArchivesSpace with Aviary, 
those who have integrated ArchivesSpace and Aviary and would like to offer 
insight to others, and those who are interested in working with fellow 
community members to make integrations with ArchivesSpace easier.

Questions?

Contact Jessica at 
jessica.cro...@lyrasis.org if you have 
questions about this webinar or the Integrations with ArchivesSpace webinar 
series.

The next Integrations with ArchivesSpace webinar will be: Integrating 
ArchivesSpace with Archivematica, February 19, 2020 at 2pm ET (11am PT)

Jessica Dowd Crouch
Community Engagement Coordinator for ArchivesSpace
jessica.cro...@lyrasis.org
Skype: jdowdcrouch

[page1image482511520]

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

Re: [Archivesspace_Users_Group] Seeking feedback on tickets by Feb. 1

[Rachel Donahue]

I'm having trouble logging in to comment (or even viewing issues, what's
up, Atlassian??), so I'll respond here.

*769: *Yes, please!

*773: *I agree with Ed Busch that both options (this and 950) should be
offered. 950 is about using CSS to print the current webpage rather than
the full finding aid PDF. I would, however, make it clear on the
button/with a text link that that is what's going to happen.

*357:* This sounds like a great feature to have, but also like it could
involve a fair amount of work. For us, it definitely isn't a high priority.

Best,
Rachel

On Tue, Dec 17, 2019 at 8:01 AM Tang, Lydia  wrote:

> Hello all!
>
>
>
> The Development Prioritization and Usability sub-teams have prepared a
> brief list of tickets that we are seeking community feedback on!
>
>
>
> Please feel free to comment on these tickets and/or discuss them on the
> list.  These tickets may be complex and/or have a high impact on the
> program, so we definitely would appreciate your thoughts on these!
>
>
>
>- Geolocation: https://archivesspace.atlassian.net/browse/ANW-357
>- Moving sidebar tree to the left:
>https://archivesspace.atlassian.net/browse/ANW-769
>- Downloading PDF from any view of the collection:
>
> https://archivesspace.atlassian.net/browse/ANW-773
> 
>
> Thank you for your feedback and consideration!  We’ll send a reminder
> after the new year, with the hope of finalizing feedback by the beginning
> of February.
>
> Lydia Tang and Maggie Hughes
>
> ~ on behalf of the Development Prioritization and Usability subteams
>
>
>
>
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Using ArchivesSpace for collection management: need trigger dates in the future

[Maureen Callahan]

Dear Natalie,

It's great to see repositories using ArchivesSpace to kick off automated
actions!

I was lucky enough to have worked on the team that had put together the
specification for your scenario 1, and that was exactly the outcome we had
in mind. (A video about that is here, although the version is very behind:
https://www.youtube.com/watch?v=biCDhkbBSng )

For your scenario 2, I've been fantasizing about future ArchivesSpace
functionality that would govern legal agreements -- a "legal agreement"
record type that could track who signed onto the agreement, when, and what
was agreed upon, and this information could be then linked to all of the
materials that this agreement governs. This is to say that I don't think
that this is the kind of thing that ASpace is currently designed to do and
I tend to be nervous about bending enterprise systems to make them do hacks
for us. But I would be very eager to talk more with you and others to come
up with a specification for these kinds of collections management /
collection development activities!

Best wishes,
Maureen

On Tue, Dec 17, 2019 at 4:47 AM Natalie Adams  wrote:

> Dear all,
>
>
>
> We are relatively new to ArchivesSpace and are currently exploring using
> the collection management functions in AS with a view to producing local
> guidelines for archivists working in the Cambridge University Library and
> partner organisations. Our ideal is that AS becomes the one (and only)
> place for notes and documentation about collection management.
>
>
>
> One of the issues we are seeking to accommodate is using AS to prompt us
> about dates for future action. Here are a couple of scenarios of the type
> of thing we would like to do:-
>
> 1)  Produce reports of future dates when archival material is due to
> be opened or reviewed
>
> 2)  Produce reports of future dates to prompt action by the
> repository eg get back in touch with a depositor to remind them to return
> deed of a gift
>
>
>
> For scenario 1, we’ve been exploring adding dates to resource/resource
> component descriptions in the ‘conditions governing access’ note field and
> linking the resource/resource component to an Assessment record. Our tech
> team wrote us a report which could pull together any resource/resource with
> a date in the ‘conditions governing access’ field. This looks like it will
> work well.
>
>
>
> For scenario 2, we’re a little stuck. We think it would be helpful to be
> able to include a future date to an assessment record, but I wondered
> whether any other AS users out there have come up with different solutions
> to this. I am sorry if I have missed anything obvious but would be very
> grateful for any help or advice. It would also be interesting to know
> whether other repositories would be interested in amending the assessment
> record in this way.
>
>
>
> Best wishes,
>
>
>
> Natalie
>
>
>
> *Natalie Adams*
>
> Systems Archivist
>
> Cambridge University Library
>
> West Road
>
> Cambridge
>
> Cambridge, CB3 9DR
>
> Tel 01223 766377
>
> www.lib.cam.ac.uk/
>
> *Normal working days are Monday to Thursday.*
>
>
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@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
413 585 2981
mcalla...@smith.edu

Pronouns: she/her/hers

Smith College Special Collections is now housed at Young Library
.
Learn more about renovations to Neilson Library here
. Visit us in our
reading room in Young Library 202. Classes are taught in Young Library 201.

More information about our current collecting goals is available in
our collection
development strategy

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

Re: [Archivesspace_Users_Group] Revised Proposal for Container Management Enhancements - Call for Community Input

[Rachel Aileen Searcy]

Hi Robin,

We wanted to provide some comments to this proposal for enhancements to
ArchivesSpace’s container management functionality. We’d like to thank
Harvard for their efforts to put this together to make ArchivesSpace a more
useful system for the broader community. We are also a large,
multi-repository institution with a single ArchivesSpace instance, and have
encountered many of the challenges outlined in this document, although we
do operate slightly differently (for example, our locations are shared
across our repositories to make the best use of the space we have).

We too have found it difficult to browse, filter, and sort through our
large number of location records, especially when linking top containers to
locations, and support the improvements specified in this document to more
efficiently perform these tasks. We would appreciate the ability to return
to an existing top container search, but would not want to sacrifice
overall system performance for this feature. While the ability to merge
locations would be useful in cleaning up obsolete or duplicate locations,
we wonder if the logic required to create this functionality might be more
complicated than other merging in the system, as there are currently
measures in place to ensure that locations cannot be deleted while holdings
are linked to them. We think this logic should remain in place to prevent
deleting important data.

We might not use many of the proposed enhancements (e.g., barcodes for
container children, repositories for container profiles) but as long as
they are optional and unobtrusive to users who do not employ them, we do
not have strong feelings. We do have concerns about the proposal to add a
Note field to the Top Container record, especially without a compelling use
case to justify its inclusion, as there is such a high likelihood of this
field being misused to record information about the contents of a box (as
opposed to the container itself) more appropriate for specific EAD fields.
It reminds us of boxes that have labels with crucial information about the
materials inside that is not documented anywhere else, and we wouldn’t want
to encourage that type of practice. If there are compelling use cases for
this field, we’d prefer values to be controlled so that they can be
structured, queried, and used somewhat consistently.

Again, thank you for developing this proposal and continuing the
conversation. We’re eager to see how this work continues.

Best wishes,

Rachel

On Tue, Dec 10, 2019 at 1:19 PM Wendler, Robin King <
robin_wend...@harvard.edu> wrote:

> Dear ArchivesSpace Community,
>
> The Harvard Library has been reviewing container and location management
> functionality in ArchivesSpace and we are proposing to make enhancements to
> this functionality that we would like to contribute to the core code. With
> these enhancements, we hope to make finding, viewing, and updating
> information related to containers and locations in the staff interface more
> efficient and effective.
>
>
>
> Some of you may remember a proposal we distributed this time last year. A
> variety of factors delayed the work, so we have significantly revised the
> proposal based on the valuable feedback provided by the ArchivesSpace
> community and informed by Harvard archivists’ increasing experience with
> container management in ArchivesSpace. Some proposals have been removed,
> while others have been added or altered.
>
>
>
> Additions include
>
>- Return to Top Container search results from viewing an individual
>Top Container record
>- Bulk or batch function to create new Top Containers, associate
>existing Locations with them, and link them to multiple existing archival
>objects.
>- Bulk operation to delete barcodes from Top Containers
>- File-upload function to add Locations to Top Containers
>- Ability to merge Location records
>
>
>
> The most significant changes to previous proposals include the following:
>
>- The proposed additional indicator fields and ILS Bibliographic
>Record ID field in Top Containers have been removed.
>- The proposed Note field and Inactive checkbox for Locations, along
>with all functionality associated with inactive status, have been removed.
>- Automatic scoping of Container Profiles, Locations, and Location
>Profiles by repository appears to be too complex, given the community
>request to make repositories repeatable and the desire for it to be an
>installation configuration option. In lieu of that, the revised proposal
>adds a repeatable, optional repository field to container profiles and adds
>a facet for filtering by repository to browse results for Container
>Profiles and Locations.
>- Proposed functionality around Location status has been removed
>
>
>
> The revised draft proposal is attached to this email and we are asking for
> community review and feedback. The proposal includes the rationale for the
> changes, a list 

[Archivesspace_Users_Group] Working with Ruby

[Alan Manifold]

Hi all,
I am new to Ruby, and have been adding some functionality to our PUI through a 
local plugin. I’m finding the testing a bit slow.

Whenever I make a change to the code or configuration files, I have to restart 
the application before I see them in effect. This generally takes 4-5 minutes 
on our server. That’s not terrible, but I wondered if there’s a way to speed up 
the process. Is there any way to avoid restarting the application each time I 
make a change, such as just recompiling a single file or something like that? 
It would save me a lot of time in my testing.

Thanks for any tips you can share.

Regards,
Alan

Alan Manifold | Library Systems & Digital Preservation Manager | Collection 
Development & Description
State Library Victoria | 328 Swanston Street | Melbourne VIC 3000
T +61 3 8664 7122 | amanif...@slv.vic.gov.au
slv.vic.gov.au

[https://www.slv.vic.gov.au/sites/default/files/email_signature/signature.jpg?9]
[follow   us]
[SLV 
facebook]
 [SLV twitter]   [SLV youtube] 
[SLV   instagram] 
[Gold Winner 2018 RACV Victorian Tourism 
Awards][MEA Awards 2018 National Winner]


This message and any attachment is intended only for the use of the Addressee 
and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not 
the intended recipient, you are hereby notified that any dissemination of this 
communication is strictly prohibited. If you have received this communication 
in error, please delete all copies of the message and its attachments and 
notify the sender immediately. Thank you.
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Seeking feedback on tickets by Feb. 1

[Lara Friedman-Shedlov]

Re: 769:
If this is going to happen, I hope at the same time the issue with
scrolling of the main window (currently to the left of the navigation tree)
when in "Finding Aid View" in Firefox, which I reported about two years ago
and is still not fixed, can be resolved. Right now the scroll bar does not
work. The only option is to scroll with a mouse or other pointing device,
which is extremely slow.

In addition, it is very hard to resize the navigation tree in Firefox.
Clicking and dragging the left side of the window to make it bigger doesn't
work correctly.

/ Lara Friedman-Shedlov

_

Lara D. Friedman-Shedlov(She/Her/Hers)
Kautz Family YMCA Archives  | University of
Minnesota Libraries
l...@umn.edu |  612.626.7972 |

[image: www.facebook.com/IHRCA]   [image:
https://twitter.com/yarchives] 



> On Tue, Dec 17, 2019 at 8:01 AM Tang, Lydia  wrote:
>
>> Hello all!
>>
>>
>>
>> The Development Prioritization and Usability sub-teams have prepared a
>> brief list of tickets that we are seeking community feedback on!
>>
>>
>>
>> Please feel free to comment on these tickets and/or discuss them on the
>> list.  These tickets may be complex and/or have a high impact on the
>> program, so we definitely would appreciate your thoughts on these!
>>
>>
>>
>>- Geolocation: https://archivesspace.atlassian.net/browse/ANW-357
>>- Moving sidebar tree to the left:
>>https://archivesspace.atlassian.net/browse/ANW-769
>>- Downloading PDF from any view of the collection:
>>
>> https://archivesspace.atlassian.net/browse/ANW-773
>> 
>>
>> Thank you for your feedback and consideration!  We’ll send a reminder
>> after the new year, with the hope of finalizing feedback by the beginning
>> of February.
>>
>> Lydia Tang and Maggie Hughes
>>
>> ~ on behalf of the Development Prioritization and Usability subteams
>>
>>
>>
>>
>> ___
>> Archivesspace_Users_Group mailing list
>> Archivesspace_Users_Group@lyralists.lyrasis.org
>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>>
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>


-- 

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