Re: [Archivesspace_Users_Group] voting for ArchivesSpace Governance Board positions starts on June 8

[Christine Di Bella]

Hello Alan,

Most ArchivesSpace member institutions are listed on the Who’s Using 
ArchivesSpace?<https://archivesspace.org/community/whos-using-archivesspace> 
page on our website (a very limited number of member institutions choose not to 
be listed publicly). That page is grouped by membership level.

Invoices for annual membership fees and the information sheet an institution 
completes upon enrolling as a member also list an institution’s member level.

That should cover pretty much all bases, but people can, of course, always 
email the program team at 
archivesspaceh...@lyrasis.org<mailto:archivesspaceh...@lyrasis.org> if there 
are questions.

(tl;dr: State Library Victoria’s membership level is Medium. )

Christine

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Alan 
Manifold
Sent: Thursday, June 8, 2023 8:18 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] voting for ArchivesSpace Governance 
Board positions starts on June 8

Hi Christine (or anyone),
How do we know what size our institutions falls into? I’m sure we’ve seen this, 
but we don’t know offhand how to verify it.

Regards,
Alan Manifold





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<mailto:amanif...@slv.vic.gov.au>
slv.vic.gov.au<http://slv.vic.gov.au>

 [slv]
[https://www.slv.vic.gov.au/sites/default/files/email_signature/signature.jpg?9]<https://www.slv.vic.gov.au/email_campaign>



From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 On Behalf Of Christine Di Bella
Sent: Thursday, June 8, 2023 2:35 AM
To: Archivesspace Member Reps 
mailto:archivesspace_member_r...@lyralists.lyrasis.org>>;
 Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Cc: 
archivesspace_bot_memb...@lyralists.lyrasis.org<mailto:archivesspace_bot_memb...@lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] voting for ArchivesSpace Governance Board 
positions starts on June 8

Hello ArchivesSpace members,

Voting for the elections for the representatives to the ArchivesSpace 
Governance Board for the Very Small, Medium, and Large membership levels opens 
on June 8. Candidate statements for the people running for these positions are 
available at 
https://archivesspace.atlassian.net/wiki/spaces/ANC/pages/3361079318/Governance+Board+2023+Elections+-+Candidate+Statements.

Each member organization gets one vote in the election for the representative 
at their membership level. Only the Very Small, Medium, and Large level 
positions are up for election this year. The Voting Member we have on record 
for each eligible organization will receive an email with the ballot this week. 
If your organization is eligible and your Voting Member does not receive the 
ballot, or if your Voting Member has changed, please contact me at 
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>. Voting 
will close on June 22 at 9 p.m. Eastern Daylight Time.

Please note: if your organization is in the Very Large or Small levels your 
representative position is not up for election and you will not be voting this 
year.

A big thank you to all those who have volunteered to serve, and thanks in 
advance to everyone who votes. To learn more about ArchivesSpace governance, 
please visit https://archivesspace.org/governance-board-and-councils.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>

[cid:image001.jpg@01D99AA8.99A59850]

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

[Archivesspace_Users_Group] voting for ArchivesSpace Governance Board positions starts on June 8

[Christine Di Bella]

Hello ArchivesSpace members,

Voting for the elections for the representatives to the ArchivesSpace 
Governance Board for the Very Small, Medium, and Large membership levels opens 
on June 8. Candidate statements for the people running for these positions are 
available at 
https://archivesspace.atlassian.net/wiki/spaces/ANC/pages/3361079318/Governance+Board+2023+Elections+-+Candidate+Statements.

Each member organization gets one vote in the election for the representative 
at their membership level. Only the Very Small, Medium, and Large level 
positions are up for election this year. The Voting Member we have on record 
for each eligible organization will receive an email with the ballot this week. 
If your organization is eligible and your Voting Member does not receive the 
ballot, or if your Voting Member has changed, please contact me at 
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>. Voting 
will close on June 22 at 9 p.m. Eastern Daylight Time.

Please note: if your organization is in the Very Large or Small levels your 
representative position is not up for election and you will not be voting this 
year.

A big thank you to all those who have volunteered to serve, and thanks in 
advance to everyone who votes. To learn more about ArchivesSpace governance, 
please visit https://archivesspace.org/governance-board-and-councils.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>

[cid:image001.jpg@01D9979E.C392E030]

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

[Archivesspace_Users_Group] ArchivesSpace 3.4.0 now available

[Christine Di Bella]

Hello ArchivesSpace members,

ArchivesSpace is announcing the availability of v3.4.0. You can download it at 
https://github.com/archivesspace/archivesspace/releases/tag/v3.4.0.


This release includes many bug fixes and feature enhancements. Of particular 
note are some enhancements related to creating digital objects and making it 
easier to identify digital content for and in the public interface. The most 
complex work relates to new functionality using the previously unused Make 
Representative button. Based on a community-authored 
specification<https://docs.google.com/document/d/1-fi-1jpE7GqWc0zWxWsRO9zgRmR1vFFygp6jGnKh23k/edit?usp=sharing>,
 it is now possible to mark a particular file version on a digital object or 
digital object component for display on different types of records, including 
digital objects, digital object components, accessions, resources, and archival 
objects. Representative images also display in relevant browse and search 
result displays in the public and staff interface.

Other enhancements for digital objects include the option to set a preference 
to spawn description fields from the linked accession, resource or archival 
object record when creating digital object instances; a View Digital Material 
section added to the "pill" for resource records in the public interface when 
there is digital content within the resource; breadcrumbs that make the context 
for linked digital objects easier to see in result displays; and a more 
recognizable generic button for digital content when an image cannot be shown. 
New documentation written by the User Documentation sub-team for many of the 
new features, including Make Representative, is available in the user 
manual<https://archivesspace.atlassian.net/wiki/spaces/ArchivesSpaceUserManual/overview>.

Enhancements not related to digital objects but still significant include work 
submitted by Hudson Molonglo that it did for Princeton University to add local 
access restriction fields to the spreadsheet importers and RDE, and including 
URIs in EAD exports; more attractive print displays for records, including 
accessions; a new CSV import for standalone subjects; internal note fields for 
top containers and container profiles; and the elimination of a bug that caused 
hover text for the help center to sometimes appear at inopportune times.
Thanks to all of the community members who contributed code for this release: 
Andrew Morrison, Brian Harrington, Corey Schmidt, Dave Mayo, James Bullen, 
Jason Jordan, Jonathan Green, Joshua Shaw, Lora Woodford, Mark Triggs, Michael 
Glanznig, Nick Butler, and Payton Giles. As always, team members Brian Hoffman, 
Don Smith, Brian Zelip, and Mark Cooper, as well as contractor Manny Rodriguez, 
wrote and/or reviewed substantial code for the release. Thanks also to our 
community groups, especially the Testing sub-team, for their efforts.

More information about what's in the release and the link to download it are at 
https://github.com/archivesspace/archivesspace/releases/tag/v3.4.0. Information 
on upgrading to a new version of ArchivesSpace is available at 
https://archivesspace.github.io/tech-docs/administration/upgrading.html.

Due to the complex nature of some of the work in this release and the need for 
additional testing and refinement, this represents both the January and May 
releases from the 
roadmap<https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/3243245569/Roadmap+as+of+May+2023>.
 The next regular release of ArchivesSpace is projected for September.

Thanks as always for your support. If you have questions or need any assistance 
in upgrading, please let us know.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905


[ASpaceOrgHomeMedium]

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

[Archivesspace_Users_Group] changes related to ArchivesSpace community engagement staffing

[Christine Di Bella]

Hello ArchivesSpace members,

The two cornerstones of ArchivesSpace are software that meets user needs and 
strong community engagement. The continued robust backing of members and the 
support of the ArchivesSpace Governance Board have enabled us to shore up our 
staffing for development in recent years. With that side of our program in a 
stronger place than ever before, we are now able to turn attention to the other 
side of our team, and I am delighted to announce two recently approved changes 
related to our staffing for engagement.

Jessica Crouch has been an essential part of the ArchivesSpace team since 2019. 
In that time, she has led significant expansion in the depth and breadth of our 
engagement programming and important improvements in many of our activities 
that directly support ArchivesSpace's users, including working with community 
groups to reconceive how we deliver our Help Center and our training model. In 
recognition of her skills, experience and valuable perspective, we are shifting 
and refocusing some of her responsibilities to enable her to get more involved 
in areas that directly impact the application itself. Going forward, in 
addition to continuing to provide leadership for our engagement programming, 
Jessica will take an active role in shepherding select projects related to 
making the ArchivesSpace application better meet user needs in some specific 
areas, including broadening its utility for multi-lingual users and those 
outside the U.S. Jessica will move into this role as of July 1 and her new 
title will be Community Engagement Lead.


To enable Jessica to give fuller attention to her new responsibilities, we are 
also adding a part-time Program Assistant to provide administrative support for 
activities that engage users across the ArchivesSpace community, with a 
particular focus on events management and communications. The person in this 
role will work under my direct supervision but in close collaboration with 
Jessica and others at Lyrasis and in the larger ArchivesSpace community. I'll 
send more information and the listing for this new position in a separate email.



Please join me in congratulating Jessica on her well-deserved promotion and in 
looking forward to the small increase in our ranks later this summer. Thank you 
for all the support that you as members provide in making things like this 
possible so that we can better support you.



Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>

[cid:image001.jpg@01D98C89.A45E1E20]

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

[Archivesspace_Users_Group] release candidate available - ArchivesSpace v3.4.0-RC1

[Christine Di Bella]

Hello ArchivesSpace members,

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

This release candidate includes many bug fixes and feature enhancements. Of 
particular note are enhancements related to creating digital objects and making 
it easier to identify digital content for and in the public interface. The most 
complex work relates to new functionality using the previously unused Make 
Representative button. Based on a community-authored 
specification<https://docs.google.com/document/d/1-fi-1jpE7GqWc0zWxWsRO9zgRmR1vFFygp6jGnKh23k/edit?usp=sharing>,
 it is now possible to mark a particular file version on a digital object or 
digital object component for display on different types of records, including 
digital objects, digital object components, accessions, resources, and archival 
objects. Representative images also display in relevant browse and search 
result displays in the public and staff interface. Draft 
documentation<https://docs.google.com/document/d/1yO8dM0o54GhIrY0ZdzNOXjSR25dt7r0WSwGUNC1rPxU/edit?usp=sharing>
 for how to use this functionality is available for reference and comment.

Other enhancements for digital objects include the option to set a preference 
to spawn description fields from the linked accession, resource or archival 
object record when creating digital object instances; a View Digital Material 
section added to the "pill" for resource records in the public interface when 
there is digital content within the resource; breadcrumbs that make the context 
for linked digital objects easier to see in result displays; and a more 
recognizable generic button for digital content when an image cannot be shown.

Enhancements not related to digital objects but still significant include work 
submitted by Hudson Molonglo that it did for Princeton University to add local 
access restriction fields to the spreadsheet importers and RDE, and include 
URIs in EAD exports; more attractive print displays for records, including 
accessions; a new CSV import for standalone subjects; internal note fields for 
top containers and container profiles; and the elimination of a bug that caused 
hover text for the Help Center to sometimes appear at inopportune times.

A particular thanks to our Testing sub-team for their work testing individual 
JIRAs, the Make Representative functionality, and doing regression testing 
across the application. Additional thanks to our User Documentation sub-team 
for their feedback on the Make Representative functionality.

Because of the potential impact of the Make Representative functionality and 
other features related to digital objects, we highly encourage you to test this 
release candidate with your own data if you can. We will be holding the 
feedback period open for longer than usual as a result. Please send us comments 
or questions at 
archivesspaceh...@lyrasis.org<mailto:archivesspaceh...@lyrasis.org> by May 15.

Based on the results of this feedback period, we will determine when to release 
the production version of 3.4.0.

Please get in touch if you have any questions. Thanks as always for your 
feedback and support.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>

[cid:image001.jpg@01D9794D.67DC3DF0]

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

Re: [Archivesspace_Users_Group] Digital Objects: mailto in the File URI field?

[Christine Di Bella]

Hello Mark,

There are changes coming to how File Versions display in the public interface 
in the next version of ArchivesSpace, so I would recommend checking those out 
before making changes across all of your records. That said, it may be better 
anyways to use a plugin or some other way to direct people to a single 
destination for your digital objects, rather than use that field in a way 
that's not its intent. Do you need published File Versions for these records at 
all? Maybe the published Digital Object record itself is sufficient for your 
purposes, with a more prominent note with the contact information.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org


-Original Message-
From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Hand, 
Sarit
Sent: Monday, March 27, 2023 9:49 AM
To: mcy...@jhu.edu; Archivesspace Users Group 

Subject: Re: [Archivesspace_Users_Group] Digital Objects: mailto in the File 
URI field?

Hi Mark,

I am not an expert on HTML coding... but out of curiosity, I tried adding a 
mailto link in the fil version as well as in a note field.

I could not get the mailto to work in the file version either, but I was able 
to make it work in a notes field. But since you are concerned about the 
visibility of the notes field...

Short of messing around with the PUI layout etc. can you have a static website 
page with the mailto link and other information regarding accessing digital 
assets and use the URL to that page in the file version for all the digital 
objects? Use the caption field on the file version record to put whatever text 
you want the "button" to say.

Does that make sense?

Cheers,



Sarit Hand
Digital Archivist
AP Corporate Archives
200 Liberty Street
New York, NY 10281
T 212.621.7035

sh...@ap.org
ap.org



-Original Message-
From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Mark 
Cyzyk
Sent: Friday, March 24, 2023 4:04 PM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] Digital Objects: mailto in the File URI 
field?

[EXTERNAL]

All,

I have a question:

Rather than a link to a File URI for Digital Objects, we'd just like to have 
some kind of Notice (exactly similar to the red box/button that pops up for 
File URIs) rendering a single "mailto:; link. Is there a way to do this? That 
File URI field does not accept mailto links, otherwise we'd just put our 
mailto's there.

We tried putting something in the Notes field, but are afraid it's too far 
Below The Fold for such a notice.

Advice appreciated,

Mark

--
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
Mark Cyzyk, M.A., M.L.S.
Library Applications Group
The Sheridan Libraries
The Johns Hopkins University
mcy...@jhu.edu

Verba volant, scripta manent.

___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group=05%7C01%7Cshand%40ap.org%7Cdaee60c6121d4efc4fc308db2ca2f0d4%7Ce442e1abfd6b4ba3abf3b020eb50df37%7C1%7C0%7C638152850561923147%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=qafVShAS2yoroPKEX9qMfIpXltRo9YRLO%2F%2F3jHikhv4%3D=0
The information contained in this communication is intended for the use of the 
designated recipients named above. If the reader of this communication is not 
the intended recipient, you are hereby notified that you have received this 
communication in error, and that any review, dissemination, distribution or 
copying of this communication is strictly prohibited. If you have received this 
communication in error, please notify The Associated Press immediately by 
telephone at +1-212-621-1500 and delete this email. Thank you.
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] File versions not appearing in reports

[Christine Di Bella]

Hello Sara,

I think you're encountering this bug which is being worked on for the next 
release: https://archivesspace.atlassian.net/browse/ANW-1526. The fix is up on 
our test server at https://test.archivesspace.org/staff. Though you won't be 
able to try it with your own data there (unless you import it), you could take 
a look to see if the results for digital objects are more what you'd expect. 
It'd be great if you'd comment on the issue if you test it and find something 
different.

Thanks,
Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905

[ASpaceOrgHomeMedium]


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Szakaly, 
Sara J - APHIS
Sent: Tuesday, December 20, 2022 12:56 PM
To: archivesspace_users_group@lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] File versions not appearing in reports

Hello all,

When running reports, both custom and the built-in file version list report, I 
cannot get digital object file versions to appear in the report. The field is 
just blank.  Other linked records such as dates appear as expected.

File versions do appear in digital object component reports though.

I've tried in both our instance and in the ArchivesSpace sandbox. We currently 
have v3.3.1, and I was experiencing the same issue in our previous version 
(v3.2.0)

Am I misunderstanding something? Any help would be appreciated, thanks!

[https://www.aphis.usda.gov/js/USDA-Logo.jpg]
  Sara Szakaly, MLS
  Archivist & Records Manager
  APHIS Wildlife Services (WS)
  National Wildlife Research Center
  4101 Laporte Ave
  Fort Collins, CO 80521
  P: 970-266-6021
  sara.j.szak...@usda.gov<mailto:sara.j.szak...@usda.gov>
In office: M, W, Th | Telework: Tu, F






This electronic message contains information generated by the USDA solely for 
the intended recipients. Any unauthorized interception of this message or the 
use or disclosure of the information it contains may violate the law and 
subject the violator to civil or criminal penalties. If you believe you have 
received this message in error, please notify the sender and delete the email 
immediately.
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] updated ArchivesSpace roadmap

[Christine Di Bella]

Hello ArchivesSpace members,

Now that we have a full development team again, we have updated the development 
roadmap<https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/3243245569/Roadmap+as+of+December+2022>
 to reflect planned work for the next year. A few notes:


  *   We aim for three regular releases per year. If urgent updates are needed 
in between releases, we may put out additional releases. In calendar year 2023, 
we are projecting releases in January 2023, May 2023, and September 2023.


  *   The scheduled work is intended to match community user-facing priorities 
for the application with development capacity, while keeping in mind the 
ongoing need to maintain technical infrastructure and pay down technical debt. 
Some community priorities have not been scheduled at this time, but may be if 
additional resources or community partners become available.


  *   The roadmap provides high-level descriptions of development projects that 
are either underway already or planned for the future. When the work for a 
project has been delivered, fully tested, and deemed satisfactory it goes into 
the next regular release. If work is not ready by the scheduled time of the 
regular release it is usually moved to a future release. The release notes that 
accompany each release contain much more granular description of individual bug 
fixes and new features, as well as infrastructure work and refactoring, that 
are in the release.


  *   While there have been many twists and turns over the last three years, we 
aim to update the roadmap after each release. We are hopeful that this will be 
more predictable in 2023.


Thank you for all the community participation in identifying needs for the 
application and writing specifications, as well as your involvement in all 
stages of the development cycle, especially prioritization and testing, . 
Having a community that really cares, and puts its actual and proverbial money 
where its mouth is, is so important in sustaining ArchivesSpace. If you have 
questions about the roadmap or individual projects, please let me know.

Best,
Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905

[ASpaceOrgHomeMedium]

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

Re: [Archivesspace_Users_Group] Validation error: missing dates of existence label field

[Christine Di Bella]

Hello Sarah,

Because being unable to validate agent records with dates of existence is not 
happening across the board, this sounds like an issue with your upgrade or 
possibly with a plugin you're running and how it interacts with 3.2.0. There 
were quite a few changes to the translations files between the version you 
moved from and the version you moved to. Depending on whether your translation 
files were customized before for earlier versions of ArchivesSpace, it's 
possible that not all the new or changed values were applied in the upgrade. 
Our tech folks should be able to help you sort that out.

Of course, if others are experiencing this issue, please let us know. But I'm 
going to put a technical support ticket in for you on this, and you'll see 
another message directly to you about that in a little bit.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905

[ASpaceOrgHomeMedium]



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Tester, 
Sarah
Sent: Wednesday, October 12, 2022 4:49 PM
To: archivesspace_users_group@lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Validation error: missing dates of 
existence label field

Kia ora all

As part of our upgrade from v2.8.0 to v.3.2.0 we have discovered that there is 
a missing Dates of Existence Label field when creating an Agent record. As this 
field is missing, when dates are entered we get a Validation error on saving 
the record.

Our developers have posted the issue to GitHub but we haven't had any response 
to this yet. Is this something anyone on this list has come across?

https://github.com/archivesspace/archivesspace/issues/2833

Cheers

Sarah

Sarah Tester (she/her)
Community Stories Liaison
Digital Content



[cid:image003.png@01D8DE68.3F1BA110]
03 367 9963 
[cid:image004.png@01D8DE68.3F1BA110]
sarah.tes...@ccc.govt.nz<mailto:%20sarah.tes...@ccc.govt.nz>
[cid:image005.png@01D8DE68.3F1BA110]
Library 180 Smith Street, 180 Smith Street, Christchurch
[cid:image006.png@01D8DE68.3F1BA110]
PO Box 73045, Christchurch 8154
[cid:image007.png@01D8DE68.3F1BA110]
ccc.govt.nz<http://ccc.govt.nz/>


[cid:image008.png@01D8DE68.3F1BA110]



**
This electronic email and any files transmitted with it are intended
solely for the use of the individual or entity to whom they are addressed.

The views expressed in this message are those of the individual sender
and may not necessarily reflect the views of the Christchurch City Council.
If you are not the correct recipient of this email please advise the
sender and delete.
Christchurch City Council
http://www.ccc.govt.nz
**
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] different date models for Agents vs Accessions, Resources, Archival Objects?

[Christine Di Bella]

Hello Ron,

The divergence of the two date models within ArchivesSpace did come about with 
the work on the Agents module. While the plan is to eventually move other 
record types for which it makes sense to the same model (there are some related 
requests at https://archivesspace.atlassian.net/browse/ANW-1475 and 
https://archivesspace.atlassian.net/browse/ANW-380), because dates are so 
complex and because the agents work was underway already, we treated the work 
on dates associated with agents as a first step. The motivation for the change 
was specific to the EAC-CPF standard, though it has broader applicability with 
EAD as well.

I don’t have a specific timeframe for moving other dates in the application to 
this model right now. One of our thoughts in staging this date transition was 
that we wanted to get feedback on the agents dates piece before taking the even 
larger step of moving the other record types (and migrating the associated 
data) to that model. We haven’t received much feedback on the agents yet, 
possibly because a lot of people haven’t upgraded to a 3.x version yet or 
possibly because the new date model meets their needs just fine. We are 
currently reviewing prioritized projects against capacity in light of staffing 
changes and I intend to share more information and an updated roadmap soon.

I hope that helps. If you have other questions, or if anyone here has 
background or feedback specific to the agents date model, we’d be glad to have 
them.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905

[ASpaceOrgHomeMedium]



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Ron Van 
den Branden
Sent: Wednesday, October 5, 2022 9:56 AM
To: archivesspace_users_group@lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] different date models for Agents vs 
Accessions, Resources, Archival Objects?

Hi,

I'm wondering why different date models exist for different record types in 
ArchivesSpace:


  *   Accessions + Resources/Archival Objects:
 *   Date Certainty: general certainty qualifier: "Approximate", 
"Inferred", "Questionable"
  *   Agents:
 *   Date Certainty: general certainty qualifier: "Approximate", 
"Inferred", "Questionable"
 *   Standardized Date Type: specific qualifier for both Begin and End 
date: "Standard", "Not Before", "Not After"

The extra field Standardized Date Type is occurring consistently for all date 
fields in the Agents module.

This raises some questions:


  *   What's the motivation for this difference? Is it standards-based, and 
does EAC-CPF allow for more detail than EAD? Or is is because the Agents module 
has been reworked more recently?
  *   In the latter case, is any harmonization foreseen for the date fields in 
Accessions and Resources/Archival Objects? If so, is there a time frame?

Many thanks for your thoughts!

Best,

Ron

Ron Van den Branden | functioneel analist - applicatiebeheerder Letterenhuis
Stad Antwerpen | Talentontwikkeling en Vrijetijdsbeleving |  Musea en Erfgoed
Minderbroedersstraat 22, 2000 Antwerpen
✉ Grote Markt 1, 2000 Antwerpen
gsm +32 0485 02 80 50 | tel. +32 3 222 93 30
letterenhuis.be<http://www.letterenhuis.be/> | 
instagram<https://www.instagram.com/letterenhuis/> | 
facebook<https://www.facebook.com/Letterenhuis>

Proclaimer
Vergissen is menselijk. Dus als deze e-mail, samen met eventuele bijlagen, niet 
voor u bestemd is, vragen we u vriendelijk om dat te melden aan de afzender. 
Deze e-mail en de bijlagen zijn namelijk officiële documenten van de stad 
Antwerpen. Ze kunnen vertrouwelijke of persoonlijke informatie bevatten. Als 
stad nemen we privacy heel serieus en willen we als een goede huisvader waken 
over de vertrouwelijkheid van documenten. Als u dit bericht per vergissing hebt 
ontvangen of ergens hebt gevonden, wees dan zo eerlijk om het meteen te 
verwijderen en het niet verder te verspreiden of te kopiëren.


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

[Archivesspace_Users_Group] ArchivesSpace 3.3.1 now available

[Christine Di Bella]

Hello ArchivesSpace members,

ArchivesSpace 3.3.1 is now available. This patch release fixes a bug when using 
default values that was introduced by 3.3.0 and adds some missing labels. 
People who haven't already upgraded to 3.3.0 should go directly to this release 
when they do upgrade, and we recommend upgrading to 3.3.1 if you have already 
upgraded to 3.3.0 and use or plan to use default values for record creation.

More information about what's in the release and the link to download it are at 
https://github.com/archivesspace/archivesspace/releases/tag/v3.3.1. Information 
on upgrading to a new version of ArchivesSpace is available at 
https://archivesspace.github.io/tech-docs/administration/upgrading.html.

If you have questions or need any assistance, please let us know. A special 
thanks to our Registered Service Providers Atlas Systems for identifying the 
default values issue and LYRASIS Digital Technology Services for the quick 
submission of a fix to it.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905


[ASpaceOrgHomeMedium]

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

Re: [Archivesspace_Users_Group] MY SQL not set up right

[Christine Di Bella]

Hi Kristine,

I’m going to put a tech support ticket in for you on this to get help 
completing your installation. You’ll see a separate message directly to you 
about that.

The embedded database is for testing purposes only and it’s a bad idea to put 
anything you want to keep in it. The migration from that database to MySQL is 
not particularly easy, so it’s much better to nip this in the bud and get set 
up with MySQL correctly before entering any data.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905

[ASpaceOrgHomeMedium]


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Kristine 
Allegretti
Sent: Thursday, September 22, 2022 10:01 AM
To: archivesspace_users_group@lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] MY SQL not set up right

Hello,
It looks like our MYSQL is not set up right to back up archivesspace because 
whenever we sign on it says we are using apache derby. Does anyone know if 
there is a way to set up MYSQL after we have already entered things into 
archivesspace? Will it mess anything up?

Thanks.


--
Kristine Allegretti (She/Her/Hers)
Director of Operations and Collections
Alice Austen House
2 Hylan Boulevard
Staten Island, NY 10305
(718) 816-4506 x 10
www.aliceausten.org<http://www.aliceausten.org/>
[https://ci3.googleusercontent.com/mail-sig/AIorK4xfMqgIXgjBArDfgTNaeoyaRuLz2C8xZDHIQGbIxzvKWKj427gFbvvo0xTFPgDRu-aG-3aj-mM]





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

[Archivesspace_Users_Group] ArchivesSpace 3.3.0 now available

[Christine Di Bella]

Hello ArchivesSpace members,

ArchivesSpace is announcing the availability of v3.3.0. You can download it at 
https://github.com/archivesspace/archivesspace/releases/tag/v3.3.0.

This release includes many small bug fixes and feature enhancements, including 
some enhancements to spawning from accessions and an option for logged in users 
to change their own passwords. As part of the spawning improvements, the plugin 
Hudson Molonglo developed for The New School Archives and Special Collections 
to link accessions to archival objects has been incorporated into the core code 
of ArchivesSpace.

Thanks to all of the community members who contributed code for this release: 
Andrew Morrison, Corey Schmidt, Greg Wiedeman, Jacob Shelby, James Bullen, 
Jason Jordan, Joshua Shaw, Lora Woodford, Mark Triggs, and Michael Glanznig. As 
always, program team members Brian Hoffman, Don Smith, and Mark Cooper, as well 
as contractors Manny Rodriguez, Brian Zelip, and Don Richards, wrote and/or 
reviewed substantial code for the release. Thanks also to our community groups, 
especially the Testing sub-team, for their efforts.

More information about what's in the release and the link to download it are at 
https://github.com/archivesspace/archivesspace/releases/tag/v3.3.0. Information 
on upgrading to a new version of ArchivesSpace is available at 
https://archivesspace.github.io/tech-docs/administration/upgrading.html.

This is the release from the 
roadmap<https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/2634973195/Roadmap+as+of+January+2022>
 that was originally projected for May. Due to staffing changes we are 
currently putting together the updated roadmap and projections for releases for 
the rest of 2022 and calendar year 2023. More information will be available 
soon.

Thanks as always for your support. If you have questions or need any assistance 
in upgrading, please let us know.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905


[ASpaceOrgHomeMedium]

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

[Archivesspace_Users_Group] release candidate available - ArchivesSpace v3.3.0-RC1

[Christine Di Bella]

Hello ArchivesSpace members,

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

This release candidate includes many small bug fixes and feature enhancements. 
Of particular note are some enhancements to spawning from accessions and an 
option for logged in users to change their own passwords. As part of the 
spawning improvements, the plugin Hudson Molonglo developed for The New School 
Archives and Special Collections<https://github.com/hudmol/as_accession_links> 
to link accessions to archival objects has been incorporated into the core code 
of ArchivesSpace.

A particular thanks to our Testing sub-team for their work testing individual 
JIRAs and doing regression testing across the application.

Please try this release candidate out and let us know at 
archivesspaceh...@lyrasis.org<mailto:archivesspaceh...@lyrasis.org> by August 
29 if you notice any problems with the specific areas addressed in this 
release, or if anything that was working before no longer is. Pending the 
results of this testing, we will aim to release the production version of 3.3.0 
shortly afterwards.

Please get in touch if you have any questions. Thanks as always for your 
feedback and support.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905

[ASpaceOrgHomeMedium]


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

Re: [Archivesspace_Users_Group] Guidance for Human Readable URLs

[Christine Di Bella]

Hello Brian,

Have you looked at the user manual section on this feature: 
https://archivesspace.atlassian.net/wiki/spaces/ArchivesSpaceUserManual/pages/890208314/Human-Readable+URLs?
 If not, that would be a good place to start for an overview.

Hopefully some folks on here can give more advice from the point of view of 
actual implementations.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905

[ASpaceOrgHomeMedium]



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Duckett, 
Brian (NIH/NLM) [C]
Sent: Tuesday, July 26, 2022 2:03 PM
To: archivesspace_users_group@lyralists.lyrasis.org
Cc: Liu, Steve (NIH/NLM) [C] ; Whitaker, John (NIH/NLM) [C] 
; Kalyanasundaram, Sriram (NIH/NLM) [C] 

Subject: [Archivesspace_Users_Group] Guidance for Human Readable URLs

Hello,

We are requesting guidance on how to implement human readable URLs in the 
ArchivesSpace application.

Our production instance supports this to an extent. For example, the following 
listed URL is a "human readable" URL for the standard ArchivesSpace URL 
https://archivesspace.nlm.nih.gov/repositories/4/resources/968


  *   https://archivesspace.nlm.nih.gov/repositories/ammp/resources/__101576736

We would like to implement this naming standard across all public facing links. 
Guidance on integrating this implementation for search would also be highly 
appreciated.

Thank You,
Brian
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] reminder: ArchivesSpace Front End Developer - Position Announcement (remote)

[Christine Di Bella]

Hello ArchivesSpace members,

Just a reminder that the priority deadline for our new Front End Developer 
position is this Friday, July 15. If you know of someone who is interested, or 
if you're interested yourself, we encourage you to apply by then.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905

[ASpaceOrgHomeMedium]




LYRASIS is seeking a detail-oriented and collaborative individual to serve as 
the ArchivesSpace Front End Developer and work with a team to maintain and 
improve the ArchivesSpace software application.
The ArchivesSpace Front End Developer is primarily responsible for implementing 
features and fixing bugs identified and prioritized by the ArchivesSpace 
community of users, with modest responsibility for monitoring the application 
stack for possible updating to new technologies. They will work in 
collaboration with others including the ArchivesSpace Technical Lead and others 
on the Program Team, code committers, the Technical Advisory Council (TAC), and 
LYRASIS IT staff.
Duties/Job Responsibilities:
Software Development

  *   Front end development
  *   Implement feature requests, bug fixes, and application updates under the 
guidance of the ArchivesSpace Technical Lead / Program Manager / ArchivesSpace 
Community
  *   Ensure the application's code base has a robust test suite and thorough 
testing coverage
  *   Document feature requests and bug fixes; provide application support 
where necessary
Application / Community Support

  *   Contribute to technical documentation of the application
  *   Provide occasional technical support to ArchivesSpace users as requested
  *   Serve as program liaison to certain Technical Advisory Council sub-teams
  *   Depending on interest, occasionally represent the ArchivesSpace 
application at technical conferences such as Code4Lib
Skills and Qualifications:

  *   Experience developing Ruby on Rails applications and familiarity with 
REST APIs.
  *   Experience with frontend development in HTML5, CSS, and JavaScript, using 
JQuery and Twitter Bootstrap or similar frameworks, with a strong understanding 
of Web standards, accessibility, and usability
  *   Experience upgrading CSS / JS and refactoring legacy CSS / JS into 
cleaner implementations
  *   Experience with NodeJS, NPM, and one or more modern Javascript frameworks 
(Stimulus preferred)
  *   Experience testing software applications on a broad range of browsers and 
browser versions as part of the application development process and when 
troubleshooting problems experienced by end-users
  *   Knowledge of best practices in test-driven development, using RSpec, 
Selenium, static analysis and code coverage tools, and continuous integration
  *   Experience using Git and GitHub for version control and release management
  *   Familiarity with agile development methodologies
  *   Commitment to writing clear, well-documented, reusable code
  *   Ability to work well in a distributed team environment with modest 
direction
  *   Effective time and project management skills
  *   Excellent communication skills
  *   Three to five years of relative work experience
  *   Willingness to travel to conferences and meetings on occasion
Preferred Qualifications

  *   Experience in application and web service development for libraries, 
archives, and digital collections
  *   Experience with Apache Solr for search and indexing platforms
  *   Experience with XML-based library and archives metadata standards, 
including Encoded Archival Description (EAD), MARCXML, MODS, Dublin Core, and 
METS, as well as XSLT stylesheets associated with their transformation
  *   Knowledge of and experience with archival management systems including 
ArchivesSpace, Archivists' Toolkit, or Archon
Salary is commensurate with skills and experience; base salary is $ 83,600- $ 
97,600
The position is part of a geographically and institutionally distributed team, 
and, as such, applications from candidates interested in telecommuting are 
welcome.
You should apply even if you don't feel that your credentials are a 100% match 
with the position description. We are looking for relevant skills and 
experience, not a checklist that exactly matches the position itself.


To Apply: All applications MUST be submitted with a cover letter for 
consideration
Applications are accepted until the position is filled but the review of 
applications will begin on July 15th.
You can view the announcement & apply online at: 
https://lyrasis.isolvedhire.com/jobs

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

Re: [Archivesspace_Users_Group] Still unable to launch ArchivesSpaceService. Please help

[Christine Di Bella]

Hello Ivan,

We'll put a technical support ticket in for you on this. You'll see another 
email about that directly to you in a minute.

(Just as a reminder to everyone, our procedure for technical support for 
members is listed at https://archivesspace.org/member-area/technical-support. 
We always encourage you to start with the listserv, but if the answer does not 
come, or if you can tell from the start that your issue needs more 
individualized attention, please email the team at 
archivesspaceh...@lyrasis.org<mailto:archivesspaceh...@lyrasis.org>.)

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905

[ASpaceOrgHomeMedium]



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of 
Allhiser, Ivan
Sent: Thursday, June 2, 2022 9:13 AM
To: archivesspace_users_group@lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Still unable to launch 
ArchivesSpaceService. Please help

Hello all,

I have yet to hear back or find anything to fix this issue. I am still unable 
to start the ArchivesSpaceService.

"Our previous system administrator set up ArchivesSpace 2.8.1 and we received a 
ticket that it needed to be re-indexed. None of us were even aware of what this 
server did. Before I could access it, the server needed to be rebooted. Once it 
came back up, I was unable to start the ArchivesSpaceServe. I am shown this 
error whenever I try (even with Powershell)

"Windows could not start the ArchivesSpaceService on Local Computer. For more 
information, review the System Event Log. If this is a non-Microsoft service, 
contact the service vendor, and refer to service-specific error code 5."

I've checked the System Event Long and I don't even see any events that show an 
attempt to start the service. We've checked the logs and honestly, I'm lost 
trying to swim through all this data. I don't see anything standing out that 
says there's an error. Has anyone encountered this before and know of a fix?"

Thank you for your time,
Ivan Allhiser
System Administrator
Information Technology Services
Ph (816) 501-3695
[Dining Services | Avila University]

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

[Archivesspace_Users_Group] Take a Break with ArchivesSpace on Friday

[Christine Di Bella]

Dear ArchivesSpace users,


After a one-week hiatus, our Friday break call returns this week. These casual 
open calls take place on zoom at 12pm ET on Fridays and don't have agendas or 
presentations. They're just an opportunity to connect, chat and recharge. Use 
this as a time to get help or talk about ArchivesSpace (or anything else) in an 
informal setting or have a beverage with other ArchivesSpace users during this 
stressful time.


Whether you can attend once or plan to be there every Friday, these calls are 
open to everyone but registration is required to join.


Register once to join any open call at 
https://lyrasis.zoom.us/meeting/register/tZcldOGuqjotE9cNSaa6j45issVCKrEQKQYv


We seek to provide a welcoming, fun, and safe community experience for 
everyone. The full text of the code of conduct is available at 
https://archivesspace.org/archivesspace-code-of-conduct.


Please email 
archivesspaceh...@lyrasis.org<mailto:archivesspaceh...@lyrasis.org> with any 
questions.
We hope to see you tomorrow!
Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905


[ASpaceOrgHomeMedium]



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

[Archivesspace_Users_Group] no Take a Break with ArchivesSpace on May 6

[Christine Di Bella]

Due to other staff commitments, ArchivesSpace will not be hosting a Friday 
break this week. (Though we encourage you to take your own break!) We plan to 
resume on Friday, May 13.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905


[ASpaceOrgHomeMedium]


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

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

[Christine Di Bella]

Hello everyone,

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

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

There is a section on Rights Statements in the User Manual (which lives at 
https://archivesspace.atlassian.net/wiki/spaces/ArchivesSpaceUserManual/pages/909934631/ArchivesSpace+User+Manual).
 Please note that the instructions for rights statements there suggest that 
people supplement them with Conditions Governing Access or Conditions Governing 
Use notes.

Rights Statements were significantly expanded in 2017 (for version 
2.1.0<https://github.com/archivesspace/archivesspace/releases/tag/v2.1.0>) 
courtesy of a community-authored and vetted specification (attached to 
https://archivesspace.atlassian.net/browse/ANW-123). There are some user 
stories included with it. That specification did not include a request for 
rights statements to appear in the public interface (possibly because it 
preceded the “new” public interface).

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

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

If folks are interested, the energy here might be well harnessed into working 
on hammering out those details. It would be wonderful to move this forward if 
there is this level of interest. If someone wants to take the lead on that and 
needs help getting started, please let me know.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905


[ASpaceOrgHomeMedium]



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Bowers, 
Kate A.
Sent: Thursday, March 24, 2022 4:53 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Rights statements not showing up in 
the public interface

Thanks, Maureen, for making this distinction really clear!

Do you know of any documentation (official AS or other) that explains the uses 
for which Rights Statements were intended?

Many folks are confusing “rights statements” which are meant for use in digital 
preservation environments with access and use restriction notes which are for 
humans. I would love to be able to point people to a better explanation than I 
can give off the cuff..

Thanks!

Kate

From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 On Behalf Of Dean DeBolt
Sent: Thursday, March 24, 2022 4:34 PM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Rights statements not showing up in 
the public interface

I'm not sure that I understand Maureen's  comment.  I just want the ability to 
change
the text on the home screen of the PUI to be able to add a 'harmful' caution 
statement.

Dean


Dean DeBolt, University Librarian (Professor)/University Archivist
UWF Archives and West Florida History Center
University of West Florida Library
11000 University Parkway
Pensacola, FL  32514-5750
ddeb...@uwf.edu<mailto:ddeb...@uwf.edu>;   850-474-2213

West Florida History Center is the largest and most comprehensive
history collection about Pensacola and the West Florida region.
http://libguides.uwf.edu/universityarchives<https://urldefense.proofpoint.com/v2/url?u=http-3A__libguides.uwf.edu_universityarchives=DwMFaQ=WO-RGvefibhHBZq3fL85hQ=wwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY=hxkauW8ve0z-LwMUn94uZ_k0X3hHrZbJbJQrubvDqz0ZhFs7nt0FTvj89q7hBvGb=MPoHjB_uy_5qAulPF5ubyIOlv0G6ZKB-au7pQ9VdnIA=>

Digital collections can be found at:  http://uwf.lyrasistechnology.org 
<https://urldefense.proofpoint.com/v2/url?u=http-3A__archives.uwf.edu_=DwMFaQ=WO-RGvefibhHBZq3fL85hQ=wwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY=hxkauW8ve0z-LwMUn94uZ_k0X3hHrZbJbJQrubvDqz0ZhFs7nt0FTvj89q7hBvGb=mYZzeTUzVpZrlDMK4cqR25FQ1ZLO-6J5b7y0jdEXRa0=>
and 
http://uwf.digital.flvc.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__uwf.digital.flvc.org=DwMFaQ=WO-RGvefibhHBZq3fL85hQ=wwc_Z_TbmWbPFh7My2zRxmrGgCNO-71Fwzlmd8YZVUY=hxkauW8ve0z-LwMUn94uZ_k0X3hHrZbJbJQrubvDqz0ZhFs7nt0FTvj89q7hBvGb=4UM4U1bdl8Xl5v_fWTikPIt0N1IWY7vkLkz4JHgbPbw=>

If we've been of service, please let us know or our administration,
Dean of Libra

Re: [Archivesspace_Users_Group] Jetty out of date - critical vulnerability

[Christine Di Bella]

Hello everyone,

Our policy for reporting security issues is at archivesspace/SECURITY.md at 
master * 
archivesspace/archivesspace<https://github.com/archivesspace/archivesspace/blob/master/SECURITY.md>
 . Given the sensitivity, we maintain security issues in a non-public JIRA. 
When you encounter issues locally, please do reach out to us at 
archivesspaceh...@lyrasis.org<mailto:archivesspaceh...@lyrasis.org> first so 
that we can discuss it with you.

We're currently investigating this issue. ArchivesSpace has many dependencies 
built into it, which can make upgrading individual pieces more complex than it 
might otherwise be. The timing for upgrades is always dependent on matching our 
available resources with the community's highest priorities, while taking care 
of infrastructure items and dependencies with the highest urgency as quickly as 
possible. Jetty is used in a relatively limited way in ArchivesSpace, as it is 
not the primary web server for most people using the application, which has, in 
the past, made upgrading it less time sensitive than it might otherwise be. We 
will review all new information, however, to determine if circumstances have 
changed. We'll have an update on this soon.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905


[ASpaceOrgHomeMedium]





From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Shalvi, 
Doron (NIH/NLM) [C]
Sent: Monday, October 25, 2021 11:14 AM
To: archivesspace_users_group@lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Jetty out of date - critical vulnerability

Hello,

I wanted to pass on to the community some critical security vulnerabilities 
that we recently found when scanning our ArchivesSpace instance.  These 
vulnerabilities allows authorization to be bypassed, due to the out of date 
version of Jetty delivered with the system.  I've written up these issues as a 
JIRA ticket at: https://archivesspace.atlassian.net/browse/ANW-1437, but also 
wanted to post about the issue here to allow for discussion.

We are hoping to soon open our ArchivesSpace instance to the general public.  
Our security team will not allow ArchivesSpace to be opened to the public while 
it has a critical security vulnerability.

We are running ArchivesSpace 2.8.1, which uses Jetty 8.1.5.  However, since all 
recent versions of ArchivesSpace use the same version of Jetty, I assume that 
all recent versions of ArchivesSpace are affected as well, including recent 
version 3.1.  Version 8 of Jetty is considered "venerable" (older even than 
deprecated), as noted at https://www.eclipse.org/jetty/download.php .  With 
this version of Jetty, NetSparker noted 2 critical issues, 3 high issues, 1 
medium issue, and 1 low issue.

These issues were found by NetSparker, which is one of the security tools we 
use for scanning.  Interestingly, this issue was found by NetSparker only a few 
weeks ago, and not in our previous NetSparker scans, even though our 
ArchivesSpace instance has not changed.  This implies that the issue was just 
recently added to NetSparker's vulnerability database, may become more 
well-known, and could present an issue to other organizations using 
ArchivesSpace as well.

I understand that ArchivesSpace does not heavily use Jetty, and does not serve 
any static content using Jetty.  However, Jetty can still be exploited even if 
it is behind an intermediary, such as Apache, as described in the links in the 
ticket.  We have spent a little bit of time attempting to upgrade Jetty on our 
own.  We were able to upgrade to Jetty 9.4, but this version is still 
vulnerable to the issues noted above.  We weren't able to upgrade to Jetty 10 
or 11, both of which require Java 11 - it looks like this may take some work.

Has anyone else observed these issue?  Would anyone have suggestions for 
remediation?

I think that the best approach would be to upgrade Jetty to version 10 or 11, 
in line with a move to Java 11.

Thanks for your thoughts and consideration!

Doron Shalvi
System Engineer
National Library of Medicine

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

Re: [Archivesspace_Users_Group] Developing custom reports

[Christine Di Bella]

Thanks for the feedback, Wendy. I think the issue you’re pointing out is one of 
terminology when there is a value with a Boolean like Publish. You can choose 
to display these, and you can choose to narrow by a value or Yes, a value of 
No, or no value at all. You are correct that the blank option would be the one 
to select if you check of Display on these, but don’t want to limit which 
records display. We’ll look into how to make that clearer.

We’re aiming to have the release with custom reports out by the end of the 
year, though there are many factors that will impact the specific timing. We’ll 
have more information to share in the coming weeks.

Christine

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Wendy 
Scheir
Sent: Friday, October 22, 2021 11:50 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Developing custom reports

Thank you, Christine! I gave this a test and it does indeed have just the 
functionality that we are seeking!

As for feedback, I only gave it three tries, and selecting fields to include 
worked well. The place that I had a bit of trouble was understanding how the 
combination "Display"/"Narrow by Values" was working. If one does not click 
Display, does one still need to narrow by a value, or, if one does not want to 
narrow by a value, does one need to select the blank option in the dropdown, 
even if one has not checked Display? What I was trying to do was to see if I 
could generate a report that included all of the resources present in the 
sandbox, but the test runs, despite my various selections of Display/Narrow by 
Values, I all 3 times ended up with a list of only 2 of the 10 resources. I was 
probably just not clicking the right combination of Display/Narrow by Value 
options, so maybe just a revision of terminology or rollover instructions or 
something like that would help.

But this is an exciting feature--when is the new release?!

Wendy

On Fri, Oct 22, 2021 at 9:57 AM Christine Di Bella 
mailto:christine.dibe...@lyrasis.org>> wrote:
Hi Wendy (and everyone),

There may be plugins and community solutions that people can share, but we are 
working on some custom reports functionality that we hope to put into the next 
release of ArchivesSpace. It’s still in progress, but testable on the test 
server at http://test.archivesspace.org (username admin, password admin). The 
way it works is that a user creates re-runnable templates for custom reports 
using the Custom Report Templates option on the gear menu, and then can use the 
templates when selecting the new Custom Reports option in the reports area.

We’d welcome feedback about this work-in-progress feature. You can send it to 
us at archivesspaceh...@lyrasis.org<mailto:archivesspaceh...@lyrasis.org>.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905


[ASpaceOrgHomeMedium]



From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 On Behalf Of Wendy Scheir
Sent: Friday, October 22, 2021 9:34 AM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Developing custom reports

Dear Adrien,

An extremely belated followup to your message about creating custom reports. We 
are especially in need of an export of a csv list from the SUI of resource 
record level data (either a full dump or selectable fields) to gather data for 
reporting purposes. I think this matches one that you described in your 
message. Did you move ahead with developing this report, or perhaps find one 
that already existed? Do any other list members know of such a report or plugin 
that can be installed and then activated from the SUI?

Many thanks,

Wendy

The New Archives and Special Collections
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org<mailto:Archivesspace_Users_Group@lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Developing custom reports

[Christine Di Bella]

Hi Wendy (and everyone),

There may be plugins and community solutions that people can share, but we are 
working on some custom reports functionality that we hope to put into the next 
release of ArchivesSpace. It’s still in progress, but testable on the test 
server at http://test.archivesspace.org (username admin, password admin). The 
way it works is that a user creates re-runnable templates for custom reports 
using the Custom Report Templates option on the gear menu, and then can use the 
templates when selecting the new Custom Reports option in the reports area.

We’d welcome feedback about this work-in-progress feature. You can send it to 
us at archivesspaceh...@lyrasis.org.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905


[ASpaceOrgHomeMedium]



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Wendy 
Scheir
Sent: Friday, October 22, 2021 9:34 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Developing custom reports

Dear Adrien,

An extremely belated followup to your message about creating custom reports. We 
are especially in need of an export of a csv list from the SUI of resource 
record level data (either a full dump or selectable fields) to gather data for 
reporting purposes. I think this matches one that you described in your 
message. Did you move ahead with developing this report, or perhaps find one 
that already existed? Do any other list members know of such a report or plugin 
that can be installed and then activated from the SUI?

Many thanks,

Wendy

The New Archives and Special Collections
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] upcoming change in the way the ArchivesSpace application is deployed

[Christine Di Bella]

Hello ArchivesSpace users,



We wanted to alert you to an upcoming change in the way the ArchivesSpace 
application is deployed. This change will not be noticeable to end users of the 
application, but it will affect those that install and maintain it for users.



Background



ArchivesSpace uses Solr<https://solr.apache.org/> for its search platform. 
Since its original release in 2013, ArchivesSpace has used a version of Solr 
that can be embedded into the application so that Solr is installed and 
configured by default when ArchivesSpace is installed. Though most 
ArchivesSpace deployments opt for this embedded version of Solr, some sites 
choose to use an external deployment of Solr and maintain it separately from 
ArchivesSpace.



In its own upgrades over the years, Solr made some changes so that it can no 
longer be embedded. While we have stayed on the highest embeddable version of 
Solr (v4.10.4) for years, this version is now old and unsupported by its 
maintainers, and it is no longer sustainable for us to use it in new releases. 
In order to maintain and improve this critical piece of ArchivesSpace 
infrastructure, we need to upgrade Solr. In the process we will need to make 
the transition to using external Solr only.



What does this mean for me?



Once we make this change, if you are responsible for deploying ArchivesSpace at 
your institution, you will need to download and install Solr and use 
ArchivesSpace's supplied Solr configuration to create the Solr index. This will 
be in addition to managing your own MySQL database. Solr will no longer be 
distributed with ArchivesSpace and ArchivesSpace will no longer work 
out-of-the-box without an external Solr deployment. ArchivesSpace will need to 
be fully re-indexed when this transition occurs.

If you are not the person responsible for deploying ArchivesSpace at your 
institution, this change will not directly affect you, though it will be 
important to make sure the person responsible for deploying your ArchivesSpace 
is aware of the change.

Will you have strict requirements for how to deploy Solr?

Like with MySQL, the ArchivesSpace team does not intend to be opinionated about 
how Solr is deployed externally. System administrators will be able to use 
whatever method they prefer to install Solr. For those who require more 
guidance, however, we will have instructions for using a standalone Solr 
installation along with specific ArchivesSpace Solr configuration files. These 
will be in addition to the standard documentation provided by Solr 
(https://solr.apache.org/guide/8_9/installing-solr.html).

When will this happen?

We expect to make the transition to external Solr with the release on the 
roadmap<https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/2634973195/Roadmap+as+of+September+2021>
 that is planned for December 2021. Even so, older versions of ArchivesSpace 
will continue to work with the embedded Solr that was included with them at the 
time of their release.

How can I learn more?

We will be providing a number of community education opportunities along with 
technical documentation beginning later this fall to help people understand 
what they will need to do to make the changes. These may include webinars, 
recorded tutorials, Q sessions for technical staff, and online documentation. 
All of these resources will be publicly available to members and non-members. 
In addition, ArchivesSpace members will be able to access technical support as 
questions arise as a benefit of their membership.

Thank you for your understanding and cooperation as we continue to work to 
improve ArchivesSpace for everyone. We look forward to working with you to 
facilitate this important transition. Please feel free to reach out with any 
questions or feedback.
Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905


[ASpaceOrgHomeMedium]




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

[Archivesspace_Users_Group] ArchivesSpace v3.1.0 now available

[Christine Di Bella]

ArchivesSpace is announcing the availability of v3.1.0. You can download it at 
https://github.com/archivesspace/archivesspace/releases/.

This release includes a number of accessibility improvements, particularly to 
the public interface. Many of these were identified in an accessibility audit 
conducted by Deque across the open source applications that make their homes at 
LYRASIS, which include DSpace, CollectionSpace, and ArchivesSpace. The release 
also includes specific bug fixes and small feature improvements prioritized by 
the Development Prioritization sub-team. There are also additional performance, 
backend and staff interface improvements from Hudson Molonglo developers James 
Bullen, Mark Triggs, and Payten Giles that derived from work HM did for 
Queensland State Archives as part of a larger project.
Thanks to all of our community members who contributed code for this release: 
Alex Duryee, Andrew Morrison, Dave Mayo, James Bullen, Mark Triggs, Nick 
Butler, Payten Giles, Sam Hatfield, and Sean Anderson. As always, program team 
members Lora Woodford, Brian Hoffman, and Mark Cooper, as well as contractors 
Manny Rodriguez and Brian Zelip, wrote and/or reviewed substantial code for the 
release. Thanks also to our community groups, especially the Testing sub-team, 
for their efforts.

Information on upgrading to a new version of ArchivesSpace is available at 
https://archivesspace.github.io/tech-docs/administration/upgrading.html. If you 
have any difficulties, please let us know.

This is the spring/summer 2021 release from the 
roadmap<https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/2634973195/Roadmap+as+of+September+2021>.
 Items that were projected for this release that did not make it in have been 
shifted to future releases.

Please get in touch if you have any questions. Thanks as always for your 
feedback and support.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905


[ASpaceOrgHomeMedium]

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

[Archivesspace_Users_Group] release candidate available - ArchivesSpace v3.1.0-RC1

[Christine Di Bella]

Hello ArchivesSpace members,

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

This release includes a number of accessibility improvements, particularly to 
the public interface. Many of these were identified in an accessibility audit 
conducted by Deque across the open source applications that make their homes at 
LYRASIS, which include DSpace, CollectionSpace, and ArchivesSpace. It also 
includes specific bug fixes and small feature improvements prioritized by the 
Development Prioritization sub-team.

A particular thanks to our Testing sub-team for their work testing individual 
JIRAs and doing regression testing across the application.

Please try this release candidate out and let us know at 
archivesspaceh...@lyrasis.org<mailto:archivesspaceh...@lyrasis.org> by 
September 14 if you notice any problems with the specific areas addressed in 
this release, or if anything that was working before no longer is. Pending the 
results of this testing, we will aim to release the production version of 3.1.0 
shortly afterwards.

This is the spring/summer 2021 release from the 
roadmap<https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/2634973195/Roadmap+as+of+September+2021>.
 Items that were projected for this release that did not make it in have been 
shifted to future releases.

Please get in touch if you have any questions. Thanks as always for your 
feedback and support.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905


[ASpaceOrgHomeMedium]

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

[Archivesspace_Users_Group] project developer for ArchivesSpace

[Christine Di Bella]

Hello ArchivesSpace members,

ArchivesSpace is currently seeking a project developer for a specialized 
assignment to work on frontend upgrades and improvements. It is a remote 
position and has a flexible term. While it could be for as little as three 
months, there is a possibility of extension.

The job description is listed below and at 
https://lyrasis.isolvedhire.com/jobs/344198-25777.html. All applications should 
be submitted via the LYRASIS website.

Please forward this to anyone you think might be interested, and feel free to 
reach out to Brian Hoffman or me if you have questions, ideas for candidates, 
or if you're interested yourself.

Thanks for your help,
Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905


[ASpaceOrgHomeMedium]





ArchivesSpace Project Developer (remote)



ArchivesSpace is seeking a project developer.

In search of a developer who can work within the multi-service architecture and 
the Java-based build system (Apache Ant), and who is also proficient with Ruby 
on Rails, Javascript (frameworks and build systems), and Twitter Bootstrap (or 
a similar framework).



This is a contract remote position for 3-6 months.

This is a full-time position but will consider part-time.

There is the possibility for the term to be extended.


Duties/Job Responsibilities:
Under the supervision of the Tech Lead and the rest of the development team, 
the contractor will upgrade JavaScript and Ruby dependencies to more recent 
versions (or in some cases alternatives), while maintaining test coverage and 
rewriting tests as necessary.

Required Knowledge, Skills, and Abilities:
Required

  *   Excellent command of git and be able to maintain a development branch 
that tracks the master branch.
  *   Exceptional command of Rspec and be able to follow the principles of 
test-driven development.
Preferred

  *   Familiarity with library and archival metadata standards and practices 
(EAD, MARC).
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] ArchivesSpace 3.0.2 now available

[Christine Di Bella]

Hello ArchivesSpace members,

ArchivesSpace 3.0.2 is now available. Version 3.0.2 is the direct result of 
community feedback about the migration of date sub-records attached to agents. 
The updated migration will create an equal number of new structured date 
sub-records from the pre-3.x date sub-records and do some parsing of date 
expressions in range dates into begin and end date expressions. If you 
previously upgraded to 3.0.0 or 3.0.1, this migration will be skipped.

This version also fixes a bug uncovered with the spreadsheet importer for 
adding digital objects to archival objects.

More information about what's in the release and the link to download it are at 
https://github.com/archivesspace/archivesspace/releases. Information on 
upgrading to a new version of ArchivesSpace is available at 
https://archivesspace.github.io/tech-docs/administration/upgrading.html.

If you have questions or need any assistance, please let us know. The timing of 
this smaller release is intended to meet the needs of institutions that need to 
complete an upgrade before the end of the summer. If you do not have that kind 
of time pressure, you may want to wait for the next version (which we 
anticipate to be 3.1.0) as we expect to put out a more typical release with the 
usual complement of bug fixes, feature enhancements, and infrastructure 
improvements in a few weeks.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905


[ASpaceOrgHomeMedium]

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

Re: [Archivesspace_Users_Group] Duplicated agent dates in migration to 3.0.1

[Christine Di Bella]

Patrick and Cory,

Thank you for surfacing this issue. We've looked into this more and I'd like to 
work with you to determine the desired outcome for migration of these dates. 
I'll reach out to you directly. If anyone else reading these messages has a 
strong interest in or suggestions for the migration of this information, would 
you please comment here or reach out to me to participate in these discussions?

In the meantime, I would suggest that people who have both structured dates and 
date expressions on Agents in their pre-3.0 ArchivesSpace hold off on migrating 
for now. These kinds of dates would typically be in your Dates of Existence 
sub-records. If pre-3.0 you have been using only the Dates field in a Name 
Form, or if you only use structured dates, the issue mentioned here is less 
likely to be pertinent to you.

Thanks for your help,
Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905


[ASpaceOrgHomeMedium]



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Cory 
Nimer
Sent: Tuesday, June 22, 2021 10:59 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Duplicated agent dates in migration to 
3.0.1

Patrick,

We found the same thing in our test migration to 3.0.1. In cases where an Agent 
date entry included both a date expression and normalized dates, the 
application had split up the 2.8 date entry into two separate entries--one for 
the date expression (without normalized dates) and one for the normalized dates 
(without date expressions). Our impression was that the application was not 
parsing the date expression at all.

This is a significant issue for us moving forward, and we would be interested 
in learning more about what approaches other institutions have been considering 
to address this issue.

Best,

Cory Nimer
University Archivist
Brigham Young University

From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 On Behalf Of Galligan, Patrick
Sent: Monday, June 21, 2021 12:10 PM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] Duplicated agent dates in migration to 
3.0.1

Hi all,

We've noticed that in our test migration from ArchivesSpace version 2.8.0 to 
3.0.1 that the agent migration was sometimes creating two separate structured 
dates based on whether there was an existing date expression or not in the 
dates of existence section.

Here is the JSON before migration:

"dates_of_existence": [
{
"lock_version": 0,
"expression": "1915-2017",
"begin": "1915",
"end": "2017",
"created_by": "pgalligan",
"last_modified_by": "pgalligan",
"create_time": "2019-12-04T14:24:11Z",
"system_mtime": "2019-12-04T14:24:11Z",
"user_mtime": "2019-12-04T14:24:11Z",
"date_type": "range",
"label": "existence",
"jsonmodel_type": "date"
}
],


Here is the JSON post-migration:

"dates_of_existence": [
{
"create_time": "2021-06-16T19:12:16Z",
"system_mtime": "2021-06-16T19:12:16Z",
"user_mtime": "2021-06-16T19:12:16Z",
"lock_version": 0,
"date_label": "existence",
"date_type_structured": "single",
"jsonmodel_type": "structured_date_label",
"structured_date_single": {
"date_expression": "1915-2017",
"create_time": "2021-06-16T19:12:16Z",
"system_mtime": "2021-06-16T19:12:16Z",
"user_mtime": "2021-06-16T19:12:16Z",
"lock_version": 0,
"date_role": "begin",
"date_standardized_type": "standard",
"jsonmodel_type": "structured_date_single"
}
},
{
"create_time": "2021-06-16T19:12:16Z",
"system_mtime": "2021-06-16T19:12:16Z",
"user_mtime": "2021-06-16T19:12:16Z",
"lock_version": 0,
"date_label": "existence",
  

[Archivesspace_Users_Group] ArchivesSpace 3.0.1 now available

[Christine Di Bella]

Hello ArchivesSpace members,

ArchivesSpace 3.0.1 is now available. It corrects an issue with the migration 
of agent contact notes that was present in 3.0.0. When you choose to upgrade 
past 2.8.1 you should use this version. We have pulled the download file for 
3.0.0 to hopefully avoid confusion as much as possible.

Otherwise, everything that was true about 3.0.0 is true about 3.0.1. More 
information about what's in the release and the link to download it are at 
https://github.com/archivesspace/archivesspace/releases. Information on 
upgrading to a new version of ArchivesSpace is available at 
https://archivesspace.github.io/tech-docs/administration/upgrading.html.

If you have questions or need any assistance, please let us know. I apologize 
for the inconvenience but I'm very glad we were able to catch and rectify the 
issue so soon after the original release. We expect to put out a more typical 
release with the usual complement of new infrastructure improvements, bug 
fixes, and feature enhancements in the late summer.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905


[ASpaceOrgHomeMedium]

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

[Archivesspace_Users_Group] updated and simplified ArchivesSpace roadmap

[Christine Di Bella]

Hello ArchivesSpace members,

We have published a new, simplified roadmap related to development for the 
ArchivesSpace application at 
https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/2634973195/Roadmap. 
This new version highlights work currently scheduled for the next 12 months. It 
also mentions priorities that are not currently scheduled for the time period 
but that could shift if additional resources or community partners are 
identified.

In general, the roadmap indicates large areas of development focus, while 
JIRA<http://development.archivesspace.org/> provides details on individual bug 
fixes and features requested by the community. 
GitHub<https://github.com/archivesspace/archivesspace> contains details on the 
actual code used to implement these and to maintain the application overall.

We are aiming to put releases out three times a year, though we may have 
occasional additional releases in between larger ones to address specific 
issues (for example, to address the agent contact note migration issue in 3.0.0 
identified earlier this week). As a release approaches we will provide more 
specific details about the work it will contain. The roadmap will be updated as 
releases come out or significant changes take place.

If the last year and a half have shown us anything (if for some reason we 
didn't know this already), it's that it's very hard to predict what will 
happen, despite best laid plans. This roadmap is our best estimation based on 
what we know now, and we hope it will be helpful for community members as you 
also make plans. Please get in touch if you have questions or suggestions and 
thank you for your ongoing support and participation.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905


[ASpaceOrgHomeMedium]

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

[Archivesspace_Users_Group] pause upgrades to 3.0.0 if you utilize the Contact Notes field in Agents

[Christine Di Bella]

Hello ArchivesSpace members,

Please pause upgrades to 3.0.0 if you utilize the Contact Notes field in 
Agents. We have found an issue with the migration of this information during 
upgrades. We will be putting out a new release that fixes this issue as soon as 
we can.

If you use this field and have already updated to 3.0.0, please get in touch so 
that we can help you address this issue with you own data.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905


[ASpaceOrgHomeMedium]

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

Re: [Archivesspace_Users_Group] lcnaf plugin

[Christine Di Bella]

Hello Tom,

The LCNAF plugin is a very rare case in that it’s both bundled with the 
standard ArchivesSpace application and, because of its popularity, lives on its 
own in case it needs to be updated between our releases due to changes in LC’s 
service. The program team has discussed doing only one or the other because it 
is undeniably duplicative for code maintainers and confusing for users (though, 
on the users side, most people use the one that comes bundled with 
ArchivesSpace and don’t realize there is a separate one). The functionality of 
both LCNAF plugins is identical. For now we’ve continued to keep it the way it 
is pending some larger discussions.

Virtually all other plugins only live on our their own, and most plugins are 
authored by and maintained by community members, not the ArchivesSpace program. 
The community-maintained Awesome ArchivesSpace list links to a lot of great 
ones: https://github.com/archivesspace/awesome-archivesspace.

For some additional context, there’s some information about plugins and 
considerations for turning a plugin into core code at 
https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/916062227/Making+a+Plug-In+part+of+the+Core+Code.
 That document also links to an outline of an evaluation process for 
considering feature contributions, including whether something might best be 
handled as a plugin: 
https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/360546309/ArchivesSpace+Process+for+Evaluating+Potential+Feature+Contributions+to+the+Core+Code.

I hope this helps. If you have other questions, please let us know.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905


[ASpaceOrgHomeMedium]



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Tom 
Hanstra
Sent: Thursday, May 20, 2021 12:23 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] lcnaf plugin

Ok, so I did not see that lcnaf was included in ArchivesSpace right from the 
beginning. I thought I had to get the files from GitHub as I would with other 
plugins, but I see that they are there. In fact several are there.

So I need to revise my overall question to:

- Why is some code added to the zip file but left as a plugin while other code 
is added to the software?

In this instance, lcnaf is there but I need to update the config file to turn 
it on. With other plugins, I have to get the files from somewhere else and turn 
them on. And maybe do more than just put them in the directory (for instance, 
oauth needs to be compiled). How is it determined what goes where and how it is 
or is not included?

Sorry, but this is rather confusing to the newbie.

Thanks
Tom

On Thu, May 20, 2021 at 10:51 AM Joshua D. Shaw 
mailto:joshua.d.s...@dartmouth.edu>> wrote:
Hi Tom

To enable any plugin in the /plugins directory, you need to update the config 
file. Specifically, the entry

AppConfig[:plugins] = []

The array contents are just the directory names of the plugins that you want to 
enable

So, to enable just the lcnaf plugin, you would want

AppConfig[:plugins] = ['lcnaf']

https://archivesspace.github.io/tech-docs/ is a good resource.

jds


From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of Tom Hanstra mailto:hans...@nd.edu>>
Sent: Thursday, May 20, 2021 9:09 AM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] lcnaf plugin

Hi, ArchivesSpace users,

I continue my quest to get our site set up and have been told that I need to 
install the lcnaf plugin. I've got a few questions:

First, where is the documentation on how to install the plugin? The code in 
github does not have so much as a README file to give me information on how to 
install it. Do I just grab the code and plunk it into the plugins directory? Or 
is there more to be done?

Second, how does ArchivesSpace decide what plugins get pulled into code and 
which do not. This one, from what I can tell, has been around for a long time 
and yet continues to be a plugin that is added after the fact. Yet other 
plugins have been added into the code. Just curious how that gets decided.

Thanks,
Tom

--
Tom Hanstra
Sr. Systems Administrator
hans...@nd.edu<mailto:hans...@nd.edu>

[https://docs.google.com/uc?export=download=1GFX1KaaMTtQ2Kg2u8bMXt1YwBp96bvf0=0B7APN9POn6xAQ244WWFYMFU3aVJwZ0lxbmVHK3FxNXlCd0RRPQ]
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org<mailto:Archivesspace_Users_Group@lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


--
Tom 

[Archivesspace_Users_Group] announcing the ArchivesSpace Diversity Partnership cohort

[Christine Di Bella]

Hello ArchivesSpace members,

I am delighted to announce our inaugural cohort for the ArchivesSpace Diversity 
Partnership, a new program designed to offer support for implementing the 
ArchivesSpace application to institutions that are themselves or primarily 
serve communities currently underrepresented in the ArchivesSpace community. 
The five institutions are:

Black Cultural Archives - a unique community archive based in the heart of 
Brixton, South London, that was established in 1981 to collect contemporary 
records of Black communities and seeks to transform the understanding of local, 
national and global Black history.

Detroit Sound Conservancy - deliberately rooted in and informed by Detroit's 
community activism, a community-based archive that tells Detroit's story 
through the experiences of its musical people.

Spelman College - a liberal arts college in Atlanta that is one of the only two 
remaining HBCUs founded to educate women of the African diaspora. In addition 
to being the official college repository, the Archives also documents women of 
the African Diaspora broadly, and houses the Audre Lorde and Toni Cade Bambara 
papers.

Weeksville Heritage Center - a historic site, house museum, and cultural center 
in Brooklyn, New York, whose mission is to use education, the arts and a social 
justice lens to preserve, document and inspire engagement with the history of 
Weeksville, one of the largest free Black communities in pre-Civil War America.

Xavier University of Louisiana - the only Catholic HBCU in the country, with 
historic collections that focus on Black history, New Orleans and Louisiana 
history, Black Catholics, and the Gulf Coast region, in addition to XULA 
institutional history.

We were fortunate to receive many strong applications, from a fascinating group 
of archives and collecting institutions, which provided our review team with 
quite a challenge when putting together this relatively small cohort. I'd like 
to thank review team members Audra Eagle Yun of UC Irvine, Skyla Hearn of Cook 
County Historic Archives and Records Office, Lizeth Ramírez of UCLA, and 
Brittany Newberry of Robert W. Woodruff Library, Atlanta University Center (who 
chaired the group), along with ArchivesSpace Community Engagement Coordinator 
Jessica Crouch, for all their hard work.

We are excited to have such excellent partners in this new endeavor. These 
institutions will join our member community officially on July 1, but we are 
already working with them to make sure they have what they need to get started 
with the application and the community. Please join me in welcoming them to 
ArchivesSpace!

All best,
Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905


[ASpaceOrgHomeMedium]

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

[Archivesspace_Users_Group] ArchivesSpace v3.0.0 now available

[Christine Di Bella]

ArchivesSpace is announcing the availability of v3.0.0. You can download it at 
https://github.com/archivesspace/archivesspace/releases/.


This release centers around changes to the agents module of ArchivesSpace to 
make it more standards-compliant with EAC-CPF and the MARCXML format for 
authority data, enabling deeper and richer description of people, families, and 
corporate entities, their relationships to each other and their relationships 
to materials held outside ArchivesSpace. This work is the result of a community 
specification involving the participation of many users across the 
ArchivesSpace community, mostly notably Cory Nimer, Sue Luftschein, and Brad 
Westbrook. Through this work new fields and sub-records have been added to the 
agents schema, and staff and public interface views, imports, exports, and 
auxiliary functionality like agent merging have all been updated. There is also 
a new Light mode, which provides the option for users to continue to work with 
agent records in the staff interface in a pared down view that is similar to 
that of ArchivesSpace versions prior to this one.

This release also contains improvements in some other areas of the application 
contributed by community developers and program team developers and 
contractors. While all are valuable, a few community contributions are of 
particular note:

  *   For spreadsheet fans, the developers and archivists at Harvard University 
have contributed a spreadsheet feature focused on adding top containers and 
associated information to existing archival objects. With this feature, a user 
will download a file of archival objects for a resource, add top container 
information outside the application, and then import the information into the 
resource record, from the Load via Spreadsheet area.
  *   There is a new Unpublish All feature, contributed by Nick Butler at the 
University of Cambridge. This feature allows for unpublishing everything in a 
resource or groups of archival objects within a resource and represents the 
conversion of this popular plugin to core code.
  *   Hudson Molonglo developers James Bullen, Mark Triggs, and Payten Giles 
contributed additional performance, backend and staff interface improvements. 
These derived from work HM did for Queensland State Archives as part of a 
larger project.
Thanks very much to all of our community members who contributed code for this 
release: Andrew Morrison, Blake Carver, Bobbi Fox, Brian Harrington, Corey 
Schmidt, Dave Mayo, Dee Dee Crema, Fred Reiss, James Bullen, Katie Amaral, Mark 
Triggs, Nick Butler, Noah Geraci, Payten Giles, Peter Heiner, and Steve 
Majewski. We were also pleased to work for the first time with contractors 
April Rieger and Braydon Justice of Notch8 on a small project.

Program team members Lora Woodford, Mark Cooper, and Brian Hoffman wrote and 
reviewed extensive code and supervised the work of Manny Ramirez, our longtime 
contractor who devoted very substantial time to the expansion of the agents 
module. This is also the first release under Brian's supervision as our new 
Tech Lead. This release would, of course, not have been possible without the 
hard work of our community groups, including our Development Prioritization, 
Testing, Metadata Standards, Technical Documentation, and User Documentation 
sub-teams, the API Documentation Ad Hoc Working Group, and the Core Committers 
Group. We'd also like to thank the SNAC Technology Infrastructure Working Group 
for reviewing and testing the changes for EAC-CPF at various points along the 
way.

Information on upgrading to a new version of ArchivesSpace is available at 
https://archivesspace.github.io/tech-docs/administration/upgrading.html. If you 
have any difficulties, please let us know.

ArchivesSpace 3.0.0 has been a major undertaking and we appreciate everyone who 
has been involved along the way. Thanks to all for your help and support.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905


[ASpaceOrgHomeMedium]

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

Re: [Archivesspace_Users_Group] ArchivesSpace with Preservica 6.3

[Christine Di Bella]

Hello Jerry,

I can't speak about the Preservica issue, but as far as the ArchivesSpace 
upgrade issue goes, you will be able to upgrade straight to 3.0.0 from 2.7.1. 
Most ArchivesSpace upgrades work this way, but we call it out in the release 
notes when that is not the case.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905


[ASpaceOrgHomeMedium]



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Jerry 
Boggio
Sent: Monday, May 3, 2021 9:47 AM
To: archivesspace_users_group@lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] ArchivesSpace with Preservica 6.3

Hello ASpace Users;

We have a question about with version of ASpace should we be using in order to 
integrate with Preservica 6.3? We are currently running version 2.7.1 of ASpace 
and are in the process of upgrading Preservica to version 6.3. We are also 
contemplating going to stable ASpace version 2.8.1 or waiting for version 3.0.0.

Further, in regards to version 3.0.0 of ASpace, is it expected we could go 
directly from version 2.7.1 to 3.0.0 or are incremental updates needed?

Thank you!
Gerard (Jerry) Boggio | MITRE Corporation | R124 - Collaboration & Info 
Management | 781-271-2719

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

[Archivesspace_Users_Group] ArchivesSpace Update - April 2021

[Christine Di Bella]

  [cid:image001.jpg@01D73DB0.B11D39E0]


ArchivesSpace Update - April 2021



Development


We put out a second release candidate for ArchivesSpace 
v3.0.0 
in mid-April. While v3.0.0 continues to center around the expansion of the 
agents module, in the period between the two release candidates we were able to 
include bug fixes and improvements in some other areas of the application that 
were contributed by community developers and program team developers and 
contractors. For spreadsheet fans, the developers and archivists at Harvard 
University have contributed another feature, this one focused on adding top 
containers and associated information to existing archival objects. With this 
feature, a user will download a file of archival objects for a resource, add 
top container information outside the application, and then import the 
information into the resource record, from the Load via Spreadsheet area. Some 
draft documentation for this feature written by Harvard staff is available at 
https://docs.google.com/document/d/10poB5BDwgEWGYwrfLgkfy_sOjkhmbvStDat_BIm6ucw/edit?usp=sharing.
 Also included among the community contributions are additional performance, 
backend and staff interface improvements courtesy of work Hudson Molonglo 
developers James Bullen, Mark Triggs, and Payten Giles did for Queensland State 
Archives as part of a larger project.


Testing of the second release candidate is finishing up, after which we expect 
to put out the 3.0.0 release.


Membership Renewals

ArchivesSpace is developed by and for the community that uses it, and 
strengthened by services and activities that support our community and connect 
us to one another. As we get close to the end of another membership year, we 
want to give a special thanks to all of the institutions that have joined us as 
members. ArchivesSpace membership is our primary source of revenue and informs 
and sustains every aspect of the program, including software development, 
support and engagement. Thanks for all that your support makes possible.


ArchivesSpace membership renewals for 2021-2022 will be sent to all current 
members during the first two weeks of May 2021. If you have any questions, or 
if you would like to join as a new member for the 2021-2022 membership year, 
please let us know at 
archivesspaceh...@lyrasis.org. We look 
forward to another year working together.




Webinar Announcement: Managing AV Materials in ArchivesSpace

When: May 19, 2021
Time: 2:00 p.m. - 3:00 p.m. ET (11:00 a.m. - 12:00pm PT)
Where: Zoom

 Registration: 
https://lyrasis.zoom.us/webinar/register/WN_Zp3vy-SZQTeWZV6qI_gh5Q



This webinar will be recorded and made available on the ArchivesSpace YouTube 
channel.



Webinar description:



In this webinar, archivists working with audiovisual materials and 
ArchivesSpace will discuss how their shared experiences have led them to help 
and bolster one another's work in ArchivesSpace and in managing audiovisual 
materials.  They'll discuss the specific projects they have worked  on to 
describe audiovisual materials in ArchivesSpace.



First, Siobhan Hagan of the Mid-Atlantic Regional Moving Image Archive (MARMIA) 
will discuss the work of the Association of Moving Image Archivists's Regional 
Audiovisual Archives Committee overall and how this work has led to 
collaborative working relationships across the group.


Next, Megan McShea will speak about her work creating the Archives of American 
Art's Guidelines to Processing Collections with Audiovisual 
Material,
 and then how her perspective changed while working with MARMIA's massive 
WJZ-TV Collection, where they are using ArchivesSpace to transform their 
inherited Word document videotape inventories into searchable, actionable 
collection description.



Then, Jamie Marie Wagner of University of Colorado Boulder Libraries will speak 
about how she adapted the Guidelines to Processing Collections with Audiovisual 
Material for her institution, plus some specific challenges they have come 
across and tips and tricks for others.


Finally, Hannah Wiatt Davis of Florida State University Libraries will speak 
about the process of migrating to ArchivesSpace, the subsequent cleanup of 
data, and their initial experimentations with the Assessment Module for AV 
materials.



A Q will follow all presentations.



Presenter Information:


Siobhan C. Hagan holds her M.A. in Moving Image Archiving and Preservation 
(MIAP) from NYU's Tisch School of the Arts and has worked in a variety of 
collecting organizations throughout her career, including the UCLA Library, the 
National Aquarium, and the Smithsonian Institute. She is currently the Project 
Manager of the Memory Lab Network at the DC Public Library and is the Founder 
and CEO of the 

Re: [Archivesspace_Users_Group] [Archivesspace_uac] release candidate available - ArchivesSpace v3.0.0-RC2

[Christine Di Bella]

Hi Cory,

That’s good to hear that you were able to successfully install the release 
candidate and that both the staff and public interfaces seem to be working well 
in general.

On the specific problem from your log, it seems like that has to do with data 
in (or missing from) a record. Is this happening for all agents or just some? 
Can you send some screenshots from the staff side of a record where this is 
happening? We can move this over to 
archivesspaceh...@lyrasis.org<mailto:archivesspaceh...@lyrasis.org> if it seems 
like it’s going to require a lot of back and forth and troubleshooting.

Thanks for your continued testing and feedback!

Christine

From: Cory Nimer 
Sent: Wednesday, April 28, 2021 5:17 PM
To: Archivesspace Users Group 
Cc: Christine Di Bella 
Subject: RE: [Archivesspace_Users_Group] [Archivesspace_uac] release candidate 
available - ArchivesSpace v3.0.0-RC2

Christine,

Thank you for making the updated release available to us. Our IT staff report 
that the installation went well, and in doing some local testing we have found 
that the staff interface and most of the public user interface work well. 
However, when trying to access Agent records in the PUI we receive an error 
message (other record types work without any issues). Below are the comments 
from our IT staff, as well as a relevant extract from the application log:

The release notes don't mention the need for a reindex so I don't think that's 
the problem, unless they forgot to mention that in the release notes. It looks 
like it might be another bug with this release candidate. I'll paste the log 
output when accessing the url you mentioned below. I think you should let the 
archivesspace developers take a look:

Apr 28, 2021 3:00:44 PM org.apache.solr.core.SolrCore execute
INFO: [collection1] webapp= path=/select 
params={mm=100%25=\=0=0=-exclude_by_default:true=publish:true=types:pui=1=title:"(uri:("\/agents\/people\/2335"))"*=(uri:("\/agents\/people\/2335"))=title^10=true="=json=true}
 hits=1 status=0 QTime=1
Apr 28, 2021 3:00:44 PM org.apache.solr.core.SolrCore execute
INFO: [collection1] webapp= path=/select 
params={mm=100%25=\=0=0=-exclude_by_default:true=-types:pui_only=suppressed:false=500=title:"(id:("global"))"*=(id:("global"))=title^10=true="=json=true}
 hits=0 status=0 QTime=1
Apr 28, 2021 3:00:44 PM org.apache.solr.core.SolrCore execute
INFO: [collection1] webapp= path=/select 
params={mm=100%25=\=0=0=-exclude_by_default:true=-types:pui_only=suppressed:false=500=title:"(id:("\/agents\/corporate_entities\/18"))"*=(id:("\/agents\/corporate_entities\/18"))=title^10=true="=json=true}
 hits=1 status=0 QTime=1
Apr 28, 2021 3:00:44 PM org.apache.solr.core.SolrCore execute
INFO: [collection1] webapp= path=/select 
params={mm=100%25=primary_type=subjects=\=0=0=((types:("classification")+OR+(types:("digital_object")+OR+(types:("archival_object")+OR+(types:("accession")+OR+(types:("resource")+OR+(types:("repository"=-exclude_by_default:true=publish:true=types:pui=title_sort+asc=10=title:"published_agent_uris:"/agents/people/2335"+AND+types:pui"*=published_agent_uris:"/agents/people/2335"+AND+types:pui=100=edismax=four_part_id^3+title^2+finding_aid_filing_title^2+fullrecord=four_part_id^4=title^10=true="=0=json=true}
 hits=48 status=0 QTime=38
Apr 28, 2021 3:00:44 PM org.apache.solr.core.SolrCore execute
INFO: [collection1] webapp= path=/select 
params={mm=100%25=\=0=0=-exclude_by_default:true=-types:pui_only=suppressed:false=500=title:"(id:("\/repositories\/14")+OR+id:("\/repositories\/14")+OR+id:("\/repositories\/14")+OR+id:("\/repositories\/14")+OR+id:("\/repositories\/14")+OR+id:("\/repositories\/14")+OR+id:("\/repositories\/14")+OR+id:("\/repositories\/14")+OR+id:("\/repositories\/14")+OR+id:("\/repositories\/14"))"*=(id:("\/repositories\/14")+OR+id:("\/repositories\/14")+OR+id:("\/repositories\/14")+OR+id:("\/repositories\/14")+OR+id:("\/repositories\/14")+OR+id:("\/repositories\/14")+OR+id:("\/repositories\/14")+OR+id:("\/repositories\/14")+OR+id:("\/repositories\/14")+OR+id:("\/repositories\/14"))=title^10=true="=json=true}
 hits=1 status=0 QTime=4
Apr 28, 2021 3:00:44 PM org.apache.solr.core.SolrCore execute
INFO: [collection1] webapp= path=/select 
params={mm=100%25=\=0=0=-exclude_by_default:true=-types:pui_only=suppressed:false=500=title:"(id:("\/repositories\/14\/resources\/9776"))"*=(id:("\/repositories\/14\/resources\/9776"))=title^10=true="=json=true}
 hits=1 status=0 QTime=1
Apr 28, 2021 3:00:44 PM org.apache.solr.core.SolrCore execute
INFO: [c

[Archivesspace_Users_Group] 1 Day Left to Apply for the ArchivesSpace Member Match program

[Christine Di Bella]

Dear ArchivesSpace Members,



As a reminder, tomorrow is the last day to apply for the ArchivesSpace Member 
Match program. Applications are being accepted through tomorrow, April 30, 2021.



The Member Match program is an initiative to engage the ArchivesSpace 
membership community, created and organized by the Member Engagement sub-team 
of the ArchivesSpace User Advisory Council, with support from the ArchivesSpace 
Community Engagement Coordinator. The program is intended to be a resource and 
venue for peer-to-peer support between ArchivesSpace members. For one, 
year-long term, participants will be matched with a member with whom they can 
receive and offer professional insight, advice, and comradery. The program will 
also offer participants the opportunity to engage in exclusive events and 
enlightening discussions about ArchivesSpace and its active user community.

Eligibility

Any individual affiliated with an ArchivesSpace member organization is eligible 
to participate in the ArchivesSpace Member Match program and there is no limit 
to the number of individuals from a member organization that may participate.

If you are unsure of your organization's ArchivesSpace membership status, visit 
https://archivesspace.org/community/whos-using-archivesspace or email 
archivesspaceh...@lyrasis.org.

To Apply

There is a short application to complete at 
https://airtable.com/shr1nE3RWpR7Y78En.

Applications should be submitted by April 30. Applicants will be notified of 
their matches no later than June 30.

To Learn More

Visit the Member Match wiki: 
https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/2198568994/ArchivesSpace+Member+Match+Program

The ArchivesSpace Member Engagement Sub-team conducted an informational webinar 
on March 10th.  You can find a link to the recording of this webinar on the 
Member Match wiki.



Please feel free to direct any questions to 
archivesspaceh...@lyrasis.org

-Sent on behalf of the ArchivesSpace Member Engagement sub-team


Kate Blalack, American Song Archive

Regina Carra, American Folk Art Museum

Bailey Hoffner, University of Oklahoma

Ashley Knox, University of North Carolina Wilmington

Brittany Newberry, Atlanta University Center and ArchivesSpace User Advisory 
Council Chair

Jessica Crouch, ArchivesSpace Community Engagement Coordinator
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] [Archivesspace_uac] release candidate available - ArchivesSpace v3.0.0-RC2

[Christine Di Bella]

Hello Cory (and anyone else following this thread),

There’s a new zip file posted for v3.0.0-RC2 on the releases 
page<https://github.com/archivesspace/archivesspace/releases> that we think 
remedies this issue. If you can, would you please ask your IT staff to try with 
this file and let us know how it goes?

Thanks for your help,
Christine

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Cory 
Nimer
Sent: Friday, April 23, 2021 7:03 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] [Archivesspace_uac] release candidate 
available - ArchivesSpace v3.0.0-RC2

Brian,

We are currently running the following plugins:

AppConfig[:plugins] = ['local', 'byu-branding', 'user_defined_in_basic', 
'contentdm-get-metadata', 'archivesspace_export_service', 'tree_component_id', 
'aspace_sitemap']

Our IT staff did try running the release candidate without the plugins, though, 
and they reported that this did not change the errors they were receiving. At 
this point they have decided to stop testing on our end until the next release 
candidate, given the current installation issues.

Thanks for your help,

Cory

From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 On Behalf Of Brian Hoffman
Sent: Friday, April 23, 2021 1:52 PM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] [Archivesspace_uac] release candidate 
available - ArchivesSpace v3.0.0-RC2

Hi Cory,

It might be possible to eliminate the issue with the staff interface by setting 
an environment variable. For example:

BUNDLE_WITH="default" ./archivesspace.sh start

I think the issue with the public app is different and is going to require a 
follow-up release next week.

I am also curious to know what plugins you are using? Did you copy them over 
from your production install?

Brian


From: 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of Cory Nimer mailto:cory_ni...@byu.edu>>
Reply-To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Date: Friday, April 23, 2021 at 3:04 PM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] [Archivesspace_uac] release candidate 
available - ArchivesSpace v3.0.0-RC2

We are currently running Java 1.8.0_282.

From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 On Behalf Of Blake Carver
Sent: Friday, April 23, 2021 10:53 AM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] [Archivesspace_uac] release candidate 
available - ArchivesSpace v3.0.0-RC2

What's the JAVA version on there?

From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of Cory Nimer mailto:cory_ni...@byu.edu>>
Sent: Friday, April 23, 2021 12:42 PM
To: Christine Di Bella 
mailto:christine.dibe...@lyrasis.org>>; 
Archivesspace Users Group 
(archivesspace_users_group@lyralists.lyrasis.org<mailto:archivesspace_users_group@lyralists.lyrasis.org>)
 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] [Archivesspace_uac] release candidate 
available - ArchivesSpace v3.0.0-RC2


Christine,



Here are the basic specs for our testing server according to our IT staff:



RHEL 8.3

4 procs

5GB RAM



For what it's worth, the error I posted that says there is a missing ruby gem 
is what I see if I go to the staff interface. If I go to the PUI, it will show 
a different missing ruby gem (sassc-2.4.0). Not sure if other pages might 
reveal other missing gems. Christine mentioned that others had seen a similar 
issue but the gem mentioned was different, so maybe they were looking at a 
different page. In any case it seems that somehow this build of ArchivesSpace 
is missing some required ruby gems.



If you need other information about the server, please let me know.



Best,



Cory



From: Christine Di Bella 
mailto:christine.dibe...@lyrasis.org>>
Sent: Friday, April 23, 2021 9:17 AM
To: Cory Nimer mailto:cory_ni...@byu.edu>>; Archivesspace 
Users Group 
(archivesspace_users_group@lyralists.lyrasis.org<mailto:archivesspace_users_group@lyralists.lyrasis.org>)
 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_uac] release candidate available 

Re: [Archivesspace_Users_Group] [Archivesspace_uac] release candidate available - ArchivesSpace v3.0.0-RC2

[Christine Di Bella]

Hello Cory,

We're investigating a gem-related issue where the second release candidate is 
not running correctly on some kinds of servers. (We encountered something 
similar on a Windows server yesterday, though the gem mentioned was different.) 
Would you please post the specs of your server here or email them to me 
directly?

There was an issue that affected all Rails applications between the release of 
our first release candidate and our second one that required us to do some 
unplanned upgrades, though we were hopeful that the impact would be limited for 
3.0 since Rails came out with a fix for their issue during that timeframe. We 
definitely want to hear from people if they are experiencing issues installing 
RC2.

Thanks for your help,
Christine


From: Cory Nimer 
Sent: Friday, April 23, 2021 10:18 AM
To: Archivesspace Users Group (archivesspace_users_group@lyralists.lyrasis.org) 
; Christine Di Bella 

Subject: RE: [Archivesspace_uac] release candidate available - ArchivesSpace 
v3.0.0-RC2


Christine,



When installing the release candidate our IT staff reports that they are 
encountering an error, as described below:



I'm trying to get archivesspace v 3.0.0-RC2 running on our staging server. 
Everything seemed to install ok, and the server seems to start up ok (based on 
the log output), but when I try to bring up the public or staff website I get 
an error. I'm wondering if you could post something on the listserv or point me 
in the right direction to do it.



I upgraded from v2.8.1 and followed the upgrade directions here: 
https://archivesspace.github.io/tech-docs/administration/upgrading.html



Here's the error I get when I try to bring up the staff website 
(https://asadminstg.lib.byu.edu<https://asadminstg.lib.byu.edu/>):



Internal Server Error (500)
Request Method: GET
Request URL: http://asadminstg.lib.byu.edu/
Could not find rubyntlm-0.6.3 in any of the sources from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:86:in
 `block in materialize' from org/jruby/RubyArray.java:2609:in `map!' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:80:in
 `materialize' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:170:in
 `specs' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:237:in
 `specs_for' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:226:in
 `requested_specs' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/runtime.rb:101:in
 `block in requested_specs' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/runtime.rb:20:in
 `setup' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler.rb:149:in
 `setup' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/setup.rb:20:in
 `block in ' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/ui/shell.rb:136:in
 `with_level' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/ui/shell.rb:88:in
 `silence' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/setup.rb:20:in
 `' from org/jruby/RubyKernel.java:974:in `require' from 
uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:130:in
 `require' from 
/srv/archivesspace-3.0.0-rc2/archivesspace/data/tmp/jetty-0.0.0.0-10080-frontend.war-_-any-/webapp/WEB-INF/config/boot.rb:10:in
 `' from org/jruby/RubyKernel.java:974:in `require' from 
uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:54:in
 `require' from uri:classloader:/jruby/rack/rails/environment3.rb:23:in 
`load_environment' from uri:classloader:/jruby/rack/rails_booter.rb:83:in 
`load_environment' from 

[Archivesspace_Users_Group] mail being rejected from ArchivesSpace listservs

[Christine Di Bella]

Hello ArchivesSpace members,

We've been informed that some email systems are rejecting emails from the 
ArchivesSpace Users Group. Assuming that if you're here you want to receive 
these messages, if you go awhile without receiving mail from this listserv or 
other ArchivesSpace listservs to which you're subscribed, please be sure that 
it's not getting delivered to spam or being blocked by your local system. The 
From line on a Users Group message is archivesspace_users_group-bounces at 
lyralists.lyrasis.org<http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group>
 "on behalf of" a specific user, with their email listed as well. When sending 
a message to the listserv, the address is 
archivesspace_users_group@lyralists.lyrasis.org<mailto:archivesspace_users_group@lyralists.lyrasis.org>.
 Our other listservs follow a similar pattern.

In some cases, messages being blocked by an account leads to a situation where 
the account is presumed not to be valid and unsubscribed from the listserv 
automatically. Please check your subscription settings as well if you are not 
receiving mail.

Please note that the archives of the Users Group listserv is at 
http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/ so you'll 
always be able to catch up with what you've missed if you find yourself in this 
situation.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905


[ASpaceOrgHomeMedium]



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

[Archivesspace_Users_Group] release candidate available - ArchivesSpace v3.0.0-RC2

[Christine Di Bella]

Hello ArchivesSpace members,

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

We have put out a second release candidate because a good deal of code has gone 
into our main branch since the release of the first release candidate. While 
some consists of improvements to the agents work that is the focus of v3.0.0, 
there have also been additional contributions from community developers and 
substantial work from the program team developers.

One of the community contributions I wanted to note is a new spreadsheet import 
feature from developers and archivists at Harvard University, focused on adding 
top containers and associated information to existing archival objects. With 
this feature, a user will download a file of archival objects for a resource, 
add top container information outside the application, and then import the 
information into the resource record, from the Load via Spreadsheet area. Some 
draft documentation for this feature written by Harvard Staff is available at 
https://docs.google.com/document/d/10poB5BDwgEWGYwrfLgkfy_sOjkhmbvStDat_BIm6ucw/edit?usp=sharing.
 Please feel free to leave feedback on the documentation.

Also included in the community contributions are a range of performance, 
backend and staff interface improvements courtesy of work Hudson Molonglo 
developers James Bullen, Mark Triggs, and Payten Giles did for Queensland State 
Archives as part of a larger project.

The core of this release candidate centers around changes to the agents module 
of ArchivesSpace to make it more standards-compliant with EAC-CPF and the 
MARCXML format for authority data, enabling deeper and richer description of 
people, families, and corporate entities, their relationships to each other and 
their relationships to materials held outside ArchivesSpace. This work is the 
result of a community specification written through the participation of many 
users across the ArchivesSpace community, mostly notably Cory Nimer, Sue 
Luftschein, and Brad Westbrook. Through this work new fields and sub-records 
have been added to the agents schema, and staff and public interface views, 
imports, exports, and auxiliary functionality like agent merging have all been 
updated. There is also a new Light mode for agents, which provides the option 
for users to continue to work with agent records in the staff interface in a 
pared down view that is similar to that of ArchivesSpace versions prior to this 
one.

Thanks to the many community members who made contributions as we worked on 
bringing this expanded functionality to ArchivesSpace, including both 
individual archives staff and developers and our Testing and User Documentation 
sub-teams.

Please try this release candidate out and let us know at 
archivesspaceh...@lyrasis.org<mailto:archivesspaceh...@lyrasis.org> by April 27 
if you notice any problems with the specific areas addressed in this release, 
or if anything that was working before no longer is. We are aiming to release 
3.0.0 by the end of the month.

Please get in touch if you have any questions. Thanks as always for your 
feedback and support.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905


[ASpaceOrgHomeMedium]

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

[Archivesspace_Users_Group] release candidate available - ArchivesSpace v3.0.0-RC1

[Christine Di Bella]

Hello ArchivesSpace members,

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

This release candidate centers around changes to the agents module of 
ArchivesSpace to make it more standards-compliant with EAC-CPF and the MARCXML 
format for authority data, enabling deeper and richer description of people, 
families, and corporate entities, their relationships to each other and their 
relationships to materials held outside ArchivesSpace. This work is the result 
of a community specification written through the participation of many users 
across the ArchivesSpace community, mostly notably Cory Nimer, Sue Luftschein, 
and Brad Westbrook. Through this work new fields and sub-records have been 
added to the agents schema, and staff and public interface views, imports, 
exports, and auxiliary functionality like agent merging have all been updated. 
There is also a new Light mode for agents, which provides the option for users 
to continue to work with agent records in the staff interface in a pared down 
view that is similar to that of ArchivesSpace versions prior to this one.

While the bulk of the changes in this release candidate relate to the agents 
module, the release candidate also contains improvements in some other areas of 
the application contributed by community developers and program team developers 
and contractors. Included among these are additional performance, backend and 
staff interface improvements courtesy of work Hudson Molonglo developers James 
Bullen, Mark Triggs, and Payten Giles did for Queensland State Archives as part 
of a larger project.

Every bit of testing and feedback helps us improves the release. We encourage 
you to test these improvements with your own data if you can. Some resources 
you may find helpful when testing include:


  *   Information from the webinar highlighting changes in v3.0.0: 
https://archivesspace.org/archives/6660


  *   Some new or updated user manual sections on the agents module (access 
requires your usual user manual login): 
https://archivesspace.atlassian.net/wiki/label/ArchivesSpaceUserManual/3agents

Thanks to the many community members who made contributions as we worked on 
bringing this expanded functionality to ArchivesSpace, including both 
individual archives staff and developers and our Testing and User Documentation 
sub-teams.

Please try this release candidate out and let us know at 
archivesspaceh...@lyrasis.org<mailto:archivesspaceh...@lyrasis.org> by April 7 
if you notice any problems with the specific areas addressed in this release, 
or if anything that was working before no longer is. The results of community 
testing will help us determine a release date.

Please get in touch if you have any questions. Thanks as always for your 
feedback and support.

Christine

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

[ASpaceOrgHomeMedium]

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

[Archivesspace_Users_Group] FW: Introducing the LYRASIS DataCite US Community

[Christine Di Bella]

Forwarded on behalf of our colleague Sheila Rabun at LYRASIS. Please contact 
Sheila (sheila.ra...@lyrasis.org) if you have 
questions.

---

Greetings all,

We are pleased to announce the official launch of the LYRASIS DataCite US 
Community, a 
national consortium/community of practice for non-profit organizations in the 
US dedicated to creating and maintaining DOIs (Digital Object Identifiers) for 
special collections, unique cultural heritage materials, research data, and 
other scholarly content via the DataCite DOI 
registration agency. This new program provides membership cost sharing, 
dedicated support, and a shared pathway for organizations to support open 
research infrastructure by using DOIs to make scholarly content and research 
materials more FAIR: Findable, 
Accessible, Interoperable, and Reusable.

Please join us for a free informational webinar "Introducing the LYRASIS 
DataCite US Community" to learn more about the benefits of DOIs, participation, 
and program details:

  *   When: Thurs. April 22, 12-1pm Pacific/ 1-2pm Mountain/ 2-3pm Central/ 
3-4pm Eastern
  *   Registration and details: 
https://www.lyrasis.org/Content/Pages/Event-Details.aspx?Eid=E0361D0F-F281-EB11-80EF-00155D0A2721
  *   Note: All registrants will receive a link to the webinar recording.

This program is designed to serve any non-profit institution in the US that is 
not already a DataCite member, and your organization does not need to be a 
LYRASIS member to participate. Additional information can be found online at 
https://www.lyrasis.org/programs/Pages/DataCite-US-Community-Membership.aspx. 
Feel free to contact me directly with any questions: 
sheila.ra...@lyrasis.org

Many thanks,
Sheila


Sheila Rabun, MA, MLIS [cid:image001.gif@01D7199F.34670460]  
https://orcid.org/-0002-1196-6279
Program Leader, Persistent Identifier Communities
Web: http://orcid-us.org
Twitter: https://twitter.com/USconsortium
Phone: 1-800-999-8558 x4809
Pronouns: she/her/hers
Recognize me: https://rescognito.com/-0002-1196-6279

[cid:image002.jpg@01D7199F.34670460]
[cid:image003.png@01D7199F.34670460]

I live, work, and learn on Kalapuya Ilihi, the traditional indigenous homeland 
of the Kalapuya people. Learn more about the Kalapuya 
people, 
their history, and the history of this land. Learn about land 
acknowledgments and ways to be in solidarity 
with Native nations beyond land acknowledgments.

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

[Archivesspace_Users_Group] reminder: March 15 is last day to apply for ArchivesSpace Diversity Partnership

[Christine Di Bella]

(Please share widely and with anyone you think may be interested)

A reminder that the last day to apply for the ArchivesSpace Diversity 
Partnership is Monday, March 15. More information about the program is below. 
Please reach out to us at 
archivesspaceh...@lyrasis.org<mailto:archivesspaceh...@lyrasis.org> if you have 
any questions. Thanks to those who have applied already!

--

The ArchivesSpace Diversity Partnership is a new program that offers support 
for implementing the ArchivesSpace application to institutions that are 
themselves or primarily serve communities underrepresented in the ArchivesSpace 
community. Participating organizations will receive, at no cost to them, 
ArchivesSpace membership, hosting with a Registered Service Provider, training, 
and user and technical support for the duration of a three-year term.

Eligible organizations include:

  *   academic Minority-Serving Institutions such as Historically Black 
Colleges and Universities (HBCUs), Hispanic Serving Institutions (HSIs), and 
Tribal Colleges and Universities
  *   non-profit or community archives primarily run by or serving BIPOC 
(Black, Indigenous, and People of Color)
  *   tribal archives

To be eligible for this new program, organizations cannot already be 
ArchivesSpace members or current hosting clients of any ArchivesSpace provider.

This program will launch with a small cohort of institutions on July 1, 2021. 
The three-year term will conclude on June 30, 2024.

More information about the ArchivesSpace Diversity Partnership, including 
information about how to apply, is available at 
https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/2049998863/ArchivesSpace+Diversity+Partnership.
 We also held an informational webinar outlining the program and the 
application process last month. The recording is available on our YouTube 
channel at https://youtu.be/B3SOgG4zThM. The deadline to submit an application 
for the program is March 15.

Members of the planning group are happy to answer questions or discuss 
potential applicant's situations at any time. Please contact us at 
archivesspaceh...@lyrasis.org<mailto:archivesspaceh...@lyrasis.org>. We really 
appreciate the interest in the program and look forward to receiving some great 
applications!

Sent on behalf of the Planning Group

Jessica Crouch, ArchivesSpace Community Engagement Coordinator

Christine Di Bella, ArchivesSpace Program Manager

Brittany Newberry, Atlanta University Center and ArchivesSpace User Advisory 
Council Chair

Sean Quimby, University of Pennsylvania and ArchivesSpace Governance Board Vice 
Chair
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] ArchivesSpace Diversity Partnership: March 15 deadline approaching

[Christine Di Bella]

(Please share widely and with anyone you think may be interested)

The deadline to apply for the ArchivesSpace Diversity Partnership is coming up 
on March 15. More information about the program is below. Please reach out to 
us at archivesspaceh...@lyrasis.org<mailto:archivesspaceh...@lyrasis.org> if 
you have any questions.

--

The ArchivesSpace Diversity Partnership is a new program that offers support 
for implementing the ArchivesSpace application to institutions that are 
themselves or primarily serve communities underrepresented in the ArchivesSpace 
community. Participating organizations will receive, at no cost to them, 
ArchivesSpace membership, hosting with a Registered Service Provider, training, 
and user and technical support for the duration of a three-year term.

Eligible organizations include:

  *   academic Minority-Serving Institutions such as Historically Black 
Colleges and Universities (HBCUs), Hispanic Serving Institutions (HSIs), and 
Tribal Colleges and Universities
  *   non-profit or community archives primarily run by or serving BIPOC 
(Black, Indigenous, and People of Color)
  *   tribal archives

To be eligible for this new program, organizations cannot already be 
ArchivesSpace members or current hosting clients of any ArchivesSpace provider.

This program will launch with a small cohort of institutions on July 1, 2021. 
The three-year term will conclude on June 30, 2024.

More information about the ArchivesSpace Diversity Partnership, including 
information about how to apply, is available at 
https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/2049998863/ArchivesSpace+Diversity+Partnership.
 We also held an informational webinar outlining the program and the 
application process last month. The recording is available on our YouTube 
channel at https://youtu.be/B3SOgG4zThM. The deadline to submit an application 
for the program is March 15.

Members of the planning group are happy to answer questions or discuss 
potential applicant's situations at any time. Please contact us at 
archivesspaceh...@lyrasis.org<mailto:archivesspaceh...@lyrasis.org>. We really 
appreciate the interest in the program and look forward to receiving some great 
applications!

Sent on behalf of the Planning Group

Jessica Crouch, ArchivesSpace Community Engagement Coordinator

Christine Di Bella, ArchivesSpace Program Manager

Brittany Newberry, Atlanta University Center and ArchivesSpace User Advisory 
Council Chair

Sean Quimby, University of Pennsylvania and ArchivesSpace Governance Board Vice 
Chair
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] new program: ArchivesSpace Diversity Partnership

[Christine Di Bella]

(We'll be announcing this on various listservs in the coming days, but please 
feel free to share widely across your networks and with anyone you think may be 
interested. As mentioned in the announcement we're also hosting an 
informational webinar on February 10 and available for questions anytime.)



In the wake of the George Floyd and Breonna Taylor murders, and in the spirit 
of protest that followed, the ArchivesSpace community began a conversation last 
spring about what it could do to promote diversity and inclusion while 
combating systemic racism in our field. That continuing conversation has led to 
a series of 
initiatives<https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/1737490437/Anti-racism+and+Inclusion+Initiatives+Progress>
 that we will undertake in the coming years, including the ArchivesSpace 
Diversity Partnership.


The ArchivesSpace Diversity Partnership is a new program that offers support 
for implementing the ArchivesSpace application to institutions that are 
themselves or primarily serve communities underrepresented in the ArchivesSpace 
community. Participating organizations will receive, at no cost to them, 
ArchivesSpace membership, hosting with a Registered Service Provider, training, 
and user and technical support for the duration of a three-year term.


Eligible organizations include:

  *   academic Minority-Serving Institutions such as Historically Black 
Colleges and Universities (HBCUs), Hispanic Serving Institutions (HSIs), and 
Tribal Colleges and Universities
  *   non-profit or community archives primarily run by or serving BIPOC 
(Black, Indigenous, and People of Color)
  *   tribal archives


To be eligible for this new program, organizations cannot already be 
ArchivesSpace members or current hosting clients of any ArchivesSpace provider.


This program will launch with a small cohort of institutions on July 1, 2021. 
The three-year term will conclude on June 30, 2024.


More information about the ArchivesSpace Diversity Partnership, including 
information about how to apply, is available at 
https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/2049998863/ArchivesSpace+Diversity+Partnership.
 Members of the planning group are happy to talk about the program at any time 
- please contact us at 
archivesspaceh...@lyrasis.org<mailto:archivesspaceh...@lyrasis.org>. Potential 
applicants who are interested in the experience of using ArchivesSpace at an 
underrepresented institution can contact Brittany Newberry 
(bnewbe...@auctr.edu<mailto:bnewbe...@auctr.edu>). She is happy to talk about 
Atlanta University Center's experience implementing ArchivesSpace as an HBCU.


We are also holding an informational webinar on February 10 at 2:00 p.m. 
ET/11:00 a.m. PT. Registration for the webinar is available at 
https://lyrasis.zoom.us/webinar/register/WN_f6s6-6JeT_6q6I_TgIqWVA. The webinar 
will be recorded.

Thanks to all who participated in the discussions and feedback opportunities 
that have made this program possible. Please get in touch if you have questions 
or ideas on this or the other initiatives our community will be undertaking to 
make ArchivesSpace more diverse and inclusive.

Christine


Sent on behalf of the Planning Group


Jessica Crouch, ArchivesSpace Community Engagement Coordinator

Christine Di Bella, ArchivesSpace Program Manager

Brittany Newberry, Atlanta University Center and ArchivesSpace User Advisory 
Council Chair

Sean Quimby, University of Pennsylvania and ArchivesSpace Governance Board Vice 
Chair

Madeline Sheldon, LYRASIS Digital Technology Services

------

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905


[ASpaceOrgHomeMedium]



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

[Archivesspace_Users_Group] Grant Funds Available through LYRASIS

[Christine Di Bella]

Shared on behalf of our colleagues in LYRASIS. The informational webinar has 
already happened, but please contact Leigh Grinstead at 
catalystf...@lyrasis.org if you have questions 
or project ideas.



It is that time of year again and we’re excited to announce that 2021 LYRASIS 
Catalyst 
Fund
 application cycle is now open and we’re accepting proposals and ideas through 
February 19. That’s where I hope you can come in, by forwarding this email 
announcement out to your colleagues, Tweet—heck, mention it on any social media 
platform—and help us spread the word. The more buzz, the better!

The application is only two-pages in length, and our program lead will meet 
with institutions to discuss concepts, provide feedback, and review 
applications ahead of time.

For those of you that may be unfamiliar, the Catalyst Fund is an award program 
to test and try new ideas and innovative projects submitted by LYRASIS members. 
2021 applications will be reviewed by librarians, archivists, and museum 
professionals during March and April with recipients announced in June 2021. 
Only LYRASIS 
Members
 may apply for the Catalyst Fund. However, LYRASIS members may partner with 
non-member institutions and can act as the lead applicant for a collaboration 
or team pulled together for the purposes of the grant.

Apply 
Today

Criteria for Consideration

This year, in addition to our general call for proposals, the Catalyst Fund is 
piloting a new thematic track and welcoming applications focused specifically 
on Open-Source Software (OSS). Applications in this track will still apply the 
same core values and creative concepts of the Fund: to test-and-try new 
approaches to shared problems; focusing on cross institutional collaboration; 
issues such as diversity, equity, inclusion, accessibility; other 
community-driven projects; and projects having community impact.

The OSS track will look for projects to help the advancement, evolution, 
expansion, and/or application of OSS to provide innovation solutions for the 
LYRASIS community. Applications do not need to address this theme, but funds 
have been reserved specifically for those that do. Click 

 to view the criteria used by the Leaders Circle for consideration and 
selection of projects to fund.

What if you are Not Ready to Apply This Year? Then Become a Reviewer!

Are you a critical thinker interested in contributing to innovation within the 
library, archives, museum, and complementary research communities? If so, 
please consider sharing your knowledge, expertise, and experience by reviewing 
applications
 to the Catalyst Fund. Reviewers will rate applications and provide feedback 
for consideration by the Leaders Circle in making the final selections.

For more information about the Catalyst Fund

Join us for Catalyst Fund: The Application Process & Overview 

Re: [Archivesspace_Users_Group] Language notes

[Christine Di Bella]

Hi Jennifer,

I think the resolution to the previous question happened off the list. It 
turned out that there was language information on the archival objects 
previously, but that didn't become clear until the upgrade because it was more 
prominent afterwards than before.

The site cleaned it up with some MySQL queries. Let me know if you'd like help 
walking through that process and I can turn this into a tech support ticket.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905


[ASpaceOrgHomeMedium]



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Sharp, 
Jennifer
Sent: Wednesday, January 13, 2021 10:39 AM
To: archivesspace_users_group@lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Language notes

Hi,

I have a question regarding the language notes. We recently upgraded from 2.6 
to 2.8.1, and I learned afterward about the language note changes that came 
with 2.7. We are in the process of doing some heavy editing to the finding aid 
for our largest collection, and it looks like every time we edit one of the 
Archival Objects, it automatically adds the language information. I've tried a 
few things, and haven't been able to get rid of it. Would either of the 
batch_update_langmaterials plugins help with this?

I found that a similar question was asked in December 
2019<http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/2019-December/007188.html>,
 but there don't seem to be any group replies.

Thanks,
Jennifer

---
Jennifer Sharp, MSI
Archivist, Hartford History Center
Hartford Public Library
jsh...@hplct.org<mailto:jsh...@hplct.org>
o: 860.695.6332
c: 860.929.6915

VIEW OUR EXHIBIT: October 1920: A Celebration of the Centennial of Women's 
Suffrage

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

Re: [Archivesspace_Users_Group] Digital object import behavior 2.8.0 vs. 2.8.1

[Christine Di Bella]

Hi John,

Could you share the spreadsheet you're testing for issue 1? I'd like to take a 
closer look to understand what you're describing since off the top of my head 
it's not as familiar to me. I know your second issue was specifically remedied 
in 2.8.1.

In general, 2.8.1 added new functionality to the spreadsheet importer and fixed 
various bugs that people encountered when using a wider range of real world 
data than was used in the 2.8.0 testing. Upgrading to 2.8.1 is almost always 
going to be the best choice to address issues encountered with the importer in 
2.8.0.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905


[ASpaceOrgHomeMedium]



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Rees, 
John (NIH/NLM) [E]
Sent: Wednesday, December 9, 2020 10:14 AM
To: archivesspace_users_group@lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Digital object import behavior 2.8.0 vs. 
2.8.1

Hi all,

We're on v.2.8.0 and are experimenting with the new Digital Object spreadsheet 
importer to append DO's to existing archival objects.

In 2.8.0, I understand that import will fail where another DO already exists 
which is a use case I'm testing. However, using the ASpace 2.8.1 sandbox I get 
the same processing error, but the job is still successful when there are 
pre-existing DOs. Is that expected behavior? See my real-world example at 
http://test.archivesspace.org/staff/resources/193/edit#tree::archival_object_43056
 (JPR4 and 5 are the new imports)

Question 2: in v.2.8.0, the import process fails unless either file URN or 
thumbnail URN is included. This is not documented as a required element. With 
2.8.1 imports with these fields empty run fine. Is this expected behavior? We 
are importing DOs as a pre-flight exercise and don't have URNs yet. We'd have 
to add dummy data and deleted afterwards.

I'm reckoning the solution to my 2.8.0 problems is moving to 2.8.1?

Thanks,
John

John P. Rees
Archivist and Digital Resources Manager
History of Medicine Division
National Library of Medicine
301-827-4510
Teleworking M-F 8:00AM - 4:30PM Eastern Time each day until further notice





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

Re: [Archivesspace_Users_Group] Top Container Searching

[Christine Di Bella]

Hello Wendy,

As you note, various improvements have been made to the Manage Top Containers 
searching in recent releases. (A big thank you to the folks at Harvard for 
their recent contributions in this area, including making the terms used in the 
last search sticky.) Across the application, we also added resource identifiers 
to the typeahead/linker display area in 2.8.1 to make it easier for users to 
identify which resource is the one of interest. There’s more information about 
using the Manage Top Containers area in the ArchivesSpace Help Center 
(https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/917045261/ArchivesSpace+Help+Center).

You’re correct that right now the typeaheads do a keyword search across all 
resource records as a user is typing along. Nothing is currently planned to 
change that, but please feel free to submit a feature request to JIRA if you’d 
like to suggest this behavior be changed. There’s information about how to do 
that at 
https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/19202060/How+to+Request+a+New+Feature.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905


[ASpaceOrgHomeMedium]



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Wendy 
Scheir
Sent: Wednesday, December 2, 2020 3:25 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Top Container Searching

Hi again,

I sent this inquiry right before the Thanksgiving holiday, so it may have been 
buried in people's inboxes. Can anyone shed light on my question about existing 
and planned top container functionality?

All best,
Wendy



WENDY SCHEIR
DIRECTOR

[https://docs.google.com/uc?export=download=16Nic6T4ZK1k1BhLOUToez7KP5Tzv8f9o=0B4enrSUaFYtfdnV0R3E3bEkvek9LUVdsbkRIVUNJaXh1MU9VPQ]

66 5TH AVENUE, NEW YORK, NY 10011
sche...@newschool.edu<mailto:sche...@newschool.edu>

T 212.229.5942 x2888

Explore the Archives<http://library.newschool.edu/archives> | Digital 
Collections from the Archives<http://digitalarchives.library.newschool.edu/> | 
New School Histories<http://newschoolhistories.org/> | 
@tnsarchives<https://twitter.com/tnsarchives>


On Wed, Nov 25, 2020 at 2:12 PM Wendy Scheir 
mailto:sche...@newschool.edu>> wrote:
Hi,

We've started working with v2.8.1 and welcome the improvements to top container 
searching. We noticed that the Resource field does not limit searches to 
Resource title, but rather is a keyword search across resources. Are there 
plans to add the capability of limiting search results to resource title? This 
functionality would reduce a result list from potentially hundreds of records 
to a handful, which would be very useful to us, as it would, I'd imagine, to 
other ASpace members.

Many thanks,

Wendy



WENDY SCHEIR
DIRECTOR

[https://docs.google.com/uc?export=download=16Nic6T4ZK1k1BhLOUToez7KP5Tzv8f9o=0B4enrSUaFYtfdnV0R3E3bEkvek9LUVdsbkRIVUNJaXh1MU9VPQ]

66 5TH AVENUE, NEW YORK, NY 10011
sche...@newschool.edu<mailto:sche...@newschool.edu>

T 212.229.5942 x2888

Explore the Archives<http://library.newschool.edu/archives> | Digital 
Collections from the Archives<http://digitalarchives.library.newschool.edu/> | 
New School Histories<http://newschoolhistories.org/> | 
@tnsarchives<https://twitter.com/tnsarchives>
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] ArchivesSpace v2.8.1 now available

[Christine Di Bella]

ArchivesSpace is announcing the availability of v2.8.1. You can download it at 
https://github.com/archivesspace/archivesspace/releases/tag/v2.8.1.

This release includes improvements to the spreadsheet importer, additional 
settable record type preferences, some bug fixes and small feature 
improvements, and a number of infrastructure upgrades. Included among these are 
some performance, indexer, and small backend and staff interface improvements 
courtesy of work Hudson Molonglo did for ArchivesSpace member institution 
Queensland State Archives as part of a larger project.

For spreadsheet importer fans: Some changes have been made to the spreadsheet 
importer in this release to extend its functionality and improve its 
performance, especially with large spreadsheets. Of particular note: there is 
now a validation option so that a user can do a test run with a file, providing 
the opportunity to clean up any errors outside ArchivesSpace before doing the 
actual import; the importer now accepts either Excel spreadsheets or CSV files 
that use the templates at 
https://github.com/archivesspace/archivesspace/tree/master/templates; and, 
while it is accessed from a resource record or resource component as before, 
the import now runs as a background job so that it can more easily handle large 
files and to make the log file downloadable and saved within ArchivesSpace. 
Also, a number of bugs that were introduced with the conversion of the 
spreadsheet from a plugin to ArchivesSpace have been fixed for this release.

Thanks very much to community members Andrew Morrison, Blake Carver, Brian 
Harrington, Dee Dee Crema, Douglas Simon, Greg Wiedeman, James Bullen, Jeremy 
Markowitz, Joshua Shaw, Mark Triggs, Noah Geraci, Payten Giles, and Steve 
Majewski for their code contributions to this release. Program team members 
Lora Woodford and Mark Cooper wrote and reviewed code and supervised the work 
of Bobbi Fox and Brian Zelip, who worked with us as contractors on this 
release. This release would, of course, not have been possible without the hard 
work of so many of our community groups, including our Development 
Prioritization, Testing, Technical Documentation, and User Documentation 
sub-teams, and Core Committers Group.

Information on upgrading to a new version of ArchivesSpace is available at 
https://archivesspace.github.io/tech-docs/administration/upgrading.html. If you 
have any difficulties, please let us know.

Thanks to all for their help and support. We are expecting to put out one more 
release in 2020, which will be almost exclusively focused on changes to the 
Agents module. You will hear more from us about that in the weeks to come.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905


[ASpaceOrgHomeMedium]

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

[Archivesspace_Users_Group] release candidate available - ArchivesSpace v2.8.1-RC1

[Christine Di Bella]

Hello ArchivesSpace members,

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

This release candidate includes improvements to the spreadsheet importer, 
additional settable record type preferences, some bug fixes and small feature 
improvements, additional translations for the public interface and reports, and 
a number of infrastructure upgrades. Included within these are a number of 
performance, indexer, and small backend and staff interface improvements 
courtesy of work Hudson Molonglo developers James Bullen, Mark Triggs, and 
Payten Giles did for Queensland State Archives as part of a larger project.

For spreadsheet importer fans: Some changes have been made to the spreadsheet 
importer in this release candidate to extend its functionality and improve its 
performance, especially with large spreadsheets. Of particular note: there is 
now a validation option so that a user can do a test run with a file, providing 
the opportunity to clean up any errors outside ArchivesSpace before doing the 
actual import; the importer now accepts either Excel spreadsheets or CSV files 
that use the templates at 
https://github.com/archivesspace/archivesspace/tree/master/templates; and, 
while it is accessed from a resource record or resource component as before, 
the import now runs as a background job so that it can more easily handle large 
files and to make the log file downloadable and saved within ArchivesSpace. 
Also, a number of bugs that were introduced with the conversion of the 
spreadsheet from a plugin to ArchivesSpace have been fixed for this release.

We encourage you to test these improvements, especially for the spreadsheet 
importer, with your own data if you can. (Hey, there are worse ways to pass 
time this week than importing a few gnarly spreadsheets!) Every bit of testing 
and feedback helps us ensure that the changes are doing what they should and 
improves the release.

Thanks to the many community members who made contributions to this release, 
including both individual archives staff and developers, as well as our 
Development Prioritization sub-team, Testing sub-team, and Core Committers 
Group. It also benefitted from some friendly 
Hacktoberfest<https://archivesspace.org/archives/6563> competition among the 
ArchivesSpace and extended LYRASIS team.

Please try this release candidate out over the next few days and let us know at 
archivesspaceh...@lyrasis.org<mailto:archivesspaceh...@lyrasis.org> by November 
9 if you notice any problems with the specific areas addressed in this release, 
or if anything that was working before no longer is. Assuming good testing 
results we're aiming to put out the release itself next week.

Please get in touch if you have any questions. Thanks as always for your 
feedback and support.

Christine

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

[ASpaceOrgHomeMedium]

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

Re: [Archivesspace_Users_Group] spreadsheet imports in 2.8v SUI

[Christine Di Bella]

Hello Anna,

The team was talking about this yesterday. We’re expecting to put out a release 
with the improvements to the spreadsheet importer in early November.

Christine

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Anna 
Robinson-Sweet
Sent: Wednesday, October 7, 2020 5:11 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] spreadsheet imports in 2.8v SUI

Hi Christine,

Following up on your exchange with Wendy regarding the improved spreadsheet 
importer. Do you know when we can expect the next version of ArchivesSpace will 
be released?

Thanks,
Anna

On Thu, Oct 1, 2020 at 9:45 AM Christine Di Bella 
mailto:christine.dibe...@lyrasis.org>> wrote:
Hi Wendy,

That’s great to hear. The improved importer will be in the next version of 
ArchivesSpace.

I understand that Bobbi Fox, the original developer of this functionality, has 
been in touch with you. She confirmed that what you’re trying to do is not 
supported. Now that the importer is in ArchivesSpace, new feature requests 
would be evaluated through our regular development prioritization process. You 
can file a feature request by following the instructions at 
https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/19202060/How+to+Request+a+New+Feature.

Christine

From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 On Behalf Of Wendy Scheir
Sent: Wednesday, September 30, 2020 3:28 PM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] spreadsheet imports in 2.8v SUI

Hi Christine,

Thank you for your reply. Yes! I was able to successfully import both 
spreadsheets in the sandbox! No error messages. Is there a patch that we can 
apply to our instance to make this work for us?

This does, however, lead me to another question. We are hoping to use the File 
version URI field to enter an internal file path (not an actual link), and I 
thought that if I used column BL on the import spreadsheet (column K on the DO 
spreadsheet) that the file path would populate the URI field--alas, it doesn't. 
But I don't see another field on the spreadsheet where one can place the 
non-linking file path to have it populate the URI field. Is there one that I'm 
just not interpreting properly?

Many thanks,
Wendy



WENDY SCHEIR
DIRECTOR

[https://docs.google.com/uc?export=download=16Nic6T4ZK1k1BhLOUToez7KP5Tzv8f9o=0B4enrSUaFYtfdnV0R3E3bEkvek9LUVdsbkRIVUNJaXh1MU9VPQ]

66 5TH AVENUE, NEW YORK, NY 10011
sche...@newschool.edu<mailto:sche...@newschool.edu>

T 212.229.5942 x2888

Explore the Archives<http://library.newschool.edu/archives> | Digital 
Collections from the Archives<http://digitalarchives.library.newschool.edu/> | 
New School Histories<http://newschoolhistories.org/> | 
@tnsarchives<https://twitter.com/tnsarchives>


On Wed, Sep 30, 2020 at 2:43 PM Christine Di Bella 
mailto:christine.dibe...@lyrasis.org>> wrote:
Hi Wendy,

Can you try importing your file into a dummy record on our test server: 
http://test.archivesspace.org/staff/? (username admin, password admin)

We’ve been working on a number of changes to the importer based on feedback 
since 2.8.0. The pretty_inspect message usually means there’s a data error that 
should be caught by the logging process that shows up post-import. Some errors 
were not accounted for in the version in 2.8.0 so you get that message instead 
of the error, but should be there. The digital objects issue is not familiar to 
me, but I’m wondering if that may be different there too.

You’ll start the import the same way you usually would on the test server, but 
it will move the process over to a background job so that it can run more 
quickly and the log is more easily downloadable afterwards. If you need any 
more guidance on that, please let me know.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905


[ASpaceOrgHomeMedium]



From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 On Behalf Of Wendy Scheir
Sent: Wednesday, September 30, 2020 2:14 PM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] spreadsheet imports in 2.8v SUI

Hi,

In addition to the DO import spreadsheet error that I indicated in my recent 
email re: duplicate field codes, another error message I'm receiving in trying 
to import the DOs is: "{"error":"undefined method `pretty_inspect' for #"}"

I'd be grateful 

Re: [Archivesspace_Users_Group] spreadsheet imports in 2.8v SUI

[Christine Di Bella]

Hi Wendy,

That’s great to hear. The improved importer will be in the next version of 
ArchivesSpace.

I understand that Bobbi Fox, the original developer of this functionality, has 
been in touch with you. She confirmed that what you’re trying to do is not 
supported. Now that the importer is in ArchivesSpace, new feature requests 
would be evaluated through our regular development prioritization process. You 
can file a feature request by following the instructions at 
https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/19202060/How+to+Request+a+New+Feature.

Christine

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Wendy 
Scheir
Sent: Wednesday, September 30, 2020 3:28 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] spreadsheet imports in 2.8v SUI

Hi Christine,

Thank you for your reply. Yes! I was able to successfully import both 
spreadsheets in the sandbox! No error messages. Is there a patch that we can 
apply to our instance to make this work for us?

This does, however, lead me to another question. We are hoping to use the File 
version URI field to enter an internal file path (not an actual link), and I 
thought that if I used column BL on the import spreadsheet (column K on the DO 
spreadsheet) that the file path would populate the URI field--alas, it doesn't. 
But I don't see another field on the spreadsheet where one can place the 
non-linking file path to have it populate the URI field. Is there one that I'm 
just not interpreting properly?

Many thanks,
Wendy



WENDY SCHEIR
DIRECTOR

[https://docs.google.com/uc?export=download=16Nic6T4ZK1k1BhLOUToez7KP5Tzv8f9o=0B4enrSUaFYtfdnV0R3E3bEkvek9LUVdsbkRIVUNJaXh1MU9VPQ]

66 5TH AVENUE, NEW YORK, NY 10011
sche...@newschool.edu<mailto:sche...@newschool.edu>

T 212.229.5942 x2888

Explore the Archives<http://library.newschool.edu/archives> | Digital 
Collections from the Archives<http://digitalarchives.library.newschool.edu/> | 
New School Histories<http://newschoolhistories.org/> | 
@tnsarchives<https://twitter.com/tnsarchives>


On Wed, Sep 30, 2020 at 2:43 PM Christine Di Bella 
mailto:christine.dibe...@lyrasis.org>> wrote:
Hi Wendy,

Can you try importing your file into a dummy record on our test server: 
http://test.archivesspace.org/staff/? (username admin, password admin)

We’ve been working on a number of changes to the importer based on feedback 
since 2.8.0. The pretty_inspect message usually means there’s a data error that 
should be caught by the logging process that shows up post-import. Some errors 
were not accounted for in the version in 2.8.0 so you get that message instead 
of the error, but should be there. The digital objects issue is not familiar to 
me, but I’m wondering if that may be different there too.

You’ll start the import the same way you usually would on the test server, but 
it will move the process over to a background job so that it can run more 
quickly and the log is more easily downloadable afterwards. If you need any 
more guidance on that, please let me know.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905


[ASpaceOrgHomeMedium]



From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 On Behalf Of Wendy Scheir
Sent: Wednesday, September 30, 2020 2:14 PM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] spreadsheet imports in 2.8v SUI

Hi,

In addition to the DO import spreadsheet error that I indicated in my recent 
email re: duplicate field codes, another error message I'm receiving in trying 
to import the DOs is: "{"error":"undefined method `pretty_inspect' for #"}"

I'd be grateful for any insight you can provide on these issues.

Many thanks,
Wendy

On Wed, Sep 30, 2020 at 1:28 PM Wendy Scheir 
mailto:sche...@newschool.edu>> wrote:
Hi,

In attempting to upload spreadsheets into ASpace using the Load via Spreadsheet 
functionality in the 2.8v SUI, I'm running into 2 issues and hoping that 
someone can shed some light. In each case, I'm using the import spreadsheets 
downloaded from Github:

(1)  Using the general import spreadsheet to upload a collection that includes 
digital objects--fields BJ (digital_object_id), BK (digital_object_title), BL 
(digital_object_link) the archival objects imported, but not the digital 
objects.

(2) Using the DO import spreadsheet (again, downloaded directly from Github), 
I'm getting the error message "This spreadsheet has duplicate Archive Space 
Field codes:  , , , , , , , , , , , , ," However, I don't see any obvious 
duplicate field co

Re: [Archivesspace_Users_Group] spreadsheet imports in 2.8v SUI

[Christine Di Bella]

Hi Wendy,

Can you try importing your file into a dummy record on our test server: 
http://test.archivesspace.org/staff/? (username admin, password admin)

We’ve been working on a number of changes to the importer based on feedback 
since 2.8.0. The pretty_inspect message usually means there’s a data error that 
should be caught by the logging process that shows up post-import. Some errors 
were not accounted for in the version in 2.8.0 so you get that message instead 
of the error, but should be there. The digital objects issue is not familiar to 
me, but I’m wondering if that may be different there too.

You’ll start the import the same way you usually would on the test server, but 
it will move the process over to a background job so that it can run more 
quickly and the log is more easily downloadable afterwards. If you need any 
more guidance on that, please let me know.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905


[ASpaceOrgHomeMedium]



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Wendy 
Scheir
Sent: Wednesday, September 30, 2020 2:14 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] spreadsheet imports in 2.8v SUI

Hi,

In addition to the DO import spreadsheet error that I indicated in my recent 
email re: duplicate field codes, another error message I'm receiving in trying 
to import the DOs is: "{"error":"undefined method `pretty_inspect' for #"}"

I'd be grateful for any insight you can provide on these issues.

Many thanks,
Wendy

On Wed, Sep 30, 2020 at 1:28 PM Wendy Scheir 
mailto:sche...@newschool.edu>> wrote:
Hi,

In attempting to upload spreadsheets into ASpace using the Load via Spreadsheet 
functionality in the 2.8v SUI, I'm running into 2 issues and hoping that 
someone can shed some light. In each case, I'm using the import spreadsheets 
downloaded from Github:

(1)  Using the general import spreadsheet to upload a collection that includes 
digital objects--fields BJ (digital_object_id), BK (digital_object_title), BL 
(digital_object_link) the archival objects imported, but not the digital 
objects.

(2) Using the DO import spreadsheet (again, downloaded directly from Github), 
I'm getting the error message "This spreadsheet has duplicate Archive Space 
Field codes:  , , , , , , , , , , , , ," However, I don't see any obvious 
duplicate field codes in Row 4 of the spreadsheet.
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] FW: NGLP “Values and Principles Framework and Assessment Checklist” Released for Public Comment

[Christine Di Bella]

Forwarded on behalf of our colleagues at Educopia. Please contact Katherine 
Skinner if you have questions.

From: Katherine Skinner mailto:kather...@educopia.org>>
Sent: Tuesday, September 1, 2020 12:03 PM
To: John Herbert mailto:john.herb...@lyrasis.org>>; 
Laurie Arp mailto:laurie@lyrasis.org>>; Kristen 
Ratan mailto:kris...@strategiesos.org>>; Catherine 
Mitchell mailto:catherine.mitch...@ucop.edu>>
Subject: NGLP “Values and Principles Framework and Assessment Checklist” 
Released for Public Comment



(apologies for cross-posting!)

Dear colleagues,

The Next Generation Library Publishing project (NGLP) invites community 
feedback on the draft release of the Values and Principles Framework and 
Assessment Checklist tools produced 
to assess and incentivize stronger alignment between publishing tools, 
services, and platforms and the scholarly communities and publics they 
ultimately serve. Pending public feedback, we plan to refine and issue this 
tool in 2021 for broad use.

We invite feedback and engagement via the open access Commonplace Publication 
(hosted on the PubPub platform).  
You can access the framework and the checklist freely; you will need to set up 
an account with Commonplace and PubPub in order to make comments directly in 
the documents. You are also welcome to contact its lead author, Katherine 
Skinner, by email to share comments or ideas. 
The draft is open for public comment until September 30, 2020.

About the NGLP Project

The Next Generation Library Publishing 
project (led by 
Educopia Institute, California Digital Library, and Stratos, in close 
collaboration with COAR, LYRASIS, and Longleaf Services, and generously funded 
by Arcadia), seeks to improve the publishing 
pathways and choices available to authors, editors, and readers through 
strengthening, integrating, and scaling up scholarly publishing infrastructure 
to support library publishers. In addition to developing interoperable 
publishing tools and workflows, our team is exploring how to create community 
hosting models that align explicitly and demonstratively with academic values.

More about the Values and Principles Assessment Tool

This Framework and Assessment Checklist and its affiliated documentation have 
been prepared by Katherine Skinner and Sarah Lippincott and edited by Nancy 
Adams, Hannah Ballard, Terra Graziani, Jennifer Kemp, Brandon Locke, Catherine 
Mitchell, Kristen Ratan, Oya Reiger, Kathleen Shearer, John Sherer, Nick 
Shockey, Eric van Rijn, and Sarah Wipperman.

This publication is also related to the Encouraging Adherence to Values and 
Principles White Paper (March 
2020), which the NGLP team issued 
for public comment in March 2020,

If you have any questions about the Framework and Assessment Checklist, please 
contact Katherine Skinner 
mailto:kather...@educopia.org>>.

With many thanks, and best wishes,
Katherine Skinner, PhD
Executive Director, Educopia Institute
http://educopia.org
Currently working at reduced capacity while balancing 
kids-school-work-life-2020...please text me if you are not hearing from me 
quickly!

Working from Greensboro, NC
kather...@educopia.org | 404 783 2534

Pronouns: she/her

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

[Archivesspace_Users_Group] FW: US DataCite Community call for interest

[Christine Di Bella]

Forwarding on behalf of our colleague Sheila Rabun at LYRASIS. Please get in 
touch with her at sheila.ra...@lyrasis.org<mailto:sheila.ra...@lyrasis.org> 
with questions.

Christine

From: Sheila Rabun 
Sent: Tuesday, September 8, 2020 11:45 AM
To: Christine Di Bella 
Subject: US DataCite Community call for interest

Hi Christine, the message below is a call for interest in a potential US 
DataCite Community administered by LYRASIS - if you can please forward to the 
ArchivesSpace community, that will be wonderful. Many thanks! -Sheila
---

To: ArchivesSpace community

Subject: US DataCite Community call for interest


Greetings all,

To bolster our existing programs, LYRASIS is considering establishing a 
national DataCite<https://datacite.org/mission.html> Community, which would 
allow non-profit organizations in the US to create DOIs* (digital object 
identifiers) for digital assets created and hosted locally for a reduced fee as 
part of DataCite's consortium member model.

We are checking in with you to gauge interest in such a program, which we would 
anticipate to begin in January 2021 with an anticipated annual per-institution 
fee of $1,600, plus a DOI fee depending on the number of DOIs created at each 
institution:

Annual DOI Fees:

  *   1-1,999 DOIs created = $.95 per DOI
  *   2,000-10,000 DOIs created = $1,900 flat rate
  *   Any organizations creating more than 10,000 DOIs per year would need to 
operate as a direct member with DataCite.

The more institutions participating, and the more DOIs created, the more 
everyone can potentially save due to DataCite's consortium fee caps. This 
program would provide a savings of approximately 40% per participating 
institution compared to what any single organization might pay for becoming a 
direct member with DataCite.

If your organization would be interested in joining our DataCite consortium, 
please complete this brief form<https://forms.gle/sKNNN44KpvtHuBwc8> by Sept. 
25 to let us know.

Many thanks, on behalf of the LYRASIS Content & Scholarly Communication team!

*DOIs are unique, persistent identifiers that can be created by institutions 
through a DOI registration service (such as DataCite) and assigned to digital 
works in order to make them easier to find on the web in a reliable manner over 
time. DOIs are commonly assigned to objects such as digital journal articles, 
white papers, OERs (open educational resources), slide decks, posters, or other 
works on the web. For example, the DOI for the document "Recommendations for 
Supporting ORCID in Repositories" is https://doi.org/10.23640/07243.274.


Sheila Rabun, MA, MLIS [cid:image001.gif@01D685BC.5D001280]  
https://orcid.org/-0002-1196-6279
ORCID US Community Specialist
Web: http://orcid-us.org<http://orcid-us.org/>
Twitter: https://twitter.com/USconsortium
Phone: 1-800-999-8558 x4809
Pronouns: she/her/hers

[cid:image004.jpg@01D685ED.3113E8A0]
[cid:image005.png@01D685ED.3113E8A0]

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

Re: [Archivesspace_Users_Group] Jobs indexing error

[Christine Di Bella]

Hi Patrick (and all),

Just a mention that we discovered this issue after the release of 2.8.0 and 
added this to the release notes:

added July 30, 2020: Due the addition of background jobs to the index in this 
release, plugins that create background jobs will cause an indexing loop if 
they are disabled. While the vast majority of users will not encounter this, it 
is most likely to be encountered if users have run the language cleanup plugins 
released in conjunction with 2.6.0. The workaround for now is to reenable the 
plugin (or keep it enabled if the job is run in 2.8.0). The plugin itself 
should not be re-run. This issue will be corrected in a future release.

You can either delete the jobs as Blake suggests or reenable the plugin. We 
expect to have this issue corrected in the next release.

Apologies for the inconvenience,
Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905


[ASpaceOrgHomeMedium]



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of 
Galligan, Patrick
Sent: Tuesday, August 25, 2020 9:43 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Jobs indexing error

Blake,

Yeah, I’m guessing that the `asck` plugin we installed to check data a year ago 
makes those jobs invalid if the plugin isn’t installed.

Which is annoying.

Thanks for the help!

From: 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of Blake Carver 
mailto:blake.car...@lyrasis.org>>
Reply-To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Date: Tuesday, August 25, 2020 at 9:31 AM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Jobs indexing error

***External*** This email originated from outside of the organization. Do not 
click links or open attachments unless you recognize the sender and know the 
content is safe.***


 You could just get rid of the aspace_check_job jobs. (back up the DB just in 
case)

select * job where job_blob like '%aspace_check_job%';

Then:

delete FROM job where job_blob like '%aspace_check_job%';




From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of Galligan, Patrick 
mailto:pgalli...@rockarch.org>>
Sent: Tuesday, August 25, 2020 9:05 AM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] Jobs indexing error


Hi all,



Posting here in the off chance someone has run into this before. We’re testing 
out AS version 2.8, coming from 2.6.0 and running into a weird issue.



Indexing works fine until we get to the job records section of indexing, and 
then we run into an unhandled exception ultimately stops indexing from 
finishing, and it just starts up again at resource records after finishing the 
jobs.



I’ve attached the relevant section of our log.



Any ideas on how to fix this? I could just delete all of our job records from 
the table, but that seems like a bad solution to this issue.



Thanks,

Patrick Galligan

He/Him

Digital Archivist

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

[Archivesspace_Users_Group] Take a break with ArchivesSpace on Fridays

[Christine Di Bella]

Dear ArchivesSpace Users,



After a short hiatus, we’ll be back hosting another casual open call via zoom 
at 12pm ET tomorrow. With no set agenda or presentation for these calls, this 
forum is an opportunity to connect, chat and recharge. Use this as a time to 
get help or talk about ArchivesSpace (or anything else) in an informal setting 
or just have a beverage with other ArchivesSpace users during this stressful 
time.


When: Fridays
Time: 12:00 p.m. – 1:00 p.m. ET (9:00 a.m. – 10:00 a.m. PT)
Where: Zoom

Join the call via the information below:


Join Zoom Meeting

https://lyrasis.zoom.us/j/281962467



Meeting ID: 281 962 467



One tap mobile

+19292056099,,281962467# US (New York)

+13126266799,,281962467# US (Chicago)



Dial by your location

+1 929 205 6099 US (New York)

+1 312 626 6799 US (Chicago)

+1 301 715 8592 US

+1 346 248 7799 US (Houston)

+1 669 900 6833 US (San Jose)

+1 253 215 8782 US

888 475 4499 US Toll-free

877 853 5257 US Toll-free

Meeting ID: 281 962 467

Find your local number: https://lyrasis.zoom.us/u/awkFNWPxh

We seek to provide a welcoming, fun, and safe community experience for everyone 
and adhere to Code4Lib’s CodeofConduct4Lib. The full text of the code of 
conduct is available at: http://bit.ly/coc4lib.
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] bring out your spreadsheets or csvs (for testing the archival object importer)

[Christine Di Bella]

Hello ArchivesSpace users,

For some testing we're doing for some new features for the archival objects 
importer (formerly "the Harvard plugin") I'm looking for a variety of 
spreadsheets and CSV files of real (or realish) data. This is only for testing 
this area - not for other kinds of imports in ArchivesSpace that use 
spreadsheets. I'm particularly looking for:


  *   Spreadsheets that use the linked digital objects option
  *   Spreadsheets with many linked records like agents, subjects, and 
containers
  *   Spreadsheets with known, fixable errors that prevent initial import
  *   CSVs of the above structured like the original template i.e. not in 
Microsoft Excel format (see CSV templates attached)
  *   Older spreadsheets created using earlier versions of the template (could 
be ones you imported a few years ago and didn't need anymore)

If you have some spreadsheets you'd be willing to donate to the cause, would 
you please send them my way? They will be used for testing only.

Thanks for your help,
Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905


[ASpaceOrgHomeMedium]



bulk_import_DO_template.csv
Description: bulk_import_DO_template.csv


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

[Archivesspace_Users_Group] bringing the LCNAF plugin back online

[Christine Di Bella]

If you tried to use the LCNAF plugin in any version of ArchivesSpace the last 
few days you may have discovered that it was no longer able to connect to the 
LC service. This is because of a change on their end that needed to be 
reflected in the plugin. To get the plugin back online for any version up to 
and including v2.8.0:


  1.  Download the updated lcnaf plugin from the archivesspace-plugins 
repository: https://github.com/archivesspace-plugins/lcnaf
  2.  Stop your ArchivesSpace.
  3.  Replace the lcnaf plugin folder on your server with this slightly newer 
version of the plugin. (rename the new folder lcnaf if it is named anything 
else)
  4.  Restart ArchivesSpace.

The updated version of the plugin with be included in future releases of 
ArchivesSpace.

Please note, if you have customized this plugin at all, replacing it like this 
will cause you to lose those changes. Email us at 
archivesspaceh...@lyrasis.org<mailto:archivesspaceh...@lyrasis.org> if you need 
help working the changes into a customized version of the plugin.

If you need any assistance, please contact us at 
archivesspaceh...@lyrasis.org<mailto:archivesspaceh...@lyrasis.org> to open up 
a technical support ticket.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905


[ASpaceOrgHomeMedium]

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

[Archivesspace_Users_Group] ArchivesSpace v2.8.0 now available

[Christine Di Bella]

ArchivesSpace is announcing the availability of v2.8.0. You can download it at 
https://github.com/archivesspace/archivesspace/releases/tag/v2.8.0.

This release contains program-led and community pull requests that provide 
feature enhancements, bug fixes, infrastructure improvements, and documentation 
updates. Some items of note include the ability to merge top containers, new 
browse, search, and sort preferences in the staff interface, some improvements 
to search and display in the public interface, additional display and faceting 
options in the background jobs area, bug fixes and accessibility improvements. 
Developers at Harvard University contributed several new features related to 
containers and locations from the specification they circulated in the 
community last year.

Fans of the popular Harvard import plugin will be pleased to see that its 
functionality is now included in ArchivesSpace, courtesy of our work with the 
plugin's original developer, Bobbi Fox. Please note that if you used the plugin 
previously you will need to disable it before starting up ArchivesSpace 
post-upgrade.

Thanks very much to community members Andrew Morrison, Austin Schaffer, Dave 
Mayo, David P. Steelman, Douglas Simon, Katie Amaral, Mark Custer, Mark Triggs, 
Matt Patterson, Michael Vandermillen, and Peter Heiner for their code 
contributions to this release. Program team members Lora Woodford and Mark 
Cooper wrote extensive code and supervised the work of the contractors we 
worked with us on this release: Bobbi Fox, Brian Zelip, Sarah Morrissey, and 
Manny Rodriguez. As always this release would not have been possible without 
the substantial efforts of our Development Prioritization sub-team, Testing 
sub-team, Technical Documentation sub-team, User Documentation sub-team, and 
Core Committers Group.

Information on upgrading to a new version of ArchivesSpace is available at 
https://archivesspace.github.io/tech-docs/administration/upgrading.html. Please 
let us know if you have any questions or need help upgrading. This is the last 
release where our primary technical documentation will live at 
https://archivesspace.github.io/archivesspace/. If you'd like to get a jump on 
things, please change your bookmarks to 
https://archivesspace.github.io/tech-docs/ for all updates going forward.

Lastly, I want to acknowledge that these are incredibly tough times for so many 
of us. Even more than usual, I've really appreciated all our team and community 
members have done to continue making ArchivesSpace better in the face of many 
challenges. Thanks for all your help and for letting us know how important the 
ArchivesSpace application and community have been to you in these times.

Christine

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

[ASpaceOrgHomeMedium]

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

[Archivesspace_Users_Group] release candidate available - ArchivesSpace v2.8.0-rc1

[Christine Di Bella]

Hello ArchivesSpace members,

The ArchivesSpace team is pleased to announce a release candidate, v2.8.0-rc1. 
You can download it at 
https://github.com/archivesspace/archivesspace/releases/tag/v2.8.0-rc1 or test 
it out without downloading at http://test.archivesspace.org/staff  (username 
admin /password admin). We encourage you to download and try it out with your 
own local setup and/or data for the most accurate results.

This release candidate contains program-led and community pull requests that 
provide feature enhancements, bug fixes, infrastructure improvements, and 
documentation updates. Some items of note include the ability to merge top 
containers, new browse, search, and sort preferences in the staff interface, 
some improvements to search and display in the public interface, and additional 
display and faceting options in the background jobs area, as well as bug fixes 
and accessibility improvements. Fans of the popular Harvard import plugin will 
be pleased to see that incorporating its functionality into out-of-the-box 
ArchivesSpace is also part of this release, courtesy of our work with the 
plugin's original developer, Bobbi Fox.

Thanks to the many community members who made contributions to this release, 
including both individual archives staff and developers, as well as our 
Development Prioritization sub-team, Testing sub-team, and Core Committers 
Group.

Please try this release candidate out over the next few days and let us know at 
archivesspaceh...@lyrasis.org<mailto:archivesspaceh...@lyrasis.org> by July 8 
if you notice any problems with the specific areas addressed in this release, 
or if anything that was working before no longer is. The results of testing 
will determine the specific timeframe for the release itself.

Please get in touch if you have any questions. Thanks as always for your 
feedback and support.

Christine

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

[ASpaceOrgHomeMedium]

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

[Archivesspace_Users_Group] FW: Archival Collecting Pandemic Survey Extension

[Christine Di Bella]

>From our colleagues at LYRASIS. Please contact Katy Klettlinger 
>(katy.klettlin...@lyrasis.org) if you 
>have any questions.


From: Katy Klettlinger
Sent: Monday, June 15, 2020 1:27 PM
To: archivp...@lyralists.lyrasis.org
Subject: Archival Collecting Pandemic Survey Extension

Hello everyone,

First, I wanted to say thank you for those that have taken our survey to 
determine archival collecting practices during the COVID-19 Pandemic thus far.  
We have received many responses to better understand and support the needs of 
our community.

Since the input we have received has been valuable we have decided to extend 
our survey deadline to June 26, 2020 at 5:00 Eastern time.

Please discuss any special needs or concerns related to the pandemic with your 
colleagues before completing the survey, as we hope to have one survey 
representing a single institution, and not multiple surveys from a single site. 
The survey is available at https://www.surveymonkey.com/r/3T5V5JN. We estimate 
the survey will take 15 minutes to complete.

Confidentiality: Your responses are being collected and analyzed by LYRASIS, an 
independent, nonprofit, membership organization serving archives, libraries, 
and museums. They will be kept confidential. Only aggregate results will be 
reported. Please answer these questions to help us learn about your current 
practices and needs. To submit your answers, you must click on the "Submit Your 
Responses" button at the end of the survey form.

If you have any questions, please contact me at 
katy.klettlin...@lyrasis.org.

Thank you for your support of this important project; we look forward to 
sharing what we discover with the archival community.

Many thanks,

Katy

Katy L. W. Klettlinger, MLIS
Consultant & Member Outreach Librarian, Mid-Atlantic & Great Lakes
katy.klettlin...@lyrasis.org
Cell phone: 404-576-9099
Skype: Katy Klettlinger
www.lyrasis.org








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

[Archivesspace_Users_Group] ArchivesSpace at this time, some ideas, and upcoming open call

[Christine Di Bella]

Hello ArchivesSpace people,



Like so many in our community we've been wanting to reach out this week and 
struggling to find a way to do so that's meaningful, at a time when violence 
against people of color and many of the structures that perpetuate it have been 
especially laid bare. We've been thinking about the good that archives do, all 
the while mindful that archives and software applications are not neutral, and 
are themselves capable of perpetuating structures that harm or silence. We've 
been thinking about the part that ArchivesSpace can play in making progress in 
these often disheartening times.


We've been specifically thinking of ways ArchivesSpace can support and amplify 
those that document and empower individuals, organizations and communities that 
work to make the world a more inclusive place. We've also been thinking about 
how ArchivesSpace itself can be more inclusive. We've come up with a few ideas 
so far like subsidizing memberships and deployments for some community 
archives, tribal archives, and grassroots organizations; convening a working 
group to examine unconscious bias and barriers to entry in the ArchivesSpace 
application; and working with organizations and groups that help others 
understand ethical collecting and archival description to identify best 
practices for using (or not using) ArchivesSpace. We've started a running list 
for discussion at 
https://docs.google.com/document/d/1b-GlCSObflqZufIiN4dJ__hlppwPloHXzytsUEVlZp4/edit?usp=sharing.


What we want most is to hear your ideas. We're going to devote our next open 
call on June 24 to these issues, and we also want to consider ways we can 
incorporate them more organically into our ongoing programming and our users' 
experience of ArchivesSpace. Please come with your thoughts, questions, and 
suggestions. And please reach out to us at any time. We welcome your 
participation in any form.


We're so proud that the ArchivesSpace community reflects many different kinds 
of archives, serving many different communities. We're so proud that our 
members range from entirely volunteer-run non-profit organizations to some of 
the largest academic archives in the world. We truly appreciate the many 
different viewpoints represented by the collections people manage in 
ArchivesSpace, and the many different viewpoints of the people who manage these 
collections in ArchivesSpace. We believe our community can become even richer 
by drawing in more viewpoints.


We're also mindful that many of us have been pushed to or past our limits 
already, not only by the events of recent months but also by the different 
challenges we each face even in the best of times. We recognize that none of us 
carries the same load, but that some of us go through life with one that is 
heavier than others. While we have no delusions about the role of an archival 
information management system in the grand scheme of things, in the end we hope 
to in some small way contribute to making those loads lighter, not heavier.


Thank you for the part you play in that and for being with us at this 
incredibly challenging time. We wish you health, safety, and solace as, like 
us, you grapple with how best to navigate this world with those you love and 
make it better.


All best,

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905


[ASpaceOrgHomeMedium]


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

Re: [Archivesspace_Users_Group] Best practices for broken date spans and multiple single dates?

[Christine Di Bella]

Hi Joshua,

While you could put all of those into a date expression field, if you're 
wanting to be able to use dates in calculations and such multiple normalized 
dates are definitely the better way to go. Your message is timely because 
there's an issue for this that we're actively working on and hoping to get into 
the next release - https://archivesspace.atlassian.net/browse/ANW-172. It 
should be testable on our regular test server (http://test.archivesspace.org)  
soon.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)



-Original Message-
From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Minor, 
Joshua Alexander
Sent: Thursday, April 23, 2020 9:54 AM
To: archivesspace_users_group@lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Best practices for broken date spans and 
multiple single dates?

Hello all,

I'm hoping this isn't a silly question or that I've just completely missed 
something in the help center/documentation but I'm wondering what's the best 
practice for inputting broken date spans (for example: 1920, 1980-1990) and for 
inputting multiple single dates (for example: 1900, 2010) at the series and/or 
file level in ArchivesSpace. I've checked the ArchivesSpace users group 
archives and this question did come up in 2015 but I didn't see an answer for 
it. It seems that ArchivesSpace doesn't want to string multiple dates together 
(unless you're inputting Bulk Dates) and instead just displays the first date 
entry in both the public interface and staff interface. I'm guessing the 
easiest way to handle this would be to use 1920, 1980-1990 as the Expression, 
use "inclusive" as the type, use 1920 as the Begin date, and use 1990 as the 
End date but this would lead to some inaccurate search results.

Am I missing something? Any advice would be greatly appreciated!

Thanks!

Joshua Minor
​Manager of Archival Processing
College of Charleston
Charleston, South Carolina, 29424
email: mino...@cofc.edu
tel: 843-953-0470

___
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] Request for Assistance with Troubleshooting EAC-CPF Exports for Agent Persons

[Christine Di Bella]

Hi all,

Updating the EAC-CPF exporter very substantially is part of the work that's 
currently happening for the expansion to the agents module. In fact, the test 
branch Mark points to (http://aspace-anw-429.lyrtech.org/) already has some of 
the changes to the import side (not complete yet, however), and the export side 
is next. If anyone's interested in looking or commenting on the map we're 
working off of, it's available at 
https://drive.google.com/file/d/1F0RCwl9ZXRoUnT2C6ICuVW42hogzL7RX/view?usp=sharing.
 All comments and testing for this work in progress very much welcome!

Christine

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

[ASpaceOrgHomeMedium]



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Custer, 
Mark
Sent: Friday, April 24, 2020 9:05 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Request for Assistance with 
Troubleshooting EAC-CPF Exports for Agent Persons

James,

I haven't had a chance to look into this, but my hunch is that the issue would 
reside in ArchivesSpace's EAC exporter, not your database. The EAC importer and 
exporter in ArchivesSpace aren't really finished; you can never (for instance) 
export a valid EAC record, regardless of the data!

I'll try to look into it later today or next week, but I suspect that if you 
want to export any EAC records from ASpace, then you'll need to use a plugin 
for that for now.  I'm not sure if the issue of EAC imports/exports is part of 
the updates to agent records (see http://aspace-anw-429.lyrtech.org/), but I 
quickly tested imports into that test application a while back and I didn't 
note any differences from the original EAC importer, so I suspect not.

Mark



From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of James R Griffin III 
mailto:j...@princeton.edu>>
Sent: Friday, April 24, 2020 8:45 AM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Request for Assistance with 
Troubleshooting EAC-CPF Exports for Agent Persons

Dear Joshua,

Thank you very much for this, but unfortunately, the bioghist note (and its 
single subnote) are both marked as explicitly published, and I am still not 
finding the export in the EAC Document.

I will proceed by seeing if maybe there are duplicate or problematic entries in 
the RDBMS backend.

Best regards,
James

From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of Joshua D. Shaw 
mailto:joshua.d.s...@dartmouth.edu>>
Sent: Thursday, April 23, 2020 12:27 PM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Request for Assistance with 
Troubleshooting EAC-CPF Exports for Agent Persons

Hey James-

Are the bioghist note(s) published - including any subnotes? Only bioghist 
notes and their subnotes will get added to the EAC if published.

Joshua


From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of James R Griffin III 
mailto:j...@princeton.edu>>
Sent: Thursday, April 23, 2020 12:13 PM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] Request for Assistance with 
Troubleshooting EAC-CPF Exports for Agent Persons

Hello Everyone,

Apologies in advance for any trouble, but I am currently experiencing 
difficulty attempting to export an EAC-CPF record. Currently there are "Notes" 
which exist within the database record for the Agent Person (I have verified 
that these exist in the `note` table within the relational database), but these 
are not being exported into a EAC-CPF document.

I believe that the area of the code base where this is found is in: 
https://github.com/archivesspace/archivesspace/blob/master/backend/app/exporters/serializers/eac.rb#L109<https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Farchivesspace%2Farchivesspace%2Fblob%2Fmaster%2Fbackend%2Fapp%2Fexporters%2Fserializers%2Feac.rb%23L109=02%7C01%7Cmark.custer%40yale.edu%7Cd830f81c4cd54b68fa0908d7e84d6499%7Cdd8cbebb21394df8b4114e3e87abeb5c%7C0%7C0%7C637233291416693813=9k%2FnEYzWg1RkO%2Bi33u1vl4XdSeVZQdDw1WutKSZKeYI%3D=0>

Please let me know if I can

Re: [Archivesspace_Users_Group] PUI search default

[Christine Di Bella]

Hi everyone,

The open ticket for this is at 
https://archivesspace.atlassian.net/browse/ANW-806. Search is a particularly 
complex area because of the way the public interface was implemented and that a 
seemingly simple change in one place has a negative impact in another. But we 
know this particular change is widely wanted and has been done in different 
ways in people’s local implementations based on their local preferences. The 
program team was talking just today about some possibilities for how this could 
be implemented in a future release to minimize negative impact.

Christine

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

[ASpaceOrgHomeMedium]



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Tang, 
Lydia
Sent: Thursday, April 9, 2020 1:16 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] PUI search default

I wasn’t able to find it either.  It seems like a widely desired change to have 
the search functionality default changed from “or” to “and.”  Could someone 
create a ticket for it?
https://archivesspace.atlassian.net/secure/Dashboard.jspa
Thanks!
Lydia
Co-leader, Dev. Pri.

From: 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of "Joshua D. Shaw" 
mailto:joshua.d.s...@dartmouth.edu>>
Reply-To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Date: Thursday, April 9, 2020 at 11:57 AM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] PUI search default

The PUI is tricky. I found that I needed to override the search method in the 
PUI SearchController to get an "and" by default. There may be a JIRA ticket in 
for this, but I'm not finding it in a quick search.

Joshua


From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of Jenny Manasco 
mailto:j.mana...@abhsarchives.org>>
Sent: Thursday, April 9, 2020 9:37 AM
To: 
archivesspace_users_group@lyralists.lyrasis.org<mailto:archivesspace_users_group@lyralists.lyrasis.org>
 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] PUI search default


We are trying to change our default search parameter in the PUI. We’ve added



AppConfig[:solr_params] = { "q.op" => "AND" }



to the config file and rebooted but the PUI still gives us “OR” results.



Is there something else we need to change?



v. 2.5.1

VM running under KVM

CentOS Linux 7.0

30 GB Hard Drive (4 GB in use)

4096 MB of RAM

2 CPUs


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

[Archivesspace_Users_Group] seeking nominations for ArchivesSpace Governance groups

[Christine Di Bella]

A reminder that we're seeking nominations for ArchivesSpace's three Governance 
groups: the User Advisory Council, the Technical Advisory Council, and the 
Governance Board. You can learn more about each of these groups at 
https://archivesspace.org/governance-board-and-councils.


Both self-nominations and nominations of others are welcome. To nominate a 
candidate for any of these groups, please submit via the form at 
https://forms.gle/PTvzTXoMCkHQdNga8.

All nominations must be submitted by 9:00 p.m. EDT Friday, April 24. The 
Nominating Committee will review all nominations and recommend appointments to 
the Governance Board for approval.

Please contact me or any member of the Nominating 
Committee<https://archivesspace.atlassian.net/wiki/spaces/ANC/pages/1187414044/2019+Nominating+Committee+Roster>
 with questions. Thanks for considering service to the ArchivesSpace community!

Christine

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

[ASpaceOrgHomeMedium]

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

Re: [Archivesspace_Users_Group] Subject Record Migration from Archon

[Christine Di Bella]

Hi Gwen,

Others may have answers here, but I'm also going to put a support ticket in for 
this. (You'll see another message about that directly to you in a minute.) Our 
tech folks who are familiar with multiple Archon migrations may have some ideas.

Christine

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

[ASpaceOrgHomeMedium]



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Gwenlyn 
Coddington
Sent: Monday, March 23, 2020 2:00 PM
To: Archivesspace Users Group 
Cc: dbren...@mcdaniel.edu
Subject: [Archivesspace_Users_Group] Subject Record Migration from Archon

Hello,

I'm working on reviewing Subject Records from our recent migration from Archon 
and have run across a discrepancy regarding how the faceted Subjects in Archon 
are displaying in ArchivesSpace. It seems that tiered Subject Records in Archon 
are displaying as multiple Subject Records in ArchivesSpace so that a record 
like Academic libraries -- United States -- Maryland now has three Subject 
Records in ArchivesSpace, Academic libraries, Academic libraries -- United 
States, and Academic libraries -- United States -- Maryland.

Where I'm running into trouble is that some of these records say they have 
Resource or Accession tags in the Subject Record but are not tagged in the 
Subject field for the Resource or Accession. Has anyone experienced this issue 
with their migrated data and does deleting or merging the untagged Subject 
Record create any issues with other Subject Records or Resource Records?

Thanks for your time,
Gwen Coddington




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

Re: [Archivesspace_Users_Group] Putting in multiple locations

[Christine Di Bella]

Hi Jill,

This sounds like it's probably specific to your deployment of ArchivesSpace and 
could use some one-on-one help. I'm going to put a tech support ticket in for 
you on this. You'll see another message about that directly to you in a minute.

Christine

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

[ASpaceOrgHomeMedium]



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Jill E. 
Sweetapple
Sent: Tuesday, March 24, 2020 3:53 PM
To: archivesspace_users_group@lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Putting in multiple locations

I'm not sure how many of you are using locations, but I have run into a 
problem. I am trying to put in locations for 877 boxes. I worked most of 
yesterday and put them all in. Late in the day, they disappeared. I put in the 
location profiles (shelf dimensions) and a lot of container profiles as well. 
But once I try to use the bulk operations to input the locations, they won't 
stick! I have put in a lot so far with no problems. But starting yesterday, 
working from HOME incidentally, via VPN, I am hitting a snag. I am tired of 
putting them in, so want to see if anyone has a suggestion.
My instance is hosted, but they are onsite and helping out. I thought more info 
might guide them.

Thank you in advance.
Jill

Jill Sweetapple
Head of Archives and Special Collections
American Baptist Historical Society
3001 Mercer University Dr.
Atlanta, GA  30341-4115

(01) 678/547-6680
www.abhsarchives.org<http://www.abhsarchives.org/>

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

[Archivesspace_Users_Group] ArchivesSpace in this challenging time

[Christine Di Bella]

Dear ArchivesSpace community,


It's an understatement to say that we are living and working through times that 
many of us never expected. We hope that everyone is safe and urge everyone to 
do whatever they need to keep themselves and their loved ones safe and healthy.


That said, we recognize that continuing to help the communities we each serve 
can be a balm when so much around us is different. If you'd like ArchivesSpace 
to factor into your plans in the coming weeks, here are some ideas for how 
ArchivesSpace can help you and you can help ArchivesSpace and each other.


(Please note that we're going to make every attempt to keep things rolling 
along, but keep in mind that the ArchivesSpace team is also adjusting to these 
new realities and changes in our personal and professional circumstances. Your 
patience and understanding with us and with each other is much appreciated.)


Brush up on your ArchivesSpace

  *   Catch up on training videos in the new Help Center 
(https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/917045261/ArchivesSpace+Help+Center)
  *   Work through areas of the User Manual that are less familiar to you
  *   Catch up on webinars you missed 
(https://archivesspace.org/using-archivesspace/webinars)
  *   Catch up on videos in our YouTube channel 
(https://www.youtube.com/channel/UCxR6D-UlSx6N6UWTeqHTjzA)
  *   Work on a data cleanup or data migration project (please reach out to the 
listservs or us at 
archivesspaceh...@lyrasis.org<mailto:archivesspaceh...@lyrasis.org> if you need 
support to get started or get stuck along the way)


Get involved in the ArchivesSpace community

  *   Submit a proposal for the Online Forum 
(https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/966688804/ArchivesSpace+Online+Forum+2020)
  *   Post or respond to questions on the ArchivesSpace Users Group 
(http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group) or 
Small Archives listserv 
(http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_small_archives_users_group)
  *   Write a blog post about how you use ArchivesSpace, past, present or 
future - contact Jessica 
(jessica.cro...@lyrasis.org<mailto:jessica.cro...@lyrasis.org>) if you'd like 
to submit it for the ArchivesSpace blog.
  *   Record a screencast on a range of topics needed by the ArchivesSpace 
community 
(https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/1126465545/Creating+a+User+Tutorial+Screencast)
  *   NEW: Take a Break with ArchivesSpace - beginning this Friday, March 20th, 
we will be hosting casual open calls via zoom at 12pm ET each Friday while many 
of us work from home. Use this as a time to get help or talk about 
ArchivesSpace (or anything else) with colleagues in an informal setting. (more 
details coming soon)


Help improve ArchivesSpace

  *   Test and give us feedback on some new features using our test servers 
(username: admin, password: admin). These are works in progress and we'll send 
more information about each of these features in the coming weeks.
 *   Custom reports: http://reports.lyrtech.org/staff/ - email us or leave 
a comment on https://archivesspace.atlassian.net/browse/ANW-761
 *   Bulk import: http://bulkimport.lyrtech.org/staff/ - email us or leave 
a comment on https://archivesspace.atlassian.net/browse/ANW-386
 *   Expansion of agents module: http://aspace-anw-429.lyrtech.org/staff/ - 
email us or leave a comment on 
https://archivesspace.atlassian.net/browse/ANW-429
  *   Suggest improvements to the User Manual
  *   Suggest improvements to the technical documentation 
(http://archivesspace.github.io/archivesspace/)
  *   Add to the Awesome ArchivesSpace list 
(https://github.com/archivesspace/awesome-archivesspace)
  *   Translate the labels in the ArchivesSpace interfaces into a different 
language (ask us how!)
  *   Assign yourself a Ready for Community Developer JIRA 
(https://archivesspace.atlassian.net/issues/?jql=status%20%3D%20%22Ready%20for%20Community%20Developer%22%20and%20assignee%20is%20EMPTY).
 Learn more about this status from the 2019 Annual Member Forum presentation by 
Lydia Tang and Maggie Hughes at https://youtu.be/qK84vgmS66I
  *   Submit a pull request with completed code. Learn more about the process 
at 
https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/39682053/Submitting+a+Pull+Request.
  *   Turn a plugin you created into core code. Learn more at 
https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/916062227/Making+a+Plug-In+part+of+the+Core+Code.


Please reach out to the ArchivesSpace team at 
archivesspaceh...@lyrasis.org<mailto:archivesspaceh...@lyrasis.org> for any 
help you need to get involved in any of these activities, and let us know if 
you have other ideas. We're here for you and are really thankful for how those 
of us in our community are here for each other.


All best,

The ArchivesSpace Team (Christine, Jessica, Lora, Laurie, Alicia)

Christine Di B

[Archivesspace_Users_Group] ArchivesSpace v2.7.1 now available

[Christine Di Bella]

ArchivesSpace is announcing the availability of v2.7.1. You can download it at 
https://github.com/archivesspace/archivesspace/releases/tag/v2.7.1.

This release contains program-led and community pull requests that provide 
feature enhancements, bug fixes, infrastructure improvements, and documentation 
updates. Items of note include the ability to merge container profiles, a new 
select all capability on browse pages, and accessibility improvements.

Thanks very much to community members Blake Carver, Mark Cooper, Alex Duryee, 
Chris Fitzpatrick, Jeremy Friesen, Brian Harrington, Peter Heiner, Adam 
Jazairi, Steve Majewski, Dave Mayo, Andrew Morrison, Tom Shorock, Douglas 
Simon, and Maura, and program team members Laney McGlohon, Lora Woodford, and 
Sarah Morrissey for their code contributions to this release. Welcome and 
thanks to new contractor Brian Zelip for his contributions. As always this 
release would not have been possible without the efforts of our Development 
Prioritization sub-team, Testing sub-team, Technical Documentation sub-team, 
and Core Committers Group.

I wanted to note that this will be the last release to come out under the 
guiding hand of Tech Lead Laney McGlohon. Thanks to Laney for all she's done 
for the ArchivesSpace application and community over the last three years. We 
will greatly miss you.

Information on upgrading to a new version of ArchivesSpace is available at 
http://archivesspace.github.io/archivesspace/user/upgrading-to-a-new-release-of-archivesspace/.
 Please let us know if you have any questions or need help upgrading. While we 
are in the process of adjusting development plans to reflect staffing changes 
and will be updating the roadmap accordingly, we still expect to have releases 
later in the year that include finished work for a number of the projects 
currently in progress, including merging top containers, functionality for 
importing from spreadsheet files, and the expanded agents module. If your 
resources for upgrading ArchivesSpace to new releases are limited, you may want 
to wait to upgrade until later in the year, when these features are available.

Christine

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

[ASpaceOrgHomeMedium]

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

[Archivesspace_Users_Group] release candidate available - ArchivesSpace v2.7.1-RC1

[Christine Di Bella]

Hello ArchivesSpace members,

The ArchivesSpace team is pleased to announce a release candidate, v2.7.1-RC1. 
You can download it at 
https://github.com/archivesspace/archivesspace/releases/tag/v2.7.1-RC1 or test 
it out without downloading at http://test.archivesspace.org/staff  (username 
admin /password admin). We encourage you to download and try it out with your 
own local setup and/or data for the most accurate results.

This release candidate contains program-led and community pull requests that 
provide feature enhancements, bug fixes, infrastructure improvements, and 
documentation updates. Items of note include the ability to merge container 
profiles, a new select all capability on browse pages, and accessibility 
improvements.

Thanks to the community members who made contributions to this release, 
including both individual archives staff and developers, as well as our 
Development Prioritization sub-team, Testing sub-team, and Core Committers 
Group.

Please try this release candidate out over the next few days and let us know by 
Thursday, February 13, at 
archivesspaceh...@lyrasis.org<mailto:archivesspaceh...@lyrasis.org> if you 
notice any problems with the specific areas addressed in this release, or if 
anything that was working before no longer is. We are providing a very narrow 
window for testing and comments because we expect to put out another release  a 
little later this year with additional features that are nearly ready, 
including merging top containers. As such, while it contains many useful 
improvements that we don't want to delaying putting out any longer, we expect 
the lifespan of v2.7.1 to be more limited than most of our releases.

Please get in touch if you have any questions. Thanks as always for your 
feedback and support.

Christine

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

[ASpaceOrgHomeMedium]

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

Re: [Archivesspace_Users_Group] Need to add new value to Subject Term Type lookup table

[Christine Di Bella]

Hi everyone,

Most controlled value lists in ArchivesSpace are editable. Subject source is an 
editable list, so any of these controlled vocabularies can be added as sources 
locally, even though only a small number are included in ArchivesSpace 
out-of-the-box. Because practices and collection scope/focus vary so much 
across the community there is a lot of latitude for people to configure lists 
locally so that they can see the values most relevant to them.

When controlled value lists in ArchivesSpace are not editable it's either 
because certain values are required to be there to make particular functions 
within the system work or because they're tied into certain external standards 
and at the time that specifications were written and circulated for 
ArchivesSpace (nearly 10 years ago at this point) there was agreement that 
these were the values to limit in the list to closely align with the standard. 
In the case of subject term type, the values closely tie into what's in MARCXML 
and EAD in the 6XX fields and the  area.

Whenever there is interest in revisiting this or any decision regarding the 
ArchivesSpace schema for any type of record or controlled value list, I 
definitely encourage you to get/keep discussion going here and/or by create 
JIRA tickets proposing changes. (As you've been doing with this one - making a 
JIRA ticket might be the next step if people want to raise it to an issue to be 
considered by Development Prioritization.) Like any software application 
ArchivesSpace evolves over time and community guidance and input are what 
determine that evolution.

Christine

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

[ASpaceOrgHomeMedium]



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of 
Majewski, Steven Dennis (sdm7g) 
Sent: Friday, January 17, 2020 8:31:52 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Need to add new value to Subject Term 
Type lookup table


This will make it editable and cause the 'create' button to appear:

MariaDB [archivesspace]> update enumeration set editable = 1 where name = 
"subject_term_type" ;

But I'ld still like to understand the reason it was set as not editable as the 
default.


- Steve M.




On Jan 17, 2020, at 5:02 PM, Bowers, Kate A. 
mailto:kate_bow...@harvard.edu>> wrote:

This needs to either be editable or include all of these controlled 
vocabularies (405 of them) with the ability to suppress display of them by 
repository managers:
https://www.loc.gov/standards/sourcelist/subject.html

Kate

From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 On Behalf Of Majewski, Steven Dennis (sdm7g)
Sent: Friday, January 17, 2020 4:27 PM
To: mcy...@jhu.edu<mailto:mcy...@jhu.edu>; Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Need to add new value to Subject Term 
Type lookup table


subject_term_type enumeration is set as non-editable, which is why no create 
button appears in the view, and also, I believe, prevents changing it via the 
API as well:


./curl_as_osx http://localhost:4567/config/enumerations/names/subject_term_type 
| jq .
{
  "lock_version": 0,
  "name": "subject_term_type",
  "editable": false,
  "create_time": "2015-08-11T21:10:13Z",
  "system_mtime": "2015-08-11T21:10:13Z",
  "user_mtime": "2015-08-11T21:10:13Z",
  "jsonmodel_type": "enumeration",
  "relationships": [
"term_type"
  ],
  "enumeration_values": [
   ...



I don't know where the logic behind what values are editable and what are not 
is documented.
I'm thinking you could change this in MySQL, but it would be wise to know why 
is it set non-editable first.

- Steve M.



On Jan 17, 2020, at 3:19 PM, Mark Cyzyk mailto:mcy...@jhu.edu>> 
wrote:


Dear Aspace List,

I've been asked to add two new terms in the following two lookup tables:

Subject Source:  lcmptm "Library of Congress Medium of Performance Thesaurus 
for Music
Subject Term Type: medium_of_performacne "Medium of performance"

The Subject Source lookup table has a Create button, I click it, add "lcmptm", 
then go into /aspace/locales/enums/en.yml to add the corresponding 
"translation".

However, the Subject Term Type lookup table does NOT have a Create button.  I 
added the new value to the proper place in /aspace/locales/enums/en.yml anyway 
hoping it would show up in the Web GUI.  But no joy.

Question:  How can I add a new value to t

[Archivesspace_Users_Group] Happy holidays from ArchivesSpace

[Christine Di Bella]

[Happy Holidays from ArchivesSpace]

Dear ArchivesSpace community,

Thank you for your continued support! We really appreciate all you do to shape 
ArchivesSpace, both as an application and a community. This has been a 
wonderful year of progress and growth, and we look forward to accomplishing 
even more together in the next.

Our office will be closed from December 24 to January 1. Normal office hours 
will resume on January 2nd. We wish you all warm and happy holidays!

Sincerely,
Your ArchivesSpace Program Team
(Christine Di Bella, Jessica Crouch, Laney McGlohon, Lora Woodford, Alicia 
Johnson, and Laurie Gemmill Arp)

___
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

[Christine Di Bella]

Hi Robin,

Thanks so much to you and your colleagues at Harvard for distributing this 
specification for community comment. We really appreciate your interest in 
making this development work as relevant to the overall community as possible 
and contributing the results for consideration for the core code. To that end, 
I wanted to make a few comments based on past experience or current development 
that you or others may find helpful.

On changing the columns that appear for browses or searches of Location records 
- we often have requests for columnar displays of browse or search results to 
be configurable, including in the Staff Interface Enhancement Working Group's 
recommendations. Our developers are currently working on more configuration 
options for Accession, Resource, and Digital Objects browse displays and the 
search results display in the staff interface, located in the preferences area 
of the application and summarized in this JIRA: 
https://archivesspace.atlassian.net/browse/ANW-929. A test server with this 
work is at http://wiprefds.lyrtech.org/staff/ (standard admin/admin login). We 
expect the final version of this work to be in the next release of 
ArchivesSpace. I'd encourage adding Locations to the type of record that can be 
configured in this area. With the established pattern I think this may be 
fairly easy to do.

I have a similar comment about the proposed changes to the linked records 
displays, though I've heard this mentioned much less frequently. Given that 
different fields may be of interest to different people, I think it's likely to 
be desirable in many situations. I don't think this would fit the other 
pattern, though. It may be one of those things where if it's relatively simple 
to do, it would be worth it in extending the relevance across many different 
users/institutions.

Lastly, you are able to delete barcodes in bulk at this time. When using the 
Rapid Barcode Entry feature in Manage Top Containers, leaving a barcode field 
blank removes the barcode without replacing it with a new barcode. This was 
actually always the case, but we fixed a bug with the indexing in this area 
(https://archivesspace.atlassian.net/browse/ANW-973) recently that didn't make 
it clear this was happening. This will be in the next release of ArchivesSpace.

Those were the things that stood out to me. I look forward to talking more as 
your development work progresses. Thank you for getting the community involved 
proactively!

Christine

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

[ASpaceOrgHomeMedium]



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Wendler, 
Robin King
Sent: Tuesday, December 10, 2019 1:19 PM
To: archivesspace_users_group@lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Revised Proposal for Container Management 
Enhancements - Call for Community Input


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 pr

Re: [Archivesspace_Users_Group] Dual Language Data

[Christine Di Bella]

Hi all,

I'm very interested in discussion of the underlying issues as well as whether 
people have done anything to work around ArchivesSpace's limitations in this 
area. (I'm fact, I recently created a Jira ticket for something in this area 
based on other inquiries: https://archivesspace.atlassian.net/browse/ANW-957.) 
As I mention in that ticket, because of the repeatability of sub-records doing 
description in multiple languages is possible in some areas of ArchivesSpace 
but not all, and there is not way for our current EAD exports (either EAD2002 
or EAD3) or other outputs to distinguish between the different languages. How 
many of you work in contexts where this would be valuable (or even required) 
for individual collections, to work with different service populations or for 
your local or national context?

Christine

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

[ASpaceOrgHomeMedium]




From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Andrew 
Morrison 
Sent: Friday, November 15, 2019 10:24:34 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Dual Language Data

I would imagine it would require a major overhaul or fork of ArchivesSpace to 
make it capable of capturing two or more translations of everything in a single 
record. The data 
model<https://github.com/archivesspace/archivesspace/tree/master/common/schemas>
 is close to the EAD 2002 schema, which isn't multilingual in this sense 
(unlike, say, the manuscript description module of the TEI 
schema<https://www.tei-c.org/release/doc/tei-p5-doc/en/html/MS.html>.)

Andrew.


On Fri, 2019-11-15 at 12:30 +, RENTON Scott wrote:
Hi folks

Wondering if anyone can help with a challenge I've been set. I've got a task to 
investigate how easily we could populate a togglable English-Scottish Gaelic 
front end supplied by Archives Space data (through either the SOLR index or the 
API- we've built a few single-language sites which interrogate ArchivesSpace 
SOLR).

I know that language can be captured when cataloguing, but would I be right in 
saying there is no way of capturing the same data in multiple languages (i.e. 
can I catalogue a title for a resource twice, once in English, and once in 
Gaelic, and would the link, that they are 'the same thing' be preserved?)?

The current website is a bespoke postgres db, which can do this. We want to 
migrate the users over to ArchivesSpace, and I'm pretty sure it can handle 
everything, but this would be a sticking point if it's not possible.

Cheers
Scott




==

Scott Renton

Library Digital Development

Floor F East

Argyle House

515219
The University of Edinburgh is a charitable body, registered in Scotland, with 
registration number SC005336.

___

Archivesspace_Users_Group mailing list

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

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

[Archivesspace_Users_Group] action plan from Toward a National Finding Aid Network (NAFAN) project

[Christine Di Bella]

Hello ArchivesSpace members,

A number of people here may have already seen or be interested in the action 
plan recently released by the Toward a National Finding Aid Network (NAFAN) 
project. Led by the California Digital Library (CDL), this project brought 
together representatives of many regional aggregators of finding aids in the 
U.S. along with funders and expert advisors to discuss ways to build upon the 
individual efforts that have been undertaken over the years and make steps 
toward a national infrastructure for finding aids and other archival 
description.

ArchivesSpace participated in this project as an expert advisor and anticipates 
being involved with follow up projects as well. We see ArchivesSpace as 
important to this project both as the mechanism by which many institutions 
create the archival description that is or could potentially be contributed to 
aggregators and as a community that includes a wide variety of institutions, 
diverse in type, size, geographic area, staffing, collection focus, and many 
other factors important to developing discovery infrastructure that meets an 
array of needs.

The action plan is available at https://bit.ly/action-plan-nafan.

>From the release about the plan:

At the heart of the action plan are recommendations for and principles to guide 
next steps to implement a sustainable national-level finding aid network, based 
on a phased, incremental approach that: moves this effort from a research and 
demonstration project to a program; is informed by a research agenda; and, from 
the outset, includes work to establish business and governance models that fit 
the infrastructure and service model and are grounded in the community's 
organizational and financial capacity.

Over the coming months the CDL will convene follow-up discussions with the 
planning initiative participants to formalize and initiate work identified in 
the action plan.

For more information about the NAFAN planning initiative and outcomes, please 
see the project wiki<https://confluence.ucop.edu/display/NAFAN>.

On the ArchivesSpace side, we welcome any thoughts you have about the value of 
regional and national finding aid/archival description aggregators, and the 
degree to which ArchivesSpace is important for your participation in these 
efforts.

Christine

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

[ASpaceOrgHomeMedium]

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

Re: [Archivesspace_Users_Group] PUI

[Christine Di Bella]

Hi June,

I'm going to put a tech support ticket in for you on this. (You'll see a 
message directly to you about that in a minute.) It sounds like something may 
not be quite right with the way your public interface is set up.

(Even though you'll hopefully get straightened out that way, once that's done I 
encourage you to share the solution back to the list since undoubtedly someone 
else will benefit from it in the future.)

Christine

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

[ASpaceOrgHomeMedium]



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of June L 
Power
Sent: Tuesday, November 5, 2019 3:52 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] PUI

I also get the same error if I click on any of the patron buttons on the top 
right of the PUI:

[cid:image002.png@01D5949F.3A95BBA0]

June

From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 On Behalf Of June L Power
Sent: Tuesday, November 5, 2019 3:30 PM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] PUI

Another noobie question the documentation isn't helping me much with answering.

On the PUI when I click on either collection organization or container 
inventory, I get the following error:

The page you were looking for doesn't exist.
You may have mistyped the address or the page may have moved.

If you are the application owner check the logs for more information.

Where do I fix that on the back end so that information populates?

Also, at the top right, the icons are missing for citation, request, print, 
staff. Where do I fix that?

Thanks in advance.

jlp


June Power, MLIS
Director, Special Collections and Archives
Mary Livermore Library
The University of North Carolina at Pembroke
P.O. Box 1510
Pembroke, NC  28372

910.521.6369
910.521.6547 (fax)
june.po...@uncp.edu<mailto:june.po...@uncp.edu>
  [image001][image002]

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

[Archivesspace_Users_Group] plugins available for bulk data cleanup of language information/RDE template issue

[Christine Di Bella]

As mentioned in the release announcement for ArchivesSpace v2.7.0, the changes 
in the languages area will require data cleanup to existing records for some 
people. Upon upgrade, existing language information is migrated to the new or 
newly structured fields. While some ways of recording information could be 
easily accommodated in this migration, because there are so many different ways 
language information could have been recorded previously, some situations will 
require data cleanup.

We've put together three plugins that you can use, or use as examples, to 
handle some common situations. These only run on resource records. They are:


  *   Batch update language and script of description in resource records to 
one language and/or script of description value: 
https://github.com/archivesspace-plugins/batch_update_lang_and_script - for 
cases where all or most of your description is done in one language and script, 
this will help you do a global or repository-specific update.


  *   Batch update language of materials in resource records currently lacking 
a controlled value language: 
https://github.com/archivesspace-plugins/batch_update_langmaterials - for 
situations where all or most of your materials that do not currently have a 
language value are in one language, this will help you do a global or 
repository-specific update.


  *   Batch update language of materials records for resource records currently 
lacking a controlled value language by matching a text string in a note: 
https://github.com/archivesspace-plugins/batch_update_langmaterials_from_note - 
for situations where specific note text can be easily parsed into a controlled 
value language, this will help you do a targeted update. You will be able to 
choose whether to keep or delete the notes after running this job.

As with any plugins that change information in records, we strongly recommend 
you backup your data before running them and review the results in records 
afterwards before moving on to do more work in your ArchivesSpace. These 
plugins make changes to your records that cannot be undone, though you can edit 
individual records or run the plugins again at any point. Once you've run the 
plugin(s) and are satisfied with the results, you can disable the plugins at 
any time.

Also, we have been alerted to an issue where previously created RDE templates 
do not display correctly in v2.7.0 due to the language changes. This will be 
corrected in the next release, but we are working on a plugin that can provide 
a fix for people who need it quicker than that. In the interim, feel free to 
reach out to us if you need guidance on fixing this locally.

We hope these resources are helpful. Please let us know if you need help with 
them or have other languages-related questions.

Christine

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

[ASpaceOrgHomeMedium]

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

Re: [Archivesspace_Users_Group] Add a static web page to ArchivesSpace PUI?

[Christine Di Bella]

Hi Kara,

Yes, following the process for requesting a new feature in JIRA is described at 
https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/19202060/How+to+Request+a+New+Feature.
 If you need help with that, feel free to reach out to the ArchivesSpace 
Program Team at 
archivesspaceh...@lyrasis.org<mailto:archivesspaceh...@lyrasis.org>.

By the way, if some enterprising person wanted to take James’ very helpful 
plugin and turn it into core code, we’d be very interested. It seems like this 
feature is already most of the way there. We have some suggestions for turning 
plugins into core code at 
https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/349995159/Turning+an+ArchivesSpace+Plugin+into+Core+Code.

Christine

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

[ASpaceOrgHomeMedium]



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of James 
Bullen
Sent: Friday, November 1, 2019 6:47 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Add a static web page to ArchivesSpace 
PUI?


Hi Kara,

Yes, there is no need to initialize this plugin.

And, sorry, I have no idea how you might request this as an enhancement.


Cheers,
James



On Nov 1, 2019, at 3:33 PM, Majewski, Steven Dennis (sdm7g) 
mailto:sd...@virginia.edu>> wrote:




On Nov 1, 2019, at 3:06 PM, Kara Hart 
mailto:kstro...@wellesley.edu>> wrote:

Thank you James!! and Andrew!
I wasn't sure if I needed to run initialize-plugin.sh on this, so I did and got 
this.

Fetching: bundler-1.16.1.gem (100%)
Successfully installed bundler-1.16.1
1 gem installed

[!] There was an error parsing `Gemfile`: No such file or directory - 
/var/local/archivesspace/plugins/static_pages/Gemfile. Bundler cannot continue.

I figure I didn't need to initialize and this error doesn't matter, but just 
checking.



Correct. You only have to run that script if the plugin requires some Gems that 
aren’t already included in that web app core.
That there isn’t a Gemfile in the plugin directory indicates that it doesn’t 
need to bundle any additional Gems.
And when you run the Bundler, it’s telling you that there is no Gemfile.

— Steve.




Also, if I want to put this in as a request for an enhancement for the core 
code, should I put create a new feature request in Jira the project ANW?  Is 
that the proper channel?
Thanks again!
Kara

~~~ Kara S. Hart
Systems Librarian - Library & Technology Services
-
Wellesley College




On Tue, Oct 29, 2019 at 2:19 PM Mike McDermott 
mailto:mmcde...@bowdoin.edu>> wrote:
Nice – looks good. Thanks!

From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 On Behalf Of James Bullen
Sent: Tuesday, October 29, 2019 1:05 PM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Add a static web page to ArchivesSpace 
PUI?


That’s funny - shows how much testing I did.

Should be good now.


On Oct 29, 2019, at 1:00 PM, Mike McDermott 
mailto:mmcde...@bowdoin.edu>> wrote:

This looks really cool.
But – What am I doing wrong.
When I put html in the file to be included, it comes out on the page looking 
like this:

div class=row
h2This is a test/h2
pThis is always a test/p
pTests are what I do./p
h3here is a heading/h3
pThis is always a test/p
pTests are what I do./p
h3here is a heading/h3
pThis is always a test/p
pTests are what I do./p
/div

So it is rendered on the page as looking like html code instead of the page 
elements.

Mike McDermott

From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 On Behalf Of Andrew Morrison
Sent: Tuesday, October 29, 2019 10:55 AM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Add a static web page to ArchivesSpace 
PUI?

Hi James,

Your original version will be useful to us, because we're probably going to 
want to add extra help pages to our staff interface for cataloguers 
transferring over from Archivists' Toolkit. And reading the static HTML from a 
file instead of building from ERB templates means they can be updated without 
restarting the service.

Andrew.


On Tue, 2019-10-29 at 09:35 -0400, James Bullen wrote:

Just a quick follow up on this,

I had misread the spec and only provided the static page facility on the staff 
interface - should have been on the PUI. Andrew Morrison noticed my oops and 
corrected it, so now it should work on both.


Cheers,
James



On Oct 28, 2019, at 6:02 PM, James Bullen 
mailto:

Re: [Archivesspace_Users_Group] Language data in 2.7.0 not exporting to EAD

[Christine Di Bella]

Hi Kevin and Rachel,

Right now the behavior for language of materials is that controlled values are 
exported in EAD2002 when there is not language of materials note. If there is a 
language of materials note, that takes precedence and is all that comes out in 
the EAD. All language-related fields and notes come out in an EAD3 export. This 
was done according to a community specification. If you are seeing behavior 
different than that, it would be great to know if you notice any differences 
depending on what combination or number of language-related values are in the 
record.

We’d like to hear from others (or the Metadata Standards subteam, though, since 
Kevin’s the leader of that group, I guess we are!) to confirm before making 
changes to this for a future release of ArchivesSpace. Feedback during the 
release candidate phase is always especially useful (an unsolicited plug for 
more community testing ), but it’s appreciated at any time.

In the interim, export behavior like this can be changed with a custom export 
plugin. It sounds like NYU already has one for EAD exports, and there are good 
examples to share from around the community (though I’d imagine all predate 
this recent language work). Because the languages area was reworked, some 
language-related fields now have different names or properties, so it would be 
a good time to update those custom export plugins to work with 2.7.0 and future 
versions in any case.

Christine

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

[ASpaceOrgHomeMedium]


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Rachel 
Aileen Searcy
Sent: Thursday, October 31, 2019 8:57 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Language data in 2.7.0 not exporting 
to EAD

Hi Kevin,

We are also currently testing 2.7.0 on a local dev instance and I can confirm 
that we are also experiencing an issue with the Language of Materials Note not 
exporting. I did test this on the 2.7.0 community sandbox and the records I 
exported there did show that note in the EAD. We also have a plugin that 
modifies our EAD export to work nicely with our finding aid publication and 
display mechanisms, which might explain our issues and I'm still 
investigating...

Thanks for bringing this to attention!
Rachel

On Wed, Oct 30, 2019 at 1:44 PM Kevin W. Schlottmann 
mailto:kws2...@columbia.edu>> wrote:
Hi all,

We're testing 2.7.0 on our hosted dev instance, and we noticed that in the EAD 
export, the language of materials information (neither the encoded data nor the 
language note) is coming through in the EAD export. Is anyone else experiencing 
this?

The MARC export appears to be work fine (008, 040$b, 041, 546 all seem to be 
exporting correctly).

Best,

Kevin
--
Kevin Schlottmann
Head of Archives Processing
Rare Book & Manuscript Library
Butler Library, Room 801
Columbia University
535 W. 114th St., New York, NY  10027
(212) 854-8483


___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org<mailto:Archivesspace_Users_Group@lyralists.lyrasis.org>
https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup=DwICAg=slrrB7dE8n7gBJbeO0g-IQ=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk=CUGD7S_0q8aCI95jC3EIOf4MHnhcmU3IfPexJGvSD3Y=WRGz2lv2MQg_qKhRZvKDeTtdI2QtNlezr4j9GpFFQPE=


--
Rachel Searcy
Accessioning Archivist, Archival Collections Management
New York University Libraries
212.998.2539 | rachel.sea...@nyu.edu<mailto:rachel.sea...@nyu.edu>
My pronouns are she/her
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] ArchivesSpace v2.7.0 now available

[Christine Di Bella]

ArchivesSpace is announcing the availability of v2.7.0. You can download it at 
https://github.com/archivesspace/archivesspace/releases/tag/v2.7.0.

This release contains program-led and community pull requests that provide 
feature enhancements, bug and security fixes, and documentation updates, as 
well as infrastructure improvements, which were a significant focus of this 
release. A full list of the changes and improvements is provided on the release 
page.

In addition to small interface and functionality changes, this release contains 
two larger areas of feature enhancement. One relates to recording information 
about language of description and materials. These changes were made to 
facilitate better standards compliance in these areas. For language of 
description language and script can now be recorded using controlled values as 
well as notes. For language of materials multiple languages and scripts can now 
be recorded using controlled values and notes. Existing language information in 
records has been migrated to the new or newly structured fields. While some 
ways of recording information could be easily accommodated in this migration, 
because there are so many different ways language information could have been 
recorded previously, some situations will require data cleanup. As you look at 
language information in your records, if you see patterns in your data, please 
let us know. We are creating a few plugins that could be helpful with bulk 
cleanup work in this area.

The second major feature enhancement, made to accommodate requests to use 
persistent identifiers in OAI-PMH harvests and exports, is that resources and 
archival objects can now be represented by Archival Resource Keys (ARKs). ARKs 
can either be generated by ArchivesSpace or created outside the application. By 
the way, we're looking to host a webinar on ARKs in 2020; if you're using ARKs 
already or planning to use them now that ArchivesSpace can generate them, 
please get in touch about this possibility for sharing your knowledge with the 
community.

Thanks very much to community members Mark Cooper, Mark Custer, Alex Duryee, 
Dave Mayo, Austin Schaffer, and Greg Wiedeman, and program team members Laney 
McGlohon, Lora Woodford, and Sarah Morrissey for their code contributions to 
this release. Thanks also to the contract developer we have been able to engage 
through member funds, Manny Rodriguez (via LibraryHost), for his efforts on the 
ARKs feature. Thanks to LYRASIS Digital Technology Services for their technical 
support with our testing servers and running trial migrations. Last, but by no 
means least, as always this release would not have been possible without the 
efforts of our Development Prioritization sub-team, Testing sub-team, Technical 
Documentation sub-team, and Core Committers Group.

Information on upgrading to a new version of ArchivesSpace is available at 
http://archivesspace.github.io/archivesspace/user/upgrading-to-a-new-release-of-archivesspace/.
 If you have not yet upgraded to a recent version, we recommend going directly 
to 2.7.0. Please let us know if you have any questions or need help upgrading.

Christine

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

[ASpaceOrgHomeMedium]


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

[Archivesspace_Users_Group] ignore LIB IT messages to the Users Group this morning

[Christine Di Bella]

Hello everyone,

Just wanted to note that the two messages from LIB IT earlier today can be 
ignored. The links in them are not harmful, but they’re also not related to 
ArchivesSpace. One of our member institutions inadvertently subscribed an 
address that sends auto-replies. That address has now been unsubscribed.

And a friendly reminder to turn off auto-replies for listservs and other 
messages that don’t go to a single user’s email address. 

Christine

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

[ASpaceOrgHomeMedium]

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

[Archivesspace_Users_Group] release candidate available - ArchivesSpace v2.7.0-RC1

[Christine Di Bella]

Hello ArchivesSpace members,

The ArchivesSpace team is pleased to announce a release candidate, v2.7.0-RC1. 
You can download it at 
https://github.com/archivesspace/archivesspace/releases/tag/v2.7.0-RC1 or test 
it out without downloading at http://test.archivesspace.org/staff (username 
admin /password admin). We encourage you to download and try it out with your 
own local setup and/or data if you can for the most accurate results.

This release candidate contains program-led and community pull requests that 
provide feature enhancements, bug fixes, and documentation updates, as well as 
a number of infrastructure improvements, which were a significant focus of this 
release. When testing, we highly encourage you to not only check out the new 
changes, but also to make sure that features you already use are working as 
intended.

In addition to small interface and functionality changes, this release 
candidate contains two larger areas of feature enhancement. One relates to 
recording information about language of description and materials. These 
changes were made to facilitate better standards compliance in these areas. For 
language of description language and script can now be recorded using 
controlled values as well as notes. For language of materials multiple 
languages and scripts can now be recorded using controlled values and notes. 
Some information about the new languages functionality is available at 
https://docs.google.com/document/d/14UlJseFzGhsoEkiSVTidJMQXizFLPjXr2fuf2Pa5iGQ/edit?usp=sharing.
 We encourage you to read through the documentation and make comments. This 
information will be incorporated into the user manual once the production 
release of 2.7.0 is available.

Existing language information in records has been migrated to the new or newly 
structured fields. While some ways of recording information could be easily 
accommodated in this migration, because there are so many different ways 
language information could have been recorded previously some situations will 
require data cleanup. As you look at language information in your records, if 
you see patterns in your data, please let us know. (An example might be that 
all of your description is in one language, but you never or only rarely 
recorded that language in the Language of Description field in Finding Aid 
Data.) We would like to help by creating some plugins that could be run to do 
bulk cleanup work in this area.

The second major feature enhancement, made to accommodate requests to use 
persistent identifiers in OAI-PMH harvests and exports, is that resources and 
archival objects can now be represented by Archival Resource Keys (ARKs). ARKs 
can either be generated by ArchivesSpace or created outside the application. 
Some information on the new ARKs functionality is available at 
https://docs.google.com/document/d/1e0K2ZsSqWPxtKifCa_-ZyhAdyDJcJR0tA3S-N3X3FGU/edit?usp=sharing.
 This information will also be incorporated into the user manual.

Thanks to the many community members who made contributions to the work 
reflected in this release candidate, including individual archives staff and 
developers, our Development Prioritization sub-team, Testing sub-team, and the 
Core Committers Group.

We'll be collecting feedback through Monday, October 7. Please let us know at 
archivesspaceh...@lyrasis.org<mailto:archivesspaceh...@lyrasis.org> if you 
notice any problems with the specific areas addressed in this release, or if 
anything that was working before no longer is. Barring major issues, we expect 
to release v2.7.0 by mid-October.

Christine

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

[ASpaceOrgHomeMedium]

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

[Archivesspace_Users_Group] informal registry of independent ArchivesSpace consultants

[Christine Di Bella]

Hi everyone,

As the ArchivesSpace user community continues to grow, we occasionally hear 
from people wanting individualized help beyond what membership or volunteer 
peer-to-peer guidance can provide. Typical needs include migrating data from a 
legacy database, custom interface work, one-on-one user training, or deploying 
an ArchivesSpace server. Often these requests come from people who aren't 
interested in hosting options, or can't pursue bringing a full workshop to 
their regional area.

To help in these kinds of situations, the ArchivesSpace program maintains an 
informal registry of individuals interested in providing independent consulting 
services related to ArchivesSpace. Please note that our involvement is for 
informational purposes only. Consultants and potential clients work out any 
details of projects and costs amongst themselves.

Interested in being a consultant?
If you know of someone who would like to be listed, or would like to be listed 
yourself, please email Jessica at 
jessica.cro...@lyrasis.org<mailto:jessica.cro...@lyrasis.org> with the 
following information.

  *   Location
  *   Services
  *   Experience with ArchivesSpace
  *   Best way for prospective clients to get in touch with you and/or see 
examples of your work

Affiliation with an ArchivesSpace member institution is not required for an 
individual to be listed in the registry.

For companies and other larger efforts, we have a Registered Service Provider 
(RSP) program 
(http://archivesspace.org/registered-service-providers/why-and-how-to-become-an-rsp/)
 that provides additional benefits. Feel free to get in touch with me 
(christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>) for more 
information on the RSP program.

Interested in finding a consultant?
If you are interested in working with a consultant, please email us at 
archivesspaceh...@lyrasis.org<mailto:archivesspaceh...@lyrasis.org>. We'll be 
glad to send you the current registry.

Please feel free to forward this message to anyone you think may be interested, 
either in being or retaining a consultant.

Christine

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

[ASpaceOrgHomeMedium]

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

Re: [Archivesspace_Users_Group] testing for ArchivesSpace Windows installer/upgrade tool

[Christine Di Bella]

Hi Eric,

We created a Windows installer in response to feedback and our own observations 
that a number of Windows folks often struggle with installing and upgrading 
ArchivesSpace. As many smaller institutions, in particular, are locked into 
using Windows, we’re hoping that a tool like this can help them get up and 
running more easily.

Once we’ve gotten this one tested and hopefully determined that it meets this 
need for the people we’re trying to help in this round, we’d be happy to 
consider expanding the scope of this project. It may very well be be possible 
to create other installers down the line, though we’d love to hear more about 
specific needs and why an installer could be useful to meet them. Like this 
one, any installers we create would have to be pretty basic and won’t be able 
to suit all needs.

Christine

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Gadsby, 
Eric T.
Sent: Monday, August 12, 2019 2:14 PM
To: Archivesspace Users Group 
; 'Archivesspace Member Reps' 
; 
archivesspace_...@lyralists.lyrasis.org; archivesspace_...@lyralists.lyrasis.org
Subject: Re: [Archivesspace_Users_Group] testing for ArchivesSpace Windows 
installer/upgrade tool

Christine et all,

Congratulations, this looks like an awesome project. Is there a similar project 
in the works for Linux that I have simply missed if not I may a suggest one? 
Thanks!




[Towson University logo]<http://www.towson.edu/>
Eric T. Gadsby
IT Operations Specialist | Albert S. Cook Library
—
P: 410-704-3340
egad...@towson.edu<mailto:egad...@towson.edu>  |  
libraries.towson.edu<http://www.towson.edu/https:/libraries.towson.edu>
—
Pronouns: he/him/his
Confidentiality Notice: This message may contain information that is 
confidential, privileged, proprietary, or otherwise legally exempt from 
disclosure. If you are not the intended recipient, you are notified that you 
are not authorized to read, print, copy or disseminate this message, any part 
of it, or any attachments. If this message has been sent to you in error, 
please notify the sender by replying to this transmission, or by calling Albert 
S. Cook Library at 410-704-3340.




From: 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of Christine Di Bella 
mailto:christine.dibe...@lyrasis.org>>
Reply-To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Date: Monday, August 12, 2019 at 1:37 PM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>,
 'Archivesspace Member Reps' 
mailto:archivesspace_member_r...@lyralists.lyrasis.org>>,
 
"archivesspace_...@lyralists.lyrasis.org<mailto:archivesspace_...@lyralists.lyrasis.org>"
 
mailto:archivesspace_...@lyralists.lyrasis.org>>,
 
"archivesspace_...@lyralists.lyrasis.org<mailto:archivesspace_...@lyralists.lyrasis.org>"
 
mailto:archivesspace_...@lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] testing for ArchivesSpace Windows 
installer/upgrade tool

[EXTERNAL EMAIL - USE CAUTION]
Hello ArchivesSpace users,

Do you use Windows, either on your personal computer or for your institution’s 
ArchivesSpace server? We are looking for people to test a new tool aimed at 
making installing or upgrading ArchivesSpace on Windows easier. The tool is 
available at 
https://github.com/archivesspace/archivesspace-installer/releases/tag/v1.0.0-beta<https://secure-web.cisco.com/1n6fEv20FPjSwKh9CeVzWZGoe871W9GgDuGdn2dvYmHDz3yhPDJxx_bLafNvzpTbCBXu_5e6Qu5aS5_UslogFWAVpAJnQp9NkK6T-Pswqqemfv1UPDezlfwL6VNG452wWCfHXDQsx8adoN_4pyMB2To2rkpfgpwlECxhWdE6ljrLf086drsFjhtqPPhSTUoRNaO9ZAq2NDaou1rfLmq0pFlZbgHv1hKEW7YzZpmHfZEmG4etYIC6RU4U1RNWTs0As9yirUv4jsWGMrkZOovicZFZG6L4xpkk140q7_MUsZFDkEyVXwpk9KoeQNN1s7Tt-NfUohVKyes2weNPoRsZWmVkIUNL31H-xnTFNn8ILInw4AHdIaXt800IfB4uX_e1o4WRprVWPuquo7KcXlQBrJJUTQfta93wY3fggE7bK1GzOte_9RmwmDemg_NS6dTW8/https%3A%2F%2Fgithub.com%2Farchivesspace%2Farchivesspace-installer%2Freleases%2Ftag%2Fv1.0.0-beta>.
The instructions are linked from within the installer and also at 
https://github.com/archivesspace/archivesspace-installer/blob/master/README.md<https://secure-web.cisco.com/1w-pf1uBaBEVldhLy3ht1WRyOexptfxbn7tRajCFi7EF8Tbowkjt3qy_VCn4nyGIFTsrFQCKTuIw4m5YcSudwZ11eaA4ooNasm9AZDBtNziAdcWxTQMbn72f9kl1n74yXxdcOWNFBr143_aYStduEv_Z-jJ8oDNmXjL48KuJKGgIvFZy19HMoMrpM_X6RKqUD7thK11IyMFrgTXtIMdNm8szDjNfynJNJWy5zM_4mBo_eCOlwxXd8zCRRWZmK5V1F8QqOoAitMdXpFJmAD4pc_v8f6osDfhVvOcE2UEbFOiONQY0oDAXNxwFqfT90BJand4ULbZzyPivxsFNhl7cl_L7GXL_6qCMiWjc_97dVZIJleQ-fX7QWmIrjhqgV12o66RpozIyvbSkF--Gj9rMoLMumq7jFdFCVsKzu4u5zeaB9s-lNJ3crxMmx1MbzJ8m4/https%3A%2F%2Fgithub.com%2Farchivesspace%2Farchivesspace-installer%2Fblob%2Fmaster%2FREADME.md>.
 This tool is in beta and should only be used for a new installation or a 
backup of your existing installation.

(Note that installing ArchivesSpace is not necessary for people just

Re: [Archivesspace_Users_Group] Adding identifiers to resource trees and record entries in assessments

[Christine Di Bella]

Hi Nick,

Identifiers were added to the assessment record display in version 2.6.0 (see 
https://archivesspace.atlassian.net/browse/ANW-274 for the issue). The CUID is 
not part of that, though a plug-in should similarly be able to change that 
behavior for you locally if you wish.

I’ll also just mention that if anyone develops plug-ins for these or other 
functions that they think might have relevance outside their own institution, 
please consider adding them as links on the Awesome ArchivesSpace list 
(https://github.com/archivesspace/awesome-archivesspace). This is a wonderful 
community-maintained web guide that points to a variety of resources developed 
across the community. It includes links to documentation, plug-ins, scripts, 
integration possibilities and more.

Christine

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

[ASpaceOrgHomeMedium]



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Nick 
Butler
Sent: Friday, June 28, 2019 5:35 AM
To: archivesspace_users_group@lyralists.lyrasis.org
Subject: Re: [Archivesspace_Users_Group] Adding identifiers to resource trees 
and record entries in assessments

Hi Cory,

Thank you very much for the link - the tree_component_id plugin looks like it 
should do exactly what we need for the resource trees.

Best wishes,
Nick

-Original Message-
From: Cory Nimer 
mailto:cory%20nimer%20%3ccory_ni...@byu.edu%3e>>
Reply-To: Archivesspace Users Group 
mailto:archivesspace%20users%20group%20%3carchivesspace_users_gr...@lyralists.lyrasis.org%3e>>
To: Archivesspace Users Group 
mailto:archivesspace%20users%20group%20%3carchivesspace_users_gr...@lyralists.lyrasis.org%3e>>
Subject: Re: [Archivesspace_Users_Group] Adding identifiers to resource trees 
and record entries in assessments
Date: Thu, 27 Jun 2019 16:17:52 +

Nick,

It appears that the second of your requests below was previously proposed as 
part of ANW-780 (https://archivesspace.atlassian.net/browse/ANW-780). The 
comments there suggest that there is some interest in replacing the Instance 
Type in the resource tree with the component unique identifier (CUI), but the 
Development Prioritization Team felt the data being recorded in the CUI field 
was not consistent enough yet to merit a change in the base code. However, the 
ticket does include a link to a plug-in from the University of Denver that 
appears to replace the instance number column in the resource tree with the 
CUI--if that would meet your need.

Best,

Cory Nimer
University Archivist
Brigham Young University
801-422-6091

From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 On Behalf Of Nick Butler
Sent: Thursday, June 27, 2019 9:21 AM
To: 
archivesspace_users_group@lyralists.lyrasis.org<mailto:archivesspace_users_group@lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Adding identifiers to resource trees and 
record entries in assessments

Good afternoon,

Our archivists are wondering if it's possible to add record identifiers to the 
following areas:

* The record(s) in Assessments (i.e. each entry in div class="input-group 
linker-wrapper multiplicity-many sortable" in the edit or new Assessments 
screen). Currently it just has the object title, we'd like it to have the 
identifier concatenated too.
* The entries in resource trees (i.e. each entry in div 
class="largetree-container ui-resizable" in the edit Resources screen). Again 
it currently only has the object title (or display_string, for archival 
objects).

Might anyone know if there's any way to achieve this with a plugin? Has anyone 
done something like this before?

Many thanks for any suggestions!

Best wishes,
Nick

--
Nick Butler
Software Developer
Digital Services
Cambridge University Library
West Road
Cambridge CB3 9DR, UK

np...@cam.ac.uk<mailto:np...@cam.ac.uk>

Internal tel: 33067

___

Archivesspace_Users_Group mailing list

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

http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group



--
Nick Butler
Software Developer
Digital Services
Cambridge University Library
West Road
Cambridge CB3 9DR, UK

np...@cam.ac.uk<mailto:np...@cam.ac.uk>

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

Re: [Archivesspace_Users_Group] Users with basic data entry credentials and access to agent contact details

[Christine Di Bella]

Dear Natalie,

First off, welcome!

Your mention of our training materials and the implications of this particular 
permission for the UK Data Protection Act and GDPR made us look to see what was 
happening in the application. As far as we can tell, all permission levels with 
access to view agent records have been able to view the contact details part of 
the record. This is clearly not what was intended, given how this was written 
up for the purposes of training and the user manual. And we know it's an even 
more important feature now given international laws around securing personal 
information.

I'm pleased to say that one of our developers was able to determine what was 
wrong and to add a specific permission for viewing the contact details part of 
an agent record. This permission will be automatically included for the 
out-of-the-box permission levels above Advanced Data Entry users and also 
selectable if high level users want to include it for other permission groups 
(and de-selectable if people don't want it included for the permission groups 
for which it comes automatically). This feature will need additional testing, 
but assuming it passes muster, we anticipate including it in our next release, 
which will come out later in the summer. We've added a JIRA issue 
(https://archivesspace.atlassian.net/browse/ANW-910) and work can be tracked 
there.

Thanks for bringing this oversight to our attention. We typically can't make 
changes to the application as quickly as this, but I'm glad it was possible in 
this case.

Christine

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

[ASpaceOrgHomeMedium]



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of na207
Sent: Tuesday, June 18, 2019 10:11 AM
To: archivesspace_users_group@lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Users with basic data entry credentials 
and access to agent contact details

Dear all,

This is my first message to the user group- I've been making great use of the 
list's archives and am hoping someone may be able to help with my question.

I'm working through issues concerning sharing personal data about living 
individuals in ArchivesSpace- seeking to ensure that personal data is only 
accessible and shared if necessary and appropriate to comply with the UK Data 
Protection Act and GDPR.

We were lucky enough to receive 2 days training on ArchivesSpace last summer 
and our training notes about the types of user record set out the following :



Basic Data Entry Staff: Has no application customization permissions; is unable 
to read or write name contact information; has read-only access to Accession, 
Digital Object, Agent, and Subject records, has read/write permissions on 
Resource records.

I have just set up a test user account and given it basic data entry 
privileges. When I log in as that user I can view (but not edit) agent records 
including contact information. The agent records have been created by the 
repository to which the test user belongs but the test user can also see 
contact details of agents created by another repository.

I have looked at the 'manage groups' menu to check what basic data entry users 
can do, and found that the following boxes only are checked:- create/update 
resources in this repository; create/update digital objects in this repository; 
view the records in this repository; create and run a background job. It 
doesn't look as though there is another box I could tick to limit access to 
contact information.

I may be missing something obvious but is there a way to limit access to 
contact information in ArchivesSpace? I would be very grateful for any 
assistance,

Best wishes,

Natalie


Natalie Adams
Systems Archivist
Cambridge University Library
West Road
Cambridge
Cambridge, CB3 9DR
Tel 01223 766377
www.lib.cam.ac.uk/<http://www.lib.cam.ac.uk/>
Normal working days are Monday-Wednesday

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

Re: [Archivesspace_Users_Group] Startup error - can't find childprocess-1.0.1

[Christine Di Bella]

Dear Christopher,

We're still researching this, but some other users with Java 1.7 have reported 
this problem when trying to run 2.6.0. There was a Rails and other 
infrastructure updates in 2.6.0 and retaining support for this significantly 
older version of Java may not be possible with these necessary updates.

Are you able to update to Java 1.8? That seems to have resolved the issue for 
others.

Christine

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

[ASpaceOrgHomeMedium]



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of 
CHRISTOPHER LOVELL
Sent: Wednesday, June 12, 2019 10:35 AM
To: archivesspace_users_group@lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Startup error - can't find 
childprocess-1.0.1

Hello all,

I just performed a fresh install of the latest release of ArchivesSpace on a 
Windows 2008 R2 server with Java 1.7.0_55 and am seeing the error "Could not 
find childprocess-1.0.1 in any of the sources" in the log.  I am unable to 
determine the cause.  Can anyone offer suggestions?  Here's a snip from the 
beginning of the log file.  Thanks in advance for any assistance you can 
provide.

[snip]
Loading ArchivesSpace configuration file from path: 
C:\archivesspace\config/config.rb
Jun 12, 2019 10:12:31 AM 
org.eclipse.jetty.server.handler.ContextHandler$Context log
INFO: An exception happened during JRuby-Rack startup
Could not find childprocess-1.0.1 in any of the sources
--- System
jruby 9.1.17.0 (2.3.3) 2018-04-20 d8b1ff9 Java HotSpot(TM) 64-Bit Server VM 
24.55-b03 on 1.7.0_55-b13 +jit [mswin32-x86_64]
Time: 2019-06-12 10:12:31 -0400
Server: jetty/8.1.5.v20120716
jruby.home: uri:classloader://META-INF/jruby.home

--- Context Init Parameters:
jruby.compat.version = 1.9
jruby.max.runtimes = 1
jruby.min.runtimes = 1
public.root = /
rack.env = production

--- Backtrace
Bundler::GemNotFound: Could not find childprocess-1.0.1 in any of the sources
  block in materialize at 
C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/spec_set.rb:88
  map! at org/jruby/RubyArray.java:2519
   materialize at 
C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/spec_set.rb:82
 specs at 
C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:170
 specs_for at 
C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:237
   requested_specs at 
C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/definition.rb:226
  block in requested_specs at 
C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:108
 setup at 
C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/runtime.rb:20
 setup at 
C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler.rb:107
 at 
C:/archivesspace/gems/gems/bundler-1.16.1/lib/bundler/setup.rb:20
   require at org/jruby/RubyKernel.java:956
(root) at 
uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1
 at 
uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:133
   require at org/jruby/RubyKernel.java:956
(root) at 
C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:1
   block in (root) at 
uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1
 instance_eval at org/jruby/RubyBasicObject.java:1691
   require at 
uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55
 at 
C:\archivesspace\data\tmp\jetty-0.0.0.0-8089-backend.war-_-any-\webapp\WEB-INF\config.ru:4
  start_server at launcher/launcher.rb:92
  main at launcher/launcher.rb:157
 at launcher/launcher.rb:261

--- RubyGems
Gem.dir: C:/archivesspace/gems
Gem.path:
C:/Users/lovellc/.gem/jruby/2.3.0
uri:classloader:/META-INF/jruby.home/lib/ruby/gems/shared
C:/archivesspace/gems
Activated gems:
  did_you_mean-1.0.1
  bundler-1.16.1

--- Bundler
Bundler.bundle_path: C:/archivesspace/gems
Bundler.root: 
C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF
Gemfile: 
C:/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/Gemfile
Settings:
  without = [:test, :development, :doc]

--- JRuby-Rack Config
compat_version = RUBY1_9
default_logger = 
org.jruby.rack.logging.StandardOutLogger@30f74da2<mailto:org.jruby.rack.logging.StandardOutLogger@30f74da2>
equals = 
err = java.io.PrintStream@d97643c<mailto:java.io.PrintStream@d97643c>
filter_adds_html = true
filter_verifies_resource = false
ignore_environment = false
initial_memory_buffer

Re: [Archivesspace_Users_Group] merge Top Container functionality

[Christine Di Bella]

For container management improvements, merging top containers has been the 
priority for awhile based on the Staff Interface Enhancement Working Group 
recommendations and what we've heard from the community -- that's definitely 
what we're aiming for first. But, as you note, there's a JIRA for merging 
container profiles as well. We'll need to revisit this when we get there, but 
I'd think that once we get top containers worked out, adding the ability to 
merge container profiles would be a comparatively short step from there.

(Of course, if a community developer is able to tackle merging container 
profiles before we get there, we 'd love to hear from them. The program team or 
community members could likely create a more detailed specification for how it 
should look/behave based on what's in the JIRA.)

Christine

-Original Message-
From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Kevin 
Clair
Sent: Tuesday, June 4, 2019 7:48 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] merge Top Container functionality

Thanks, Christine! Will there be similar functionality for Container Profiles? 
Someone at our shop asked me about that the other day and I saw there's a 
ticket for it at https://archivesspace.atlassian.net/browse/ANW-550, but it 
looks like it hasn't been updated since last summer.  -k

On 6/4/19, 2:50 PM, "archivesspace_users_group-boun...@lyralists.lyrasis.org 
on behalf of Christine Di Bella" 
 wrote:

Hi Benn,

Merging Top Containers has been on our development roadmap, and we know it 
is of great interest to a number of people in the community, but until recently 
we had not been able to identify a developer to take this on. We've now 
determined that we will be able to work on this after some of the large 
projects related to agents and infrastructure that are currently in progress 
have been completed. We're aiming for this functionality to be available in the 
application later this year.

Christine

    Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)



-Original Message-
From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Benn 
Joseph
Sent: Tuesday, May 21, 2019 5:22 PM
To: Archivesspace Users Group 

Subject: [Archivesspace_Users_Group] merge Top Container functionality

Hi all,
I'm curious whether there are any updates re: the ability to merge Top 
Containers. It looks like ANW-462 deals specifically with this but I can't tell 
if there has been much activity on it lately:


https://archivesspace.atlassian.net/browse/ANW-462?atlOrigin=eyJpIjoiZTc0MWQ4MDdlMjhjNGFlZmE4YTEwYzg3YTQ0ZmQzZTkiLCJwIjoiaiJ9

Thanks!
--Benn

Benn Joseph
Head of Archival Processing
Northwestern University Libraries
Northwestern University
www.library.northwestern.edu
benn.jos...@northwestern.edu
847.467.6581



-Original Message-
From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Tang, 
Lydia
Sent: Wednesday, January 16, 2019 12:18 PM
To: Archivesspace Users Group 

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

I second the ability to merge containers!  
Lydia

From:  on behalf 
of Valerie Addonizio 
Reply-To: Archivesspace Users Group 

Date: Wednesday, January 16, 2019 at 1:17 PM
To: Archivesspace Users Group 

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

I know that the comment period is closed, but this seemed like a logical 
place to ask whether the idea of container merging functionality was considered 
as part of this effort (I know it is not in the scope of work, but was it 
considered and not selected?) and whether other institutions are in need of 
such functionality?

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Bowers, Kate A.
Sent: Thursday, December 20, 2018 4:16 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] REMINDER: Proposal for Container 
Management Enhancements - Call for Community Input

Dear ArchivesSpace community:

Apologies for the length of this. I’ll try to address a lot of comments, 
but not all!  Please let me know if (as they may well do) my elaborations only 
elicit more questions!

In general, most of these proposals are derived from facing problems of 
scale. Harvard has 30 repositories and over 200 users of ArchivesSpace. Others 
have to do with managing “medium rare” materials’ locations and containers in 
ArchivesSpace

Re: [Archivesspace_Users_Group] merge Top Container functionality

[Christine Di Bella]

Hi Benn,

Merging Top Containers has been on our development roadmap, and we know it is 
of great interest to a number of people in the community, but until recently we 
had not been able to identify a developer to take this on. We've now determined 
that we will be able to work on this after some of the large projects related 
to agents and infrastructure that are currently in progress have been 
completed. We're aiming for this functionality to be available in the 
application later this year.

Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org
800.999.8558 x2905
678-235-2905
cdibella13 (Skype)



-Original Message-
From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Benn 
Joseph
Sent: Tuesday, May 21, 2019 5:22 PM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] merge Top Container functionality

Hi all,
I'm curious whether there are any updates re: the ability to merge Top 
Containers. It looks like ANW-462 deals specifically with this but I can't tell 
if there has been much activity on it lately:

https://archivesspace.atlassian.net/browse/ANW-462?atlOrigin=eyJpIjoiZTc0MWQ4MDdlMjhjNGFlZmE4YTEwYzg3YTQ0ZmQzZTkiLCJwIjoiaiJ9

Thanks!
--Benn

Benn Joseph
Head of Archival Processing
Northwestern University Libraries
Northwestern University
www.library.northwestern.edu
benn.jos...@northwestern.edu
847.467.6581



-Original Message-
From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Tang, 
Lydia
Sent: Wednesday, January 16, 2019 12:18 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] REMINDER: Proposal for Container 
Management Enhancements - Call for Community Input

I second the ability to merge containers!  
Lydia

From:  on behalf of 
Valerie Addonizio 
Reply-To: Archivesspace Users Group 

Date: Wednesday, January 16, 2019 at 1:17 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] REMINDER: Proposal for Container 
Management Enhancements - Call for Community Input

I know that the comment period is closed, but this seemed like a logical place 
to ask whether the idea of container merging functionality was considered as 
part of this effort (I know it is not in the scope of work, but was it 
considered and not selected?) and whether other institutions are in need of 
such functionality?

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Bowers, Kate A.
Sent: Thursday, December 20, 2018 4:16 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] REMINDER: Proposal for Container 
Management Enhancements - Call for Community Input

Dear ArchivesSpace community:

Apologies for the length of this. I’ll try to address a lot of comments, but 
not all!  Please let me know if (as they may well do) my elaborations only 
elicit more questions!

In general, most of these proposals are derived from facing problems of scale. 
Harvard has 30 repositories and over 200 users of ArchivesSpace. Others have to 
do with managing “medium rare” materials’ locations and containers in 
ArchivesSpace.  (Medium-rare is a tongue-in-cheek term used to cover materials 
that might exist in multiple manifestations but that have archival or rare 
characteristics or treatment. Examples include entire libraries ingested into 
an archives, author’s own copies of their books, annotated books, or the record 
copy of serials or reports kept by institutional archives.)

 • Multi-field top container indicators
 Some commenters wondered if the multiple fields were to accommodate child 
containers. To clarify, the suggestion was to facilitate parsing top container 
identifiers.  As a few commenters have surmised, this is to cope with legacy 
numbers.  These are especially common on medium-rare materials.
 One suggestion was to use a sort algorithm that would obviate the need for 
separated fields for data. However, because there would be is more than one 
algorithm necessary over the installation, such a solution would require an 
added field to identify the algorithm and probably a third field retain a value 
derived by the algorithm to be sorted alphanumerically. Thus, the direct 
3-field solution seems simpler. (A 4-field suggestion was mooted in the 
committee as potentially more useful communally.) It does occur to me that 
there just might not be enough really old, really big repositories with lots of 
legacy identifiers in the ArchivesSpace community for the parsing of legacy 
numbers to be a common problem. I appreciate the recognition that a plug-in 
might be needed instead, but it would be worth hearing from any repositories 
with similar issues.

 • Container and location profiles by repository
   We were envisioning a one-to-one profile-to-repository scenario. Due to 
the ArchivesSpace staff user interface requirement that one identify only

Re: [Archivesspace_Users_Group] EAC-CPF in ASpace

[Christine Di Bella]

Hi Celia,

Others can address how they’re working around the limits of current 
ArchivesSpace support for EAC-CPF, but I’ll just mention what’s planned for the 
application in terms of fuller EAC-CPF support, including the ability to 
exchange records with SNAC. A community specification, authored by Cory Nimer, 
Brad Westbrook, and Sue Luftschein, was circulated about 2 years ago and 
finalized later that year. You can see the specification components and its 
updates in the comments to this JIRA issue: 
https://archivesspace.atlassian.net/browse/ANW-429. We’ve been slowly building 
in some pieces of the functionality requested, such as the additional control 
over merging agents which came out in 2.5.2, and are currently working on the 
data model changes that form the core of what’s needed. That work includes 
adding the fields to the underlying database, adding API endpoints, updating 
the views in the staff and public interfaces, and updating the importers and 
exporters. The data model work will appear in the application later this year.

On a parallel but related track, representatives of SNAC are working on the 
mapping between SNAC and ArchivesSpace. In all likelihood, the first goal once 
the data model changes have been made to ArchivesSpace and the 
ArchivesSpace/SNAC mapping is done is to build a plugin (or plugins) for basic 
importing and exporting of these records between the two systems.

Hope that helps,
Christine

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

[ASpaceOrgHomeMedium]



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Celia 
Caust-Ellenbogen
Sent: Monday, June 3, 2019 1:18 PM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] EAC-CPF in ASpace

Hi folks,

We are just starting to think about implementing EAC-CPF at our repository. 
ASpace's agents module supports some EAC-CPF elements, but it seems like some 
are missing, or maybe I am just not seeing how to utilize them. (For example, 
how to create a  if the resource is owned by another 
repository and not in my ASpace instance?)

I would love to hear from other folks who are using EAC-CPF. Are you using 
ASpace to create the records? Also curious if you are using a different 
interface besides ASpace (and besides SNAC) to display the records?

Best,
Celia

--
Celia Caust-Ellenbogen (she/her/hers<https://www.mypronouns.org/she-her>)
Friends Historical Library of Swarthmore 
College<http://swarthmore.edu/friends-historical-library>   |   Swarthmore 
College Archives<https://swarthmore.edu/archives>
ccaus...@swarthmore.edu<mailto:ccaus...@swarthmore.edu>
610-328-8496


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

[Archivesspace_Users_Group] ArchivesSpace v2.6.0 now available

[Christine Di Bella]

ArchivesSpace is announcing the availability of v2.6.0. You can download it at 
https://github.com/archivesspace/archivesspace/releases/tag/v2.6.0.

This release contains program-led and community pull requests that provide 
feature enhancements, bug fixes, infrastructure improvements and documentation 
updates. There are a number of small changes to the staff and public interfaces 
to improve usability and clarity. There is also a significant revamp of how 
background jobs run, including a new reports page layout. This release also has 
a new feature guided by a community-initiated and authored specification, the 
option to generate human-readable URLs for use in the public user interface. A 
full list of the changes and improvements is provided on the release page.

Thanks very much to community members Br. Paul, Blake Carver, Mark Cooper, Tim 
DiLauro, Bobbi Fox, Brian Harrington, dvhassel, Adam Jazairi, Steve Majewski, 
Dave Mayo, Curtis Poston, Austin Schaffer, and Trevor Thornton for their code 
contributions to this release. Thanks also to the contract developer we have 
been able to engage through member funds, Manny Rodriguez (via LibraryHost), 
for his substantial efforts on the human-readable URLs feature. Thanks as 
always to LYRASIS Digital Technology Services for their technical support. This 
release is also very much a testament to the efforts of our Development 
Prioritization sub-team, Testing sub-team, Technical Documentation sub-team, 
and Core Committers Group, as well as individual ArchivesSpace users like Celia 
Caust-Ellenbogen, Cory Nimer, and Rachel Searcy, who identified and helped us 
work through particular bug fixes and new features in this release.

Within the program, our co-op student Sarah Morrissey did amazing work in 
providing a number of community-requested improvements to the staff and public 
interfaces (many of them recommended by the Staff Interface Enhancement Working 
Group last year). And though I don't always call them out in release 
announcements, I would be remiss if I didn't mention that Technical Lead Laney 
McGlohon and Junior Developer Lora Woodford worked through a tremendous amount 
of their own code and that of others to bring this packed release to you. We 
are very fortunate to have such a wonderful community-based and user-focused 
developer team.

Information on upgrading to a new version of ArchivesSpace is available at 
http://archivesspace.github.io/archivesspace/user/upgrading-to-a-new-release-of-archivesspace/.
 If you have not yet upgraded to a recent version, we recommend going directly 
to 2.6.0. Please note that a complete reindex is required for this release.

Please let us know if you have any questions or need help upgrading. We are 
turning our attention to some needed infrastructure improvements for the 
application, but also aim for some work on agents and recording language 
information that will make ArchivesSpace more standards-compliant in these 
areas to be ready to go into the application in a release later this summer. 
We'll be updating the roadmap on the wiki in the next few days.

Christine

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

[ASpaceOrgHomeMedium]

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

[Archivesspace_Users_Group] release candidate available - ArchivesSpace v2.6.0-RC1

[Christine Di Bella]

Hello ArchivesSpace members,

The ArchivesSpace team is pleased to announce a release candidate, v2.6.0-RC1. 
You can download it at 
https://github.com/archivesspace/archivesspace/releases/tag/v2.6.0-RC1 or test 
it out without downloading at http://test.archivesspace.org/staff (username 
admin /password admin). We do encourage you to download and try it out with 
your own local setup and/or data if you can for the most accurate results.

This release candidate contains program-led and community pull requests that 
provide feature enhancements, bug fixes, infrastructure improvements, and 
documentation updates. You'll see many small changes to the staff and public 
interfaces that came out of community-prioritized requests. There is also a 
significant revamp of how background jobs run, including a new reports page 
layout. While testing, we highly encourage you to not only check out the new 
changes, but also to make sure that features you already use are working as 
intended.

This release candidate also has a new feature guided by a community-initiated 
and authored specification, the option to generate human-readable URLs for use 
in the public user interface. Human-readable urls can help improve the user 
experience and also contribute to Search Engage Optimization (SEO). More 
information about how human-readable URLs work in ArchivesSpace is available at 
https://docs.google.com/document/d/1ycNuk86TD9jGHS5YzTw3tjQY3Kuln3F4fvR7kLlfigQ/edit?usp=sharing.
 I encourage you to contribute ideas and even edits to this documentation while 
testing human-readable urls. Thanks to Celia Caust-Ellenbogen and Cory Nimer 
for authoring and circulating the human-readable URLs specification throughout 
the community last year.

Thanks to the many community members who made contributions to the work 
reflected in this release candidate, including individual archives staff and 
developers, our Development Prioritization sub-team, Testing sub-team, 
Technical Documentation sub-team, and the Core Committers Group.

We'll be collecting feedback through Friday, May 24. Please let us know at 
archivesspaceh...@lyrasis.org<mailto:archivesspaceh...@lyrasis.org> if you 
notice any problems with the specific areas addressed in this release, or if 
anything that was working before no longer is. Barring major issues, we expect 
to release v2.6.0 by the end of the month.

Christine

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

[ASpaceOrgHomeMedium]

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

[Archivesspace_Users_Group] open call on ArchivesSpace reports - Wednesday, April 3 at 1:00 p.m. EDT / 10 a.m. PDT

[Christine Di Bella]

Please join the Reports sub-team of the ArchivesSpace User Advisory Council 
this Wednesday, April 3, at 1:00 EDT / 10 a.m. PDT for an open call on reports. 
The Reports sub-team is interested in learning about the community's use of the 
existing reports, use cases, and pain points. The sub-team will use this 
feedback to inform their next steps.

Some questions and discussion items are posted on the wiki page for the call: 
https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/834994187/2019-04-03+UAC+Reports+Open+Call.
 Feel free to add more by using the comments section on the page. Connection 
information is provided below.

If you have any questions, please contact Alston Cobourn, Reports sub-team 
leader (cobourn...@ecu.edu), or me. We hope to see a 
number of you there!

Connection information:
https://zoom.us/j/926134522

Dial by your location (if you cannot connect to the audio with your computer)
+1 646 876 9923 US (New York)
+1 669 900 6833 US (San Jose)
Meeting ID: 926 134 522
Find your local number: https://zoom.us/u/abY0PUiwRs
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] ArchivesSpace Update - March 2019

[Christine Di Bella]

[ASpaceOrgHome.jpg]

March 2019 Update
Development

We continue to work on our next release, which, pending further development and 
testing, we are aiming to put out in April. Thanks to all who have helped with 
testing or pull requests so far.

ArchivesSpace is always interested in more development help. Depending on your 
interest and availability, we have lots of suggestions for projects small and 
big that developers and tech-savvy archivists of all experience levels could 
help with to make ArchivesSpace better for everyone. If you're interested in 
writing code and helping with ArchivesSpace development, or if you know someone 
who might be, please contact Program Manager Christine Di Bella 
(christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>) or Tech 
Lead Laney McGlohon 
(laney.mcglo...@lyrasis.org<mailto:laney.mcglo...@lyrasis.org>) for more 
details.

Open Call on Reports - April 3

Please join us at 1:00 p.m. Eastern time on Wednesday, April 3, for an 
ArchivesSpace open call discussion focused on reports.  The User Advisory 
Council Reports sub-team is interested in learning about the community's use of 
the existing reports, use cases, and pain points. The sub-team will use this 
feedback to inform their next steps. Some questions and discussion items are 
posted on the wiki page for the call. Feel free to add more by using the 
comments section on the page. 
https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/834994187/2019-04-03+UAC+Reports+Open+Call.

Connection information:

https://zoom.us/j/926134522

Dial by your location (if you cannot connect to the audio with your computer)

+1 646 876 9923 US (New York)

+1 669 900 6833 US (San Jose)

Meeting ID: 926 134 522

Find your local number: https://zoom.us/u/abY0PUiwRs

Follow Up from ArchivesSpace Online Forum - March 18

Thank you to all who attended our first Online Forum on March 18. We were so 
thrilled with the variety of speakers, topics, and attendees, and the 
possibilities for the future. Links to presentations, notes, and other 
materials are at 
https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/802127927/ASpace+Online+Forum+2019.
 We are still editing the recordings, but hope to make them available soon.

Given the wonderful response, we expect to hold similar events in the future, 
but we want to hear from you what you liked, what would have made it better, 
and your ideas for future topics, speakers, and formats. Please fill out an 
evaluation to give us your feedback: https://www.surveymonkey.com/r/7VXYKQK.

Nominations Being Accepted for Our Advisory Councils Through April 19

Community governance is vital to ArchivesSpace, and the community members that 
serve on our governance groups provide essential leadership and coordination 
for a wide range of activities. More information about these groups is 
available at https://archivesspace.org/governance-board-and-councils.

The Nominating Committee is accepting nominations for several openings on our 
User Advisory Council and Technical Advisory Council through April 19. The User 
Advisory Council is open to those from ArchivesSpace member institutions only. 
The Technical Advisory Council is open to non-members as well. We especially 
encourage those from small institutions and non-academic institutions to apply. 
If you have questions about or are interested in nominating yourself or someone 
else for a two-year term on one of the Councils, please contact Christine Di 
Bella (christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>).

Connect with ArchivesSpace in Person

Christine will be at the Midwest Archives Conference (MAC) annual meeting in 
Detroit from April 4-5. Come find her in the exhibit hall to talk about the 
ArchivesSpace application, our community activities, membership, and more. Our 
organizational home, LYRASIS, will also have a table at MAC, and Tom Clareson 
(Senior Digital and Preservation Services Consultant ) and Katy Klettinger 
(Outreach Representative, Mid-Atlantic & Great Lakes ) will be on hand to 
advise on the many services LYRASIS offers, including ArchivesSpace hosting. 
You can also catch up with Katy at the LYRASIS happy hour at Ready Player 
One<https://www.rpodetroit.com/>, 407 E. Fort St., on Friday April 5 from 5-7 
p.m.

Hannah Rosen (Licensing Specialist and Digitization Program Coordinator) will 
host a LYRASIS happy hour at the Mid-Atlantic Regional Archives Conference 
(MARAC) spring meeting in Morgantown, West Virginia, on Thursday, April 11, 
from 6-7:30 p.m., at Table 9<http://dinetable9.com/>, 40 Donley St. You can 
also meet up with Hannah at the LYRASIS table in the exhibit hall on Friday, 
April 12.

Membership Update

We are excited to welcome our newest members to our community! Our new members 
since February 28 include:

  *   Medical University of South Carolina
  *   Mike Kelley Foundation for the Arts
  *   Pratt Institute Libraries

A