From alphie at hawaii.edu  Fri Dec  2 14:45:49 2022
From: alphie at hawaii.edu (Alphie Garcia)
Date: Fri, 2 Dec 2022 09:45:49 -1000
Subject: [Archivesspace_Users_Group] HTTPS Setup on a Windows machine
Message-ID: <CAE1TGfjs8gDT4WSu4OUOSWYS__CrQ5cjiMrCHNxBPZhxi3MOUg@mail.gmail.com>

Hello all,

I'm running this past the group to see if anyone else has run into this
issue. We ran the ArchivesSpace installer out of the box on a windows
machine and can't figure out how to get HTTPS to work. I do see there is
the documentation for HTTPS via Apache and Ngnix but I believe the
installer comes with Jetty and there doesn't seem to be anything for that
in the help files about that:
https://archivesspace.github.io/tech-docs/provisioning/https.html

Right now, our IT person has been able to configure IIS for the
public-facing side, but that leaves the staff-facing side as HTTP.
Ideally, we want HTTPS on all ports.

Hope this makes sense as I'm the middle-man passing info between a
technical expert and this group.

Thank you,



*______________________________________________________________________________________________________*

*Alphie Garcia | *Information Resources and Collection Management Librarian
 | James & Abigail Campbell Library at the University of Hawai'i - West
O'ahu *| *91-1001 Farrington Hwy.,

Kapolei, HI 96707* |* Tel:* (808) 689-2708 *| Email:* alphie at hawaii.edu
<alphie at hawaii.edu> | **Subscribe for the * <http://go.hawaii.edu/jzC>*latest
Library news* <http://go.hawaii.edu/jzC> | *Make an appointment*
<https://calendly.com/alphie>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221202/6cd76097/attachment.html>

From brian.hoffman at lyrasis.org  Fri Dec  2 15:00:22 2022
From: brian.hoffman at lyrasis.org (Brian Hoffman)
Date: Fri, 2 Dec 2022 20:00:22 +0000
Subject: [Archivesspace_Users_Group] HTTPS Setup on a Windows machine
In-Reply-To: <CAE1TGfjs8gDT4WSu4OUOSWYS__CrQ5cjiMrCHNxBPZhxi3MOUg@mail.gmail.com>
References: <CAE1TGfjs8gDT4WSu4OUOSWYS__CrQ5cjiMrCHNxBPZhxi3MOUg@mail.gmail.com>
Message-ID: <DM8PR22MB275789DF36DDFAF8F0317F47FC179@DM8PR22MB2757.namprd22.prod.outlook.com>

Hi,

The easiest and recommend way to do this is to place ArchivesSpace behind a proxy server ? typically nginx or apache. The proxy server can handle the entire SSL layer and you won?t need to expose the Jetty server to the world.

Brian

From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Alphie Garcia <alphie at hawaii.edu>
Date: Friday, December 2, 2022 at 2:46 PM
To: archivesspace_users_group at lyralists.lyrasis.org <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] HTTPS Setup on a Windows machine
Hello all,

I'm running this past the group to see if anyone else has run into this issue. We ran the ArchivesSpace installer out of the box on a windows machine and can't figure out how to get HTTPS to work. I do see there is the documentation for HTTPS via Apache and Ngnix but I believe the installer comes with Jetty and there doesn't seem to be anything for that in the help files about that: https://archivesspace.github.io/tech-docs/provisioning/https.html

Right now, our IT person has been able to configure IIS for the public-facing side, but that leaves the staff-facing side as HTTP.  Ideally, we want HTTPS on all ports.

Hope this makes sense as I'm the middle-man passing info between a technical expert and this group.

Thank you,



______________________________________________________________________________________________________

Alphie Garcia | Information Resources and Collection Management Librarian | James & Abigail Campbell Library at the University of Hawai'i - West O'ahu | 91-1001 Farrington Hwy.,

Kapolei, HI 96707 | Tel: (808) 689-2708 | Email: alphie at hawaii.edu<mailto:alphie at hawaii.edu> | Subscribe for the <http://go.hawaii.edu/jzC> latest Library news<http://go.hawaii.edu/jzC> | Make an appointment<https://calendly.com/alphie>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221202/3493d155/attachment.html>

From nigel.bond at auckland.ac.nz  Sun Dec  4 21:10:26 2022
From: nigel.bond at auckland.ac.nz (Nigel Bond)
Date: Mon, 5 Dec 2022 02:10:26 +0000
Subject: [Archivesspace_Users_Group] LCNAF plugin
Message-ID: <SY6PR01MB7670EF7B093E7E045F6ACE98B7189@SY6PR01MB7670.ausprd01.prod.outlook.com>

Hi all,
We have recently upgraded to AS 3.3.1, and all seems to working fine apart for the Library of Congress LCNAF plugin.
We are not sure whether we still need to use a plugin, or if it is now embedded in the new version of AS.
Can anybody please assist us, in advising how we get this to work.

Thank you in advance.

Nigel Bond

Dr. Nigel Bond (he/him)
Team Leader
Cultural Collections (Special Collections)
Waipapa Taumata Rau, University of Auckland

Special Collections: Celebrating 20 years

[cid:image001.png at 01D908BB.B40C1EA0]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221205/5a5d2f93/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 6317 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221205/5a5d2f93/attachment.png>

From jmhutchens at anderson.edu  Mon Dec  5 09:07:44 2022
From: jmhutchens at anderson.edu (Jared Hutchens)
Date: Mon, 5 Dec 2022 09:07:44 -0500
Subject: [Archivesspace_Users_Group] LCNAF plugin
In-Reply-To: <SY6PR01MB7670EF7B093E7E045F6ACE98B7189@SY6PR01MB7670.ausprd01.prod.outlook.com>
References: <SY6PR01MB7670EF7B093E7E045F6ACE98B7189@SY6PR01MB7670.ausprd01.prod.outlook.com>
Message-ID: <CABdH0zkk_XaOGGembJ58jkjns615C6T0jF1gTANoFmOzBX+K-w@mail.gmail.com>

Hi Nigel,

We recently resolved an issue with the LCNAF plugin failing to give any
results (running v3.1). In our case it was due to the plugin files being
incomplete, several lines were missing which I added back referencing
Github build. Not sure if that's the issue you're facing but I hope this
helps.

Thanks,
Jared


<https://anderson.edu/>

Jared Hutchens

Library Technology Specialist

Nicholson Library

o: (765) 641-4270

https://library.anderson.edu

This message contains confidential information and is intended only for the
individual named. If you are not the named addressee you should not
disseminate, distribute or copy this email. Please notify the sender
immediately by email if you have received this email by mistake and delete
this email from your system.


On Sun, Dec 4, 2022 at 9:10 PM Nigel Bond <nigel.bond at auckland.ac.nz> wrote:

> Hi all,
>
> We have recently upgraded to AS 3.3.1, and all seems to working fine apart
> for the Library of Congress LCNAF plugin.
>
> We are not sure whether we still need to use a plugin, or if it is now
> embedded in the new version of AS.
>
> Can anybody please assist us, in advising how we get this to work.
>
>
>
> Thank you in advance.
>
>
>
> Nigel Bond
>
>
>
> *Dr. Nigel Bond (he/him)*
>
> *Team Leader*
>
> Cultural Collections (Special Collections)
>
> Waipapa Taumata Rau, University of Auckland
>
>
>
> *Special Collections: Celebrating 20 years*
>
>
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221205/0d359f4f/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 6317 bytes
Desc: not available
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221205/0d359f4f/attachment.png>

From tessa.wakefield at uni.edu  Mon Dec  5 12:08:32 2022
From: tessa.wakefield at uni.edu (Tessa Wakefield)
Date: Mon, 5 Dec 2022 11:08:32 -0600
Subject: [Archivesspace_Users_Group] How does searching with the dates
	filled out work?
Message-ID: <CAD1+Wkksj2Kjzyt6E=wseCLQRVie24BZVmesO6--ATYB-xLxxA@mail.gmail.com>

Hello!
Forgive me if this is a silly question -- we're new to using ArchivesSpace!
I'm confused as to how the dates work when entered in the search function
("From year" and "To year" boxes). Does narrowing your search by date range
only pull records marked with dates that fall within? I've tried doing this
in our Aspace instance, as well as in a few others, and results show up
that are not within the dates. For example, with a parameter of 1900 to
2000, results with dates from the 1800s were included. I think I'm not
understanding how this actually works and before we go live for our users
to access our finding aids, I want to make sure we know what we're talking
about!

Thanks!

-- 
*Tessa Wakefield (she/her <https://www.mypronouns.org/>)*

Archival Processor & Reference Associate
Rod Library

319-273-2132

LIB 342  /  Cedar Falls, IA 50614
uni.edu  /  #1UNI
*To schedule an appointment, please visit **LibCal
<https://uni.libcal.com/appointments/scua>.*
[image: UNI / University of Northern Iowa]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221205/8cf9f58c/attachment.html>

From christine.dibella at lyrasis.org  Mon Dec  5 15:03:36 2022
From: christine.dibella at lyrasis.org (Christine Di Bella)
Date: Mon, 5 Dec 2022 20:03:36 +0000
Subject: [Archivesspace_Users_Group] updated ArchivesSpace roadmap
Message-ID: <MN2PR22MB1887D24F8EDEAF8CB9F84ED4F1189@MN2PR22MB1887.namprd22.prod.outlook.com>

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.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
678-235-2905

[ASpaceOrgHomeMedium]

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

From andrew.morrison at bodleian.ox.ac.uk  Tue Dec  6 04:03:08 2022
From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison)
Date: Tue, 6 Dec 2022 09:03:08 +0000
Subject: [Archivesspace_Users_Group] How does searching with the dates
 filled out work?
In-Reply-To: <CAD1+Wkksj2Kjzyt6E=wseCLQRVie24BZVmesO6--ATYB-xLxxA@mail.gmail.com>
References: <CAD1+Wkksj2Kjzyt6E=wseCLQRVie24BZVmesO6--ATYB-xLxxA@mail.gmail.com>
Message-ID: <dc078954-60a0-dc10-f930-860eee1da628@bodleian.ox.ac.uk>

All dates in the "Dates" section of a record are indexed for use in 
date-range searches, regardless of the label.

For example, if something was created between 1880 and 1885, but it was 
also published in June 1950, and digitized on 4th May 2010, then it'll 
be indexed with the years 1880, 1881, 1882, 1883, 1884, 1885, 1950, and 
2010. Therefore, as well as matching searches with a date range of 
1800-1900, it'll also match 1900-2000, or even 2000-present. But it 
won't match dates ranges in the gaps between, i.e. any subset of 
1886-1949 or 1951-2009.

It would be possible to write a plug-in to choose which dates to index.

Andrew.


On 05/12/2022 17:08, Tessa Wakefield wrote:
> Hello!
> Forgive me if this is a silly?question -- we're new to using 
> ArchivesSpace! I'm confused as to how the dates work when entered in 
> the search function ("From year" and "To year" boxes). Does narrowing 
> your search by date range only pull records marked with dates that 
> fall within? I've tried doing?this in our Aspace instance, as well as 
> in a few others, and results show up that are not within the dates. 
> For example, with a parameter?of 1900 to 2000, results?with dates from 
> the 1800s were included. I think I'm not understanding how this 
> actually works and before we go live for our users to access our 
> finding aids, I want to make sure we know what we're talking about!
>
> Thanks!
>
> -- 
> *Tessa Wakefield(she/her <https://www.mypronouns.org/>)*
>
> Archival Processor & Reference Associate
>
> Rod Library
>
> 319-273-2132
>
> LIB 342? / Cedar Falls, IA 50614
>
> uni.edu <https://uni.edu/>? / #1UNI
> *To schedule an appointment, please visit **LibCal 
> <https://uni.libcal.com/appointments/scua>.*
> UNI / University of Northern Iowa**
>
>
>
>
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221206/1883157f/attachment.html>

From dsteelma at umd.edu  Tue Dec  6 14:02:33 2022
From: dsteelma at umd.edu (David P. Steelman)
Date: Tue, 6 Dec 2022 14:02:33 -0500
Subject: [Archivesspace_Users_Group] Startup error with ArchivesSpace
	v3.3.1/aspace-oauth plugin
Message-ID: <CA+mHiJZMp9Qe4D6PxTiSfCMNc5LZDcHpKi=H_Zv6h6CAOuiK=g@mail.gmail.com>

Hello all,

In attempting to upgrade from ArchivesSpace v3.1.1 to v3.3.1, I am
encountering the following error on startup:

----
  Dec 05, 2022 8:23:43 PM
org.eclipse.jetty.server.handler.ContextHandler$Context log
  WARNING: ERROR: initialization failed
  org.jruby.rack.RackInitializationException: Could not find
public_suffix-4.0.6 in any of the sources
  from
/apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:86:in
`block in materialize'
  from org/jruby/RubyArray.java:2621:in `map!'
  from
/apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:80:in
`materialize'
  from
/apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:170:in
`specs'
  ...
----

We are using the "aspace-oauth" plugin (
https://github.com/lyrasis/aspace-oauth) -- if we remove this plugin from
the configuration the error does not occur.

Comparing the ArchivesSpace v3.1.1 distribution to v3.3.1, the "gems/gems"
directory in the v3.3.1 distribution includes significantly fewer gems, and
no longer includes a "public_suffix-3.0.6" directory.

Any pointers in handling this issue are appreciated.

Thanks,

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

From hanstra at nd.edu  Tue Dec  6 14:14:31 2022
From: hanstra at nd.edu (Tom Hanstra)
Date: Tue, 6 Dec 2022 14:14:31 -0500
Subject: [Archivesspace_Users_Group] Startup error with ArchivesSpace
 v3.3.1/aspace-oauth plugin
In-Reply-To: <CA+mHiJZMp9Qe4D6PxTiSfCMNc5LZDcHpKi=H_Zv6h6CAOuiK=g@mail.gmail.com>
References: <CA+mHiJZMp9Qe4D6PxTiSfCMNc5LZDcHpKi=H_Zv6h6CAOuiK=g@mail.gmail.com>
Message-ID: <CAA60kZMY+1pma6Wt4r7gjf5X_jujSxDv7amjtVfLDG-8813+8A@mail.gmail.com>

Be sure to run the initialize_plugin script again after the upgrade.

Tom

On Tue, Dec 6, 2022 at 2:06 PM David P. Steelman <dsteelma at umd.edu> wrote:

> Hello all,
>
> In attempting to upgrade from ArchivesSpace v3.1.1 to v3.3.1, I am
> encountering the following error on startup:
>
> ----
>   Dec 05, 2022 8:23:43 PM
> org.eclipse.jetty.server.handler.ContextHandler$Context log
>   WARNING: ERROR: initialization failed
>   org.jruby.rack.RackInitializationException: Could not find
> public_suffix-4.0.6 in any of the sources
>   from
> /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:86:in
> `block in materialize'
>   from org/jruby/RubyArray.java:2621:in `map!'
>   from
> /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:80:in
> `materialize'
>   from
> /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:170:in
> `specs'
>   ...
> ----
>
> We are using the "aspace-oauth" plugin (
> https://github.com/lyrasis/aspace-oauth) -- if we remove this plugin from
> the configuration the error does not occur.
>
> Comparing the ArchivesSpace v3.1.1 distribution to v3.3.1, the "gems/gems"
> directory in the v3.3.1 distribution includes significantly fewer gems, and
> no longer includes a "public_suffix-3.0.6" directory.
>
> Any pointers in handling this issue are appreciated.
>
> Thanks,
>
> David
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>


-- 
*Tom Hanstra*
*Sr. Systems Administrator*
hanstra at nd.edu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221206/d2694bc5/attachment.html>

From blake.carver at lyrasis.org  Tue Dec  6 14:18:53 2022
From: blake.carver at lyrasis.org (Blake Carver)
Date: Tue, 6 Dec 2022 19:18:53 +0000
Subject: [Archivesspace_Users_Group] Startup error with
	ArchivesSpace	v3.3.1/aspace-oauth plugin
In-Reply-To: <CA+mHiJZMp9Qe4D6PxTiSfCMNc5LZDcHpKi=H_Zv6h6CAOuiK=g@mail.gmail.com>
References: <CA+mHiJZMp9Qe4D6PxTiSfCMNc5LZDcHpKi=H_Zv6h6CAOuiK=g@mail.gmail.com>
Message-ID: <DM6PR22MB23091620C6C6CB229A671F209F1B9@DM6PR22MB2309.namprd22.prod.outlook.com>

Try using the latest tag version on that plugin.


 https://github.com/lyrasis/aspace-oauth/tags
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of David P. Steelman <dsteelma at umd.edu>
Sent: Tuesday, December 6, 2022 2:02 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Startup error with ArchivesSpace v3.3.1/aspace-oauth plugin

Hello all,

In attempting to upgrade from ArchivesSpace v3.1.1 to v3.3.1, I am encountering the following error on startup:

----
  Dec 05, 2022 8:23:43 PM org.eclipse.jetty.server.handler.ContextHandler$Context log
  WARNING: ERROR: initialization failed
  org.jruby.rack.RackInitializationException: Could not find public_suffix-4.0.6 in any of the sources
  from /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:86:in `block in materialize'
  from org/jruby/RubyArray.java:2621:in `map!'
  from /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:80:in `materialize'
  from /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:170:in `specs'
  ...
----

We are using the "aspace-oauth" plugin (https://github.com/lyrasis/aspace-oauth) -- if we remove this plugin from the configuration the error does not occur.

Comparing the ArchivesSpace v3.1.1 distribution to v3.3.1, the "gems/gems" directory in the v3.3.1 distribution includes significantly fewer gems, and no longer includes a "public_suffix-3.0.6" directory.

Any pointers in handling this issue are appreciated.

Thanks,

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

From hanstra at nd.edu  Tue Dec  6 14:55:12 2022
From: hanstra at nd.edu (Tom Hanstra)
Date: Tue, 6 Dec 2022 14:55:12 -0500
Subject: [Archivesspace_Users_Group] Startup error with ArchivesSpace
 v3.3.1/aspace-oauth plugin
In-Reply-To: <DM6PR22MB23091620C6C6CB229A671F209F1B9@DM6PR22MB2309.namprd22.prod.outlook.com>
References: <CA+mHiJZMp9Qe4D6PxTiSfCMNc5LZDcHpKi=H_Zv6h6CAOuiK=g@mail.gmail.com>
 <DM6PR22MB23091620C6C6CB229A671F209F1B9@DM6PR22MB2309.namprd22.prod.outlook.com>
Message-ID: <CAA60kZPhA5dQAMeGx-=f+O_5ZPtPHw4aZz1Gtj1NR3kqvNSjMw@mail.gmail.com>

There was a version of the aspace-oauth plugin in which the public_suffix
gem did not compile. I remember having some problems with that.

I just rebuilt mine here and it looks like the current version is working
right, with the 4.0.7 version. So it may help to simply download again.

Tom

On Tue, Dec 6, 2022 at 2:19 PM Blake Carver <blake.carver at lyrasis.org>
wrote:

> Try using the latest tag version on that plugin.
>
>
>  https://github.com/lyrasis/aspace-oauth/tags
> ------------------------------
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org <
> archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of
> David P. Steelman <dsteelma at umd.edu>
> *Sent:* Tuesday, December 6, 2022 2:02 PM
> *To:* Archivesspace Users Group <
> archivesspace_users_group at lyralists.lyrasis.org>
> *Subject:* [Archivesspace_Users_Group] Startup error with ArchivesSpace
> v3.3.1/aspace-oauth plugin
>
> Hello all,
>
> In attempting to upgrade from ArchivesSpace v3.1.1 to v3.3.1, I am
> encountering the following error on startup:
>
> ----
>   Dec 05, 2022 8:23:43 PM
> org.eclipse.jetty.server.handler.ContextHandler$Context log
>   WARNING: ERROR: initialization failed
>   org.jruby.rack.RackInitializationException: Could not find
> public_suffix-4.0.6 in any of the sources
>   from
> /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:86:in
> `block in materialize'
>   from org/jruby/RubyArray.java:2621:in `map!'
>   from
> /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:80:in
> `materialize'
>   from
> /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:170:in
> `specs'
>   ...
> ----
>
> We are using the "aspace-oauth" plugin (
> https://github.com/lyrasis/aspace-oauth) -- if we remove this plugin from
> the configuration the error does not occur.
>
> Comparing the ArchivesSpace v3.1.1 distribution to v3.3.1, the "gems/gems"
> directory in the v3.3.1 distribution includes significantly fewer gems, and
> no longer includes a "public_suffix-3.0.6" directory.
>
> Any pointers in handling this issue are appreciated.
>
> Thanks,
>
> David
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>


-- 
*Tom Hanstra*
*Sr. Systems Administrator*
hanstra at nd.edu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221206/11fd5266/attachment.html>

From dsteelma at umd.edu  Tue Dec  6 15:03:36 2022
From: dsteelma at umd.edu (David P. Steelman)
Date: Tue, 6 Dec 2022 15:03:36 -0500
Subject: [Archivesspace_Users_Group] Startup error with ArchivesSpace
 v3.3.1/aspace-oauth plugin
In-Reply-To: <CAA60kZPhA5dQAMeGx-=f+O_5ZPtPHw4aZz1Gtj1NR3kqvNSjMw@mail.gmail.com>
References: <CA+mHiJZMp9Qe4D6PxTiSfCMNc5LZDcHpKi=H_Zv6h6CAOuiK=g@mail.gmail.com>
 <DM6PR22MB23091620C6C6CB229A671F209F1B9@DM6PR22MB2309.namprd22.prod.outlook.com>
 <CAA60kZPhA5dQAMeGx-=f+O_5ZPtPHw4aZz1Gtj1NR3kqvNSjMw@mail.gmail.com>
Message-ID: <CA+mHiJZGf8ARQn4tUpy4oQELp0Jyg4ZcaMzW-Q6g1C27r0UA+g@mail.gmail.com>

Thanks for the quick responses.

I have tried using aspace-oauth v3.2.0, and am running the
'initialize_plugin" script, and still receiving the same error.

On the server, there is a
"plugins/aspace-oauth/gems/cache/public_suffix-4.0.7.gem" file, and a
"plugins/aspace-oauth/gems/gems/public_suffix-4.0.7" directory, so the
"aspace-oauth" gem appears to be using the "public_suffix:4.0.7" gem

The "WEB-INF/Gemfile.lock" file in the "public.war" and "frontend.war" WAR
files from the ArchivesSpace distribution each contain a reference to
"public_suffix" v4.0.6.

In the ArchivesSpace v3.3.1 source distribution there are references to
"plugin_suffix:4.0.6" in the following files:

* Gemfile.lock
* docs/Gemfile.lock
* frontend/Gemfile.lock
* public/Gemfile.lock

So I'm wondering if there is some kind of confusion about which version of
the gem is supposed to be used.

Thanks,

David

On Tue, Dec 6, 2022 at 2:55 PM Tom Hanstra <hanstra at nd.edu> wrote:

> There was a version of the aspace-oauth plugin in which the public_suffix
> gem did not compile. I remember having some problems with that.
>
> I just rebuilt mine here and it looks like the current version is working
> right, with the 4.0.7 version. So it may help to simply download again.
>
> Tom
>
> On Tue, Dec 6, 2022 at 2:19 PM Blake Carver <blake.carver at lyrasis.org>
> wrote:
>
>> Try using the latest tag version on that plugin.
>>
>>
>>  https://github.com/lyrasis/aspace-oauth/tags
>> ------------------------------
>> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org <
>> archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of
>> David P. Steelman <dsteelma at umd.edu>
>> *Sent:* Tuesday, December 6, 2022 2:02 PM
>> *To:* Archivesspace Users Group <
>> archivesspace_users_group at lyralists.lyrasis.org>
>> *Subject:* [Archivesspace_Users_Group] Startup error with ArchivesSpace
>> v3.3.1/aspace-oauth plugin
>>
>> Hello all,
>>
>> In attempting to upgrade from ArchivesSpace v3.1.1 to v3.3.1, I am
>> encountering the following error on startup:
>>
>> ----
>>   Dec 05, 2022 8:23:43 PM
>> org.eclipse.jetty.server.handler.ContextHandler$Context log
>>   WARNING: ERROR: initialization failed
>>   org.jruby.rack.RackInitializationException: Could not find
>> public_suffix-4.0.6 in any of the sources
>>   from
>> /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:86:in
>> `block in materialize'
>>   from org/jruby/RubyArray.java:2621:in `map!'
>>   from
>> /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:80:in
>> `materialize'
>>   from
>> /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:170:in
>> `specs'
>>   ...
>> ----
>>
>> We are using the "aspace-oauth" plugin (
>> https://github.com/lyrasis/aspace-oauth) -- if we remove this plugin
>> from the configuration the error does not occur.
>>
>> Comparing the ArchivesSpace v3.1.1 distribution to v3.3.1, the
>> "gems/gems" directory in the v3.3.1 distribution includes significantly
>> fewer gems, and no longer includes a "public_suffix-3.0.6" directory.
>>
>> Any pointers in handling this issue are appreciated.
>>
>> Thanks,
>>
>> David
>> _______________________________________________
>> Archivesspace_Users_Group mailing list
>> Archivesspace_Users_Group at lyralists.lyrasis.org
>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>>
>
>
> --
> *Tom Hanstra*
> *Sr. Systems Administrator*
> hanstra at nd.edu
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221206/84d6a85c/attachment.html>

From hanstra at nd.edu  Tue Dec  6 15:47:05 2022
From: hanstra at nd.edu (Tom Hanstra)
Date: Tue, 6 Dec 2022 15:47:05 -0500
Subject: [Archivesspace_Users_Group] Startup error with ArchivesSpace
 v3.3.1/aspace-oauth plugin
In-Reply-To: <CA+mHiJZGf8ARQn4tUpy4oQELp0Jyg4ZcaMzW-Q6g1C27r0UA+g@mail.gmail.com>
References: <CA+mHiJZMp9Qe4D6PxTiSfCMNc5LZDcHpKi=H_Zv6h6CAOuiK=g@mail.gmail.com>
 <DM6PR22MB23091620C6C6CB229A671F209F1B9@DM6PR22MB2309.namprd22.prod.outlook.com>
 <CAA60kZPhA5dQAMeGx-=f+O_5ZPtPHw4aZz1Gtj1NR3kqvNSjMw@mail.gmail.com>
 <CA+mHiJZGf8ARQn4tUpy4oQELp0Jyg4ZcaMzW-Q6g1C27r0UA+g@mail.gmail.com>
Message-ID: <CAA60kZPZ6YzHwXEm6F8vp5XQSr+qHHpSLxJX3ue+LQBDgA4wXg@mail.gmail.com>

Try updating the Gemfile.lock to use the 4.0.6 version of the gem and then
run the initialize_plugin script. I'm pretty sure that was how I got around
the issue at one point.

You just need to get the plugin bundled. Version does not matter (in my
experience).

Tom

On Tue, Dec 6, 2022 at 3:03 PM David P. Steelman <dsteelma at umd.edu> wrote:

> Thanks for the quick responses.
>
> I have tried using aspace-oauth v3.2.0, and am running the
> 'initialize_plugin" script, and still receiving the same error.
>
> On the server, there is a
> "plugins/aspace-oauth/gems/cache/public_suffix-4.0.7.gem" file, and a
> "plugins/aspace-oauth/gems/gems/public_suffix-4.0.7" directory, so the
> "aspace-oauth" gem appears to be using the "public_suffix:4.0.7" gem
>
> The "WEB-INF/Gemfile.lock" file in the "public.war" and "frontend.war" WAR
> files from the ArchivesSpace distribution each contain a reference to
> "public_suffix" v4.0.6.
>
> In the ArchivesSpace v3.3.1 source distribution there are references to
> "plugin_suffix:4.0.6" in the following files:
>
> * Gemfile.lock
> * docs/Gemfile.lock
> * frontend/Gemfile.lock
> * public/Gemfile.lock
>
> So I'm wondering if there is some kind of confusion about which version of
> the gem is supposed to be used.
>
> Thanks,
>
> David
>
> On Tue, Dec 6, 2022 at 2:55 PM Tom Hanstra <hanstra at nd.edu> wrote:
>
>> There was a version of the aspace-oauth plugin in which the public_suffix
>> gem did not compile. I remember having some problems with that.
>>
>> I just rebuilt mine here and it looks like the current version is working
>> right, with the 4.0.7 version. So it may help to simply download again.
>>
>> Tom
>>
>> On Tue, Dec 6, 2022 at 2:19 PM Blake Carver <blake.carver at lyrasis.org>
>> wrote:
>>
>>> Try using the latest tag version on that plugin.
>>>
>>>
>>>  https://github.com/lyrasis/aspace-oauth/tags
>>> ------------------------------
>>> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org <
>>> archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of
>>> David P. Steelman <dsteelma at umd.edu>
>>> *Sent:* Tuesday, December 6, 2022 2:02 PM
>>> *To:* Archivesspace Users Group <
>>> archivesspace_users_group at lyralists.lyrasis.org>
>>> *Subject:* [Archivesspace_Users_Group] Startup error with ArchivesSpace
>>> v3.3.1/aspace-oauth plugin
>>>
>>> Hello all,
>>>
>>> In attempting to upgrade from ArchivesSpace v3.1.1 to v3.3.1, I am
>>> encountering the following error on startup:
>>>
>>> ----
>>>   Dec 05, 2022 8:23:43 PM
>>> org.eclipse.jetty.server.handler.ContextHandler$Context log
>>>   WARNING: ERROR: initialization failed
>>>   org.jruby.rack.RackInitializationException: Could not find
>>> public_suffix-4.0.6 in any of the sources
>>>   from
>>> /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:86:in
>>> `block in materialize'
>>>   from org/jruby/RubyArray.java:2621:in `map!'
>>>   from
>>> /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:80:in
>>> `materialize'
>>>   from
>>> /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:170:in
>>> `specs'
>>>   ...
>>> ----
>>>
>>> We are using the "aspace-oauth" plugin (
>>> https://github.com/lyrasis/aspace-oauth) -- if we remove this plugin
>>> from the configuration the error does not occur.
>>>
>>> Comparing the ArchivesSpace v3.1.1 distribution to v3.3.1, the
>>> "gems/gems" directory in the v3.3.1 distribution includes significantly
>>> fewer gems, and no longer includes a "public_suffix-3.0.6" directory.
>>>
>>> Any pointers in handling this issue are appreciated.
>>>
>>> Thanks,
>>>
>>> David
>>> _______________________________________________
>>> Archivesspace_Users_Group mailing list
>>> Archivesspace_Users_Group at lyralists.lyrasis.org
>>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>>>
>>
>>
>> --
>> *Tom Hanstra*
>> *Sr. Systems Administrator*
>> hanstra at nd.edu
>>
>>
>> _______________________________________________
>> Archivesspace_Users_Group mailing list
>> Archivesspace_Users_Group at lyralists.lyrasis.org
>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>


-- 
*Tom Hanstra*
*Sr. Systems Administrator*
hanstra at nd.edu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221206/a808d998/attachment.html>

From cziegler at ulcc.org  Wed Dec  7 09:53:09 2022
From: cziegler at ulcc.org (Cheryl Ziegler)
Date: Wed, 7 Dec 2022 08:53:09 -0600
Subject: [Archivesspace_Users_Group] Top Containers
Message-ID: <CAMASd00N9ud3ZS6qZRsEWURmt=vuugud7nBxH4aQa5iCOeA5hw@mail.gmail.com>

Hello all,

Could someone please help me sort out a way to determine my "top container"
for records? I think I am doing it wrong and I don't want to go any further
until I know what I'm doing and I may need to start all over again with
what is already in the system. My collection is relatively small and not
complicated. I am bringing over records from an Excel spreadsheet.

Any help would be greatly appreciated.
Cheryl

Cheryl L. Ziegler, MLIS
(she/her/hers)
Archivist
Union League Club of Chicago
65 W. Jackson Blvd.
Chicago, IL  60604

P: 312.427.7800 X414
www.ulcc.org

*Find out how the Union League Club of Chicago can help enrich your life
and improve the world by contacting membership at ulcc.org
<membership at ulcc.org> or 312.435.4825 <312.435.4825>.*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221207/6759776a/attachment.html>

From dsteelma at umd.edu  Wed Dec  7 10:42:56 2022
From: dsteelma at umd.edu (David P. Steelman)
Date: Wed, 7 Dec 2022 10:42:56 -0500
Subject: [Archivesspace_Users_Group] Startup error with ArchivesSpace
 v3.3.1/aspace-oauth plugin
In-Reply-To: <CAA60kZPZ6YzHwXEm6F8vp5XQSr+qHHpSLxJX3ue+LQBDgA4wXg@mail.gmail.com>
References: <CA+mHiJZMp9Qe4D6PxTiSfCMNc5LZDcHpKi=H_Zv6h6CAOuiK=g@mail.gmail.com>
 <DM6PR22MB23091620C6C6CB229A671F209F1B9@DM6PR22MB2309.namprd22.prod.outlook.com>
 <CAA60kZPhA5dQAMeGx-=f+O_5ZPtPHw4aZz1Gtj1NR3kqvNSjMw@mail.gmail.com>
 <CA+mHiJZGf8ARQn4tUpy4oQELp0Jyg4ZcaMzW-Q6g1C27r0UA+g@mail.gmail.com>
 <CAA60kZPZ6YzHwXEm6F8vp5XQSr+qHHpSLxJX3ue+LQBDgA4wXg@mail.gmail.com>
Message-ID: <CA+mHiJYpTU4qPxesDhPGqghoZ4Eijzx70gn1qr_6B5LEGfdXJw@mail.gmail.com>

Tom,

Thanks for the suggestion. If I understand you correctly, the suggestion is
to  modify the "Gemfile.lock" file on the "aspace-oauth" gem to change the
"public_suffix" version to 4.0.6.

I gave it a try, and made the following changes to the "Gemfile.lock" file
(and reran the "initialize-plugin.sh" script), and was able to start
ArchivesSpace without error:

* "public_suffix (4.0.7)" to "public_suffix (4.0.6)"
* "addressable (2.8.1)" to "addressable (2.8.0)"
* "public_suffix (>= 2.0.2, < 6.0)" to "public_suffix (>= 2.0.2, < 5.0)"

I wonder, though, if the actual issue is something deeper. The
"addressable"/"public_suffix" gem versions are specified in the following
files of the ArchivesSpace v3.3.1 source code:

* Gemfile.lock (addressable v2.7.0, public_suffix v4.0.6)
* frontend/Gemfile.lock (addressable v2.8.0, public_suffix v4.0.6)
* public/Gemfile.lock (addressable v2.8.0, publix_suffix v4.0.6)

Also, the "backend/Gemfile" specifies the "rubyXL" v3.4.18 gem, which has a
transitive dependency in its "Gemfile.lock" file (
https://github.com/weshatheleopard/rubyXL/blob/v3.4.18/Gemfile.lock) on the
public_suffix v4.0.6 and addressable v2.8.0 gems.

This problem does not seem to occur in our previous version (v3.1.1),
because the addressable v2.80 and public_suffix v4.0.6 gems were provided
in the "gems/gems" directory of the ArchivesSpace v3.1.1 binary
distribution, but are not provided in the v3.3.1 binary distribution.

Since at least one gem (rubyXL) in the ArchiveSpace source code appears to
rely on the addressable/public_suffix gems, should they be included in the
"gems/gems" directory of the ArchivesSpace binary distribution?

Thanks for all the help,

David

On Tue, Dec 6, 2022 at 3:47 PM Tom Hanstra <hanstra at nd.edu> wrote:

> Try updating the Gemfile.lock to use the 4.0.6 version of the gem and then
> run the initialize_plugin script. I'm pretty sure that was how I got around
> the issue at one point.
>
> You just need to get the plugin bundled. Version does not matter (in my
> experience).
>
> Tom
>
> On Tue, Dec 6, 2022 at 3:03 PM David P. Steelman <dsteelma at umd.edu> wrote:
>
>> Thanks for the quick responses.
>>
>> I have tried using aspace-oauth v3.2.0, and am running the
>> 'initialize_plugin" script, and still receiving the same error.
>>
>> On the server, there is a
>> "plugins/aspace-oauth/gems/cache/public_suffix-4.0.7.gem" file, and a
>> "plugins/aspace-oauth/gems/gems/public_suffix-4.0.7" directory, so the
>> "aspace-oauth" gem appears to be using the "public_suffix:4.0.7" gem
>>
>> The "WEB-INF/Gemfile.lock" file in the "public.war" and "frontend.war"
>> WAR files from the ArchivesSpace distribution each contain a reference to
>> "public_suffix" v4.0.6.
>>
>> In the ArchivesSpace v3.3.1 source distribution there are references to
>> "plugin_suffix:4.0.6" in the following files:
>>
>> * Gemfile.lock
>> * docs/Gemfile.lock
>> * frontend/Gemfile.lock
>> * public/Gemfile.lock
>>
>> So I'm wondering if there is some kind of confusion about which version
>> of the gem is supposed to be used.
>>
>> Thanks,
>>
>> David
>>
>> On Tue, Dec 6, 2022 at 2:55 PM Tom Hanstra <hanstra at nd.edu> wrote:
>>
>>> There was a version of the aspace-oauth plugin in which the
>>> public_suffix gem did not compile. I remember having some problems with
>>> that.
>>>
>>> I just rebuilt mine here and it looks like the current version is
>>> working right, with the 4.0.7 version. So it may help to simply download
>>> again.
>>>
>>> Tom
>>>
>>> On Tue, Dec 6, 2022 at 2:19 PM Blake Carver <blake.carver at lyrasis.org>
>>> wrote:
>>>
>>>> Try using the latest tag version on that plugin.
>>>>
>>>>
>>>>  https://github.com/lyrasis/aspace-oauth/tags
>>>> ------------------------------
>>>> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org <
>>>> archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of
>>>> David P. Steelman <dsteelma at umd.edu>
>>>> *Sent:* Tuesday, December 6, 2022 2:02 PM
>>>> *To:* Archivesspace Users Group <
>>>> archivesspace_users_group at lyralists.lyrasis.org>
>>>> *Subject:* [Archivesspace_Users_Group] Startup error with
>>>> ArchivesSpace v3.3.1/aspace-oauth plugin
>>>>
>>>> Hello all,
>>>>
>>>> In attempting to upgrade from ArchivesSpace v3.1.1 to v3.3.1, I am
>>>> encountering the following error on startup:
>>>>
>>>> ----
>>>>   Dec 05, 2022 8:23:43 PM
>>>> org.eclipse.jetty.server.handler.ContextHandler$Context log
>>>>   WARNING: ERROR: initialization failed
>>>>   org.jruby.rack.RackInitializationException: Could not find
>>>> public_suffix-4.0.6 in any of the sources
>>>>   from
>>>> /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:86:in
>>>> `block in materialize'
>>>>   from org/jruby/RubyArray.java:2621:in `map!'
>>>>   from
>>>> /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/spec_set.rb:80:in
>>>> `materialize'
>>>>   from
>>>> /apps/aspace/archivesspace/gems/gems/bundler-2.1.4/lib/bundler/definition.rb:170:in
>>>> `specs'
>>>>   ...
>>>> ----
>>>>
>>>> We are using the "aspace-oauth" plugin (
>>>> https://github.com/lyrasis/aspace-oauth) -- if we remove this plugin
>>>> from the configuration the error does not occur.
>>>>
>>>> Comparing the ArchivesSpace v3.1.1 distribution to v3.3.1, the
>>>> "gems/gems" directory in the v3.3.1 distribution includes significantly
>>>> fewer gems, and no longer includes a "public_suffix-3.0.6" directory.
>>>>
>>>> Any pointers in handling this issue are appreciated.
>>>>
>>>> Thanks,
>>>>
>>>> David
>>>> _______________________________________________
>>>> Archivesspace_Users_Group mailing list
>>>> Archivesspace_Users_Group at lyralists.lyrasis.org
>>>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>>>>
>>>
>>>
>>> --
>>> *Tom Hanstra*
>>> *Sr. Systems Administrator*
>>> hanstra at nd.edu
>>>
>>>
>>> _______________________________________________
>>> Archivesspace_Users_Group mailing list
>>> Archivesspace_Users_Group at lyralists.lyrasis.org
>>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>>>
>> _______________________________________________
>> Archivesspace_Users_Group mailing list
>> Archivesspace_Users_Group at lyralists.lyrasis.org
>> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>>
>
>
> --
> *Tom Hanstra*
> *Sr. Systems Administrator*
> hanstra at nd.edu
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221207/b0aa754b/attachment-0001.html>

From julie_wetherill at harvard.edu  Wed Dec  7 12:22:10 2022
From: julie_wetherill at harvard.edu (Wetherill, Julie M.)
Date: Wed, 7 Dec 2022 17:22:10 +0000
Subject: [Archivesspace_Users_Group] Publish status set incorrectly in
	Accession csv import
Message-ID: <SJ0PR07MB864550AD263F781A377F7DBE8A1A9@SJ0PR07MB8645.namprd07.prod.outlook.com>

Hi all,

We have a problem importing accession records by csv that seems to be limited to a single user's computer.

Accession imports by this staff user are loaded successfully, but the records always land in the system as published despite the accession_publish column being set to '0' (unpublished) across the board. Our public interface doesn't display accessions but PUI solr happily indexes them, so PUI users find these accession records but can't open them. So we don't want published accessions.

We are running v3.0.2 and the user (who I'm calling User 0) is working off a fresh accession csv template pulled from github.

Using the same csv, I am able to import accession records that load as unpublished. And other users in the same repository as User 0 can load that csv and get unpublished records. But not User 0.

All csv editing is done in a text editor and not Excel. I don't think this is an issue with user preferences or permissions (which are the same for everyone who has tested).

Using a hex viewer, I don't see anything funky going on with the value for accession_publish in the csv (it is the number zero).

Any ideas what is causing this weirdness? Many moons ago we had a similar issue importing EADs from spreadsheet and discovered that the internal Excel datatype assigned to the publish column was not what the loader expected, causing it to assign a default publish value regardless of the supplied value. But in the accessions case, Excel is not involved.

Thanks in advance for any advice you can offer. Regards. -julie

Julie Wetherill
HUIT Library Technology Services
Harvard University
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221207/7ad38304/attachment.html>

From leah.tams at duke.edu  Wed Dec  7 12:48:40 2022
From: leah.tams at duke.edu (Leah Tams)
Date: Wed, 7 Dec 2022 17:48:40 +0000
Subject: [Archivesspace_Users_Group] Publish status set incorrectly
	in	Accession csv import
In-Reply-To: <SJ0PR07MB864550AD263F781A377F7DBE8A1A9@SJ0PR07MB8645.namprd07.prod.outlook.com>
References: <SJ0PR07MB864550AD263F781A377F7DBE8A1A9@SJ0PR07MB8645.namprd07.prod.outlook.com>
Message-ID: <647F2BD8-600D-4FE3-A796-D36D99965648@duke.edu>

Hi Julie,

Are User 0?s settings correct? There is a setting for users that will automatically publish any record they create or upload. If that?s turned on, I?d suggest turning it off and then seeing if the problem persists.

Best,
Leah

On Dec 7, 2022, at 12:22 PM, Wetherill, Julie M. <julie_wetherill at harvard.edu> wrote:

?
Hi all,

We have a problem importing accession records by csv that seems to be limited to a single user's computer.

Accession imports by this staff user are loaded successfully, but the records always land in the system as published despite the accession_publish column being set to '0' (unpublished) across the board. Our public interface doesn't display accessions but PUI solr happily indexes them, so PUI users find these accession records but can't open them. So we don't want published accessions.

We are running v3.0.2 and the user (who I'm calling User 0) is working off a fresh accession csv template pulled from github.

Using the same csv, I am able to import accession records that load as unpublished. And other users in the same repository as User 0 can load that csv and get unpublished records. But not User 0.

All csv editing is done in a text editor and not Excel. I don't think this is an issue with user preferences or permissions (which are the same for everyone who has tested).

Using a hex viewer, I don't see anything funky going on with the value for accession_publish in the csv (it is the number zero).

Any ideas what is causing this weirdness? Many moons ago we had a similar issue importing EADs from spreadsheet and discovered that the internal Excel datatype assigned to the publish column was not what the loader expected, causing it to assign a default publish value regardless of the supplied value. But in the accessions case, Excel is not involved.

Thanks in advance for any advice you can offer. Regards. -julie

Julie Wetherill
HUIT Library Technology Services
Harvard University
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org
https://urldefense.com/v3/__http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group__;!!OToaGQ!si2xKFmOjAf4dqXN8lfhdNlh6jdmPttwzDk_WpUuUeLeU98PMOBBf25tbv2FeWfv9ZEGKBd9gpeYrH-QXDGyaeHA9uQYmUQ$
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221207/3e216875/attachment.html>

From julie_wetherill at harvard.edu  Wed Dec  7 13:05:15 2022
From: julie_wetherill at harvard.edu (Wetherill, Julie M.)
Date: Wed, 7 Dec 2022 18:05:15 +0000
Subject: [Archivesspace_Users_Group] Publish status set incorrectly in
 Accession csv import
In-Reply-To: <647F2BD8-600D-4FE3-A796-D36D99965648@duke.edu>
References: <SJ0PR07MB864550AD263F781A377F7DBE8A1A9@SJ0PR07MB8645.namprd07.prod.outlook.com>
 <647F2BD8-600D-4FE3-A796-D36D99965648@duke.edu>
Message-ID: <SJ0PR07MB864592502A9C8A1878E9AB608A1A9@SJ0PR07MB8645.namprd07.prod.outlook.com>

Hi Leah,

User 0 reports that the user preference setting for ?Publish? is unchecked. Under ?Repository Preferences?, it?s also unchecked.  --julie

From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Leah Tams
Sent: Wednesday, December 7, 2022 12:49 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Publish status set incorrectly in Accession csv import

Hi Julie,

Are User 0?s settings correct? There is a setting for users that will automatically publish any record they create or upload. If that?s turned on, I?d suggest turning it off and then seeing if the problem persists.

Best,
Leah


On Dec 7, 2022, at 12:22 PM, Wetherill, Julie M. <julie_wetherill at harvard.edu<mailto:julie_wetherill at harvard.edu>> wrote:
?
Hi all,

We have a problem importing accession records by csv that seems to be limited to a single user's computer.

Accession imports by this staff user are loaded successfully, but the records always land in the system as published despite the accession_publish column being set to '0' (unpublished) across the board. Our public interface doesn't display accessions but PUI solr happily indexes them, so PUI users find these accession records but can't open them. So we don't want published accessions.

We are running v3.0.2 and the user (who I'm calling User 0) is working off a fresh accession csv template pulled from github.

Using the same csv, I am able to import accession records that load as unpublished. And other users in the same repository as User 0 can load that csv and get unpublished records. But not User 0.

All csv editing is done in a text editor and not Excel. I don't think this is an issue with user preferences or permissions (which are the same for everyone who has tested).

Using a hex viewer, I don't see anything funky going on with the value for accession_publish in the csv (it is the number zero).

Any ideas what is causing this weirdness? Many moons ago we had a similar issue importing EADs from spreadsheet and discovered that the internal Excel datatype assigned to the publish column was not what the loader expected, causing it to assign a default publish value regardless of the supplied value. But in the accessions case, Excel is not involved.

Thanks in advance for any advice you can offer. Regards. -julie

Julie Wetherill
HUIT Library Technology Services
Harvard University
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
https://urldefense.com/v3/__http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group__;!!OToaGQ!si2xKFmOjAf4dqXN8lfhdNlh6jdmPttwzDk_WpUuUeLeU98PMOBBf25tbv2FeWfv9ZEGKBd9gpeYrH-QXDGyaeHA9uQYmUQ$<https://urldefense.com/v3/__http:/lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group__;!!OToaGQ!si2xKFmOjAf4dqXN8lfhdNlh6jdmPttwzDk_WpUuUeLeU98PMOBBf25tbv2FeWfv9ZEGKBd9gpeYrH-QXDGyaeHA9uQYmUQ$>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221207/c9d9acdc/attachment.html>

From Jessica.Crouch at lyrasis.org  Wed Dec  7 14:14:15 2022
From: Jessica.Crouch at lyrasis.org (Jessica Crouch)
Date: Wed, 7 Dec 2022 19:14:15 +0000
Subject: [Archivesspace_Users_Group] Member Discussion and Survey - Future
 Development of the ArchivesSpace Digital Objects Module
In-Reply-To: <DM5PR22MB054063A543B4197F15716F358B3E9@DM5PR22MB0540.namprd22.prod.outlook.com>
References: <E2EAD981-9305-4512-B6EA-F73688764342@lyrasis.org>
 <MN2PR22MB19498F036210B24D708423858BE19@MN2PR22MB1949.namprd22.prod.outlook.com>
 <MN2PR22MB1949A65C83F87516CE51545E8BFD9@MN2PR22MB1949.namprd22.prod.outlook.com>
 <MN2PR22MB1949BE931B72D3249131900C8BDC9@MN2PR22MB1949.namprd22.prod.outlook.com>
 <MN2PR22MB1949E5B6EE730B5A4C1C66448BBA9@MN2PR22MB1949.namprd22.prod.outlook.com>
 <DM5PR22MB05407922B6CDC870AD3A665A8B999@DM5PR22MB0540.namprd22.prod.outlook.com>
 <DM5PR22MB05402F3626F4B5CC7A479C3E8B789@DM5PR22MB0540.namprd22.prod.outlook.com>
 <DM5PR22MB054029E347B7CF8AC6835A708B569@DM5PR22MB0540.namprd22.prod.outlook.com>
 <DM5PR22MB0540182519A854A7757357018B379@DM5PR22MB0540.namprd22.prod.outlook.com>
 <DM5PR22MB054063A543B4197F15716F358B3E9@DM5PR22MB0540.namprd22.prod.outlook.com>
Message-ID: <DM5PR22MB0540A91BEC9905D3DFAF49138B1A9@DM5PR22MB0540.namprd22.prod.outlook.com>

Dear ArchivesSpace members,



Join the ArchivesSpace program team and your fellow ArchivesSpace members on December 14, 2022, at 1pm ET/10am PT for a discussion of future development of the ArchivesSpace Digital Objects Module.


Date: December 14, 2022
Time: 1:00pm-2:30pm ET/10:00am-11:30am PT (find your local time<https://www.timeanddate.com/worldclock/fixedtime.html?msg=Member+Discussion+-+Member+Discussion+-+Future+Development+ArchivesSpace+Digital+Objects&iso=20221214T13&p1=179&ah=1&am=30>)
Registration:  https://lyrasis.zoom.us/meeting/register/tZEpce-trjkoGdSGvc2uCimrn5zVU0UM-027


In this discussion facilitated by members of the ArchivesSpace program team, members will be able to share their own use cases and goals for the digital objects module.  Members are encouraged to review current community-submitted feature requests for the digital objects module on the ArchivesSpace JIRA<https://archivesspace.atlassian.net/jira/dashboards/10000> prior to the discussion.  If you are unable to locate a current feature request that represents your use case, you are encouraged to submit a feature request<https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/19202060/How+to+Request+a+New+Feature> following these instructions.


Members are also encouraged to review the digital objects section<https://archivesspace.atlassian.net/wiki/spaces/ArchivesSpaceUserManual/pages/890142831/Managing+Digital+Objects> of the ArchivesSpace user manual<https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/917045261/ArchivesSpace+Help+Center> in anticipation of this discussion.


This discussion is open to ArchivesSpace members only and registration is required. Attendees must register using an email address affiliated with a member organization.  This is in recognition of the crucial role that ArchivesSpace members play in directly financially supporting the sustainability and development of the application. Having input in large development projects and discussions like this one is one of the member benefits<https://archivesspace.org/community/member-benefits> of ArchivesSpace.


In preparation for this discussion about the digital objects module, we are gathering some information about how people are currently using digital objects and ideas for the future. All members with an interest in digital objects are welcome to respond to this survey, even if they won't be attending the discussion.  To complete the survey visit https://www.surveymonkey.com/r/JRCV9F7.


This discussion will not be recorded but notes will be made available on the ArchivesSpace wiki in the days following the discussion.  If you are interested in ArchivesSpace membership and contributing to the future development of the application, email the ArchivesSpace program team at ArchivesSpaceHome at lyrasis.org<mailto:ArchivesSpaceHome at lyrasis.org>.



Jessica Dowd Crouch
Community Engagement Coordinator for ArchivesSpace
jessica.crouch at lyrasis.org<mailto:jessica.crouch at lyrasis.org>
[page1image482511520]

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

From naomi-franklin at utulsa.edu  Thu Dec  8 12:58:56 2022
From: naomi-franklin at utulsa.edu (Franklin, Naomi)
Date: Thu, 8 Dec 2022 17:58:56 +0000
Subject: [Archivesspace_Users_Group] Looking for ways to best handle
 object record culturally sensitive restrictions
In-Reply-To: <CAKu+i=0XEhN7kZLO-ddgLrWA3eAWAKbXrm=hO5fU=n_eN2EOBA@mail.gmail.com>
References: <SN4PR0201MB880622AF3133F413E1C27207F8009@SN4PR0201MB8806.namprd02.prod.outlook.com>
 <DM5PR05MB3308C1D1DA4B4D38F156D73E9A009@DM5PR05MB3308.namprd05.prod.outlook.com>
 <CAKu+i=0XEhN7kZLO-ddgLrWA3eAWAKbXrm=hO5fU=n_eN2EOBA@mail.gmail.com>
Message-ID: <SN4PR0201MB8806C615B691F4110DBDC517F81D9@SN4PR0201MB8806.namprd02.prod.outlook.com>

Sorry for a delayed response. I appreciate the feedback on restrictions that I?ve received. Thank you for your help Leah, Michael, and Olivia!

Best,
Naomi
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Olivia S Solis <livsolis at utexas.edu>
Date: Saturday, November 12, 2022 at 10:17 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Looking for ways to best handle object record culturally sensitive restrictions
Just wanted to add that in addition to the Conditions Governing Access allows you to apply local access restrictions that are internal flags for staff yjay further define the reason for the restriction. Any top container attached to an archival object or child, direct or indirect, of an archival object flagged with a local access restriction will get clearly noted as restricted. You can customize the restrictions for local access use. Yale has a pretty good video explanation, which while made in 7 years ago is still applicable:
https://www.youtube.com/watch?time_continue=1&v=0m1rAbfn3h8&feature=emb_logo<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Ftime_continue%3D1%26v%3D0m1rAbfn3h8%26feature%3Demb_logo&data=05%7C01%7Cnaomi-franklin%40utulsa.edu%7C12492eb27248401c310f08dac4c95e25%7Cd4ff013c62b74167924f5bd93e8202d3%7C0%7C0%7C638038666405858633%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2BpX0x5QoTBOEF7j3FBfWynGGu%2FFDH9az0W%2Bon24QCXo%3D&reserved=0>

On Fri, Nov 11, 2022 at 2:26 PM Leah Tams <leah.tams at duke.edu<mailto:leah.tams at duke.edu>> wrote:
Hi Naomi,

The ?Notes? module of an Archival Object in ASpace allows you to indicate restrictions on material (Conditions Governing Access and/or Conditions Governing Use). As long as there is an Archival Object, you can place a restriction at any description level (Collection, Series, File, Item, etc.). Of course, this only indicates the existence of a restriction and doesn?t enforce the restriction itself.

I hope this is helpful!

Best,
Leah

she/her/hers
MSLS in Archives & Records Management
Accessions Coordinator
Rubenstein Rare Book & Manuscript Library
Duke University
leah.tams at duke.edu<mailto:leah.tams at duke.edu> | leahtams.org<https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.leahtams.org%2F&data=05%7C01%7Cnaomi-franklin%40utulsa.edu%7C12492eb27248401c310f08dac4c95e25%7Cd4ff013c62b74167924f5bd93e8202d3%7C0%7C0%7C638038666405858633%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=7ImEcOpI0k1WAoWA4wyf%2Bw58fa6PcEl%2Bl9KzRghMwcA%3D&reserved=0>

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> On Behalf Of Franklin, Naomi
Sent: Friday, November 11, 2022 1:55 PM
To: archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Looking for ways to best handle object record culturally sensitive restrictions

Hello, hello.

I?m seeking advice for how to best handle archival object record restrictions in ASpace. During a recent consultation of an archive collection, a number of photographs were identified with being culturally sensitive thus needing to be not only restricted to public access, but also internal access. In our efforts to be NAGPRA compliant and to follow the wishes of the Tribe, I need to determine best method(s) of restricting these records based on the options available in ASpace. I cannot find any previous conversations around this topic, and am wondering if others have had to restrict records for similar reasons before or restrict in general. My institution migrated our archive data to ASpace from TMS (The Museum System) a little over a year ago, so we?re still becoming familiar with the ins and outs of ASpace. We have procedures established for handling NAGPRA/Culturally Sensitive materials in TMS, but not yet ASpace. I welcome any thoughts and suggestions. Thanks!

Best,
Naomi
Cataloguing Manager and Associate DBA
Gilcrease Museum
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group<https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group&data=05%7C01%7Cnaomi-franklin%40utulsa.edu%7C12492eb27248401c310f08dac4c95e25%7Cd4ff013c62b74167924f5bd93e8202d3%7C0%7C0%7C638038666405858633%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=T1lK7jDJJ%2FQow3xuCVEyTSrewgjYpbCwQ1np3sIGwxw%3D&reserved=0>
>> This message is from an external sender. Learn more about why this <<
>> matters at https://links.utexas.edu/rtyclf<https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Flinks.utexas.edu%2Frtyclf&data=05%7C01%7Cnaomi-franklin%40utulsa.edu%7C12492eb27248401c310f08dac4c95e25%7Cd4ff013c62b74167924f5bd93e8202d3%7C0%7C0%7C638038666405858633%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=KrMTp5S8XcnY%2FWAYt2%2F%2FjdG3P9sTkMusxjZ%2BLpCpkIQ%3D&reserved=0>.                        <<


--
Olivia Solis, MSIS (she/her)
Metadata Coordinator
Dolph Briscoe Center for American History
The University of Texas at Austin
2300 Red River St. Stop D1100
Austin TX, 78712-1426
(512) 232-8013
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221208/40801a31/attachment.html>

From Amanda.Brown at ccc.govt.nz  Thu Dec  8 19:27:50 2022
From: Amanda.Brown at ccc.govt.nz (Brown, Amanda)
Date: Fri, 9 Dec 2022 00:27:50 +0000
Subject: [Archivesspace_Users_Group] Pruning temporary files?
Message-ID: <SYZP282MB3132C970AF63D7CCCC5C104DC91C9@SYZP282MB3132.AUSP282.PROD.OUTLOOK.COM>

Kia ora koutou,


Our ArchivesSpace UAT has run out of space, and the information from our developer is :

      The space is mainly being taken up by temporary files created by the archivesspace app itself, eg:

      antbrown at ccc-dhr-uat-as1:/opt/archivesspace3/data$ sudo -u archivesspace du -hs tmp
      9.4G    tmp

      Some of these files are used for running the app and it's not obvious from https://archivesspace.github.io/tech-docs/readme_implement.html which are safe to delete.
      If you were able to post to the mailing list asking which files are safe to delete in the data/tmp directory, we could write a script to make sure it's cleaned daily for example.

Any suggestions which files are safe to delete in the data/tmp directory?

Ng? mihi
Amanda

Digital Content Librarian | Digital Content Team |
Christchurch City Libraries | Ng? Kete W?nanga-o-?tautahi |
https://canterburystories.nz/

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 the email.

[Christchurch City Council logo]<https://ccc.govt.nz>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221209/ea813e33/attachment.html>

From andrew.morrison at bodleian.ox.ac.uk  Mon Dec 12 03:52:40 2022
From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison)
Date: Mon, 12 Dec 2022 08:52:40 +0000
Subject: [Archivesspace_Users_Group] Pruning temporary files?
In-Reply-To: <SYZP282MB3132C970AF63D7CCCC5C104DC91C9@SYZP282MB3132.AUSP282.PROD.OUTLOOK.COM>
References: <SYZP282MB3132C970AF63D7CCCC5C104DC91C9@SYZP282MB3132.AUSP282.PROD.OUTLOOK.COM>
Message-ID: <01139e02-45bf-5737-5ae4-db60293a6990@bodleian.ox.ac.uk>

The tmp folder is used to store files which should be deleted 
automatically after the process that created them finishes, but that 
doesn't always happen. On the system I run, it has grown to 0.4G in four 
years, mostly files created during indexing. Some files are also written 
there during startup.

So you should be able to stop the ArchivesSpace service, delete 
everything inside the tmp folder, then restart, although I've never done 
so myself. But first it would be worth investigating when the bulk of 
the 9.4G was created. If it has built up over time, the majority before 
the last restart, it is less of a concern than if most of it is new.

Andrew.


On 09/12/2022 00:27, Brown, Amanda wrote:
> Kia ora koutou,
> Our ArchivesSpace UAT has run out of space, and the information from 
> our developer is :
> The space is mainly being taken up by temporary files created by the 
> archivesspace app itself, eg:
> antbrown at ccc-dhr-uat-as1:/opt/archivesspace3/data$ sudo -u 
> archivesspace du -hs tmp
> 9.4G??? tmp
> Some of these files are used for running the app and it's not obvious 
> from https://archivesspace.github.io/tech-docs/readme_implement.html 
> which are safe to delete.
> If you were able to post to the mailing list asking which files are 
> safe to delete in the data/tmp directory, we could write a script to 
> make sure it's cleaned daily for example.
> Any suggestions which files are safe to delete in the data/tmp directory?
> Ng? mihi
> Amanda
> Digital Content Librarian | Digital Content Team |
> Christchurch City Libraries | Ng? Kete W?nanga-o-?tautahi |
> _https://canterburystories.nz/_ <https://canterburystories.nz/>
> 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 the email.
>
> <https://ccc.govt.nz>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221212/bcd7c620/attachment.html>

From hanstra at nd.edu  Mon Dec 12 12:46:29 2022
From: hanstra at nd.edu (Tom Hanstra)
Date: Mon, 12 Dec 2022 12:46:29 -0500
Subject: [Archivesspace_Users_Group] Pruning temporary files?
In-Reply-To: <01139e02-45bf-5737-5ae4-db60293a6990@bodleian.ox.ac.uk>
References: <SYZP282MB3132C970AF63D7CCCC5C104DC91C9@SYZP282MB3132.AUSP282.PROD.OUTLOOK.COM>
 <01139e02-45bf-5737-5ae4-db60293a6990@bodleian.ox.ac.uk>
Message-ID: <CAA60kZManf7-ckXr-avCBQNGkBvoKCiOtcENYTpSEGiiO2AWGw@mail.gmail.com>

Thanks, Andrew.

I was waiting for someone with a bit more experience with ArchivesSpace to
chime in on this. In my case, we have a number of old jruby directories
which contain a set of jar files. What should be cleaning these up?
Whatever it might be, it is missing doing that cleanup on my site.  I'm
curious how things are supposed to work.

As for cleanup, if the service is somehow not cleaning these up properly,
then my usual methodology is to have a cleanup script (or manual
intervention) come behind and delete everything which is a certain number
of days old. I would guess anything older than 30 days in that directory is
fair game for deletion. Do you see anything wrong with that?

Thanks,
Tom

On Mon, Dec 12, 2022 at 3:52 AM Andrew Morrison <
andrew.morrison at bodleian.ox.ac.uk> wrote:

> The tmp folder is used to store files which should be deleted
> automatically after the process that created them finishes, but that
> doesn't always happen. On the system I run, it has grown to 0.4G in four
> years, mostly files created during indexing. Some files are also written
> there during startup.
>
> So you should be able to stop the ArchivesSpace service, delete everything
> inside the tmp folder, then restart, although I've never done so myself.
> But first it would be worth investigating when the bulk of the 9.4G was
> created. If it has built up over time, the majority before the last
> restart, it is less of a concern than if most of it is new.
>
> Andrew.
>
>
> On 09/12/2022 00:27, Brown, Amanda wrote:
>
> Kia ora koutou,
>
>
> Our ArchivesSpace UAT has run out of space, and the information from our
> developer is :
>
> The space is mainly being taken up by temporary files created by the
> archivesspace app itself, eg:
>
> antbrown at ccc-dhr-uat-as1:/opt/archivesspace3/data$ sudo -u archivesspace
> du -hs tmp
> 9.4G    tmp
>
> Some of these files are used for running the app and it's not obvious from
> https://archivesspace.github.io/tech-docs/readme_implement.html which are
> safe to delete.
> If you were able to post to the mailing list asking which files are safe
> to delete in the data/tmp directory, we could write a script to make sure
> it's cleaned daily for example.
>
> Any suggestions which files are safe to delete in the data/tmp directory?
>
> Ng? mihi
> Amanda
>
> Digital Content Librarian | Digital Content Team |
> Christchurch City Libraries | Ng? Kete W?nanga-o-?tautahi |
> *https://canterburystories.nz/* <https://canterburystories.nz/>
>
> 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 the email.
>
> <https://ccc.govt.nz>
>
> _______________________________________________
> Archivesspace_Users_Group mailing listArchivesspace_Users_Group at lyralists.lyrasis.orghttp://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>


-- 
*Tom Hanstra*
*Sr. Systems Administrator*
hanstra at nd.edu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221212/34d9d8bd/attachment.html>

From amanifold at slv.vic.gov.au  Mon Dec 12 22:50:11 2022
From: amanifold at slv.vic.gov.au (Alan Manifold)
Date: Tue, 13 Dec 2022 03:50:11 +0000
Subject: [Archivesspace_Users_Group] Find by ID API call
Message-ID: <ME3PR01MB6088246898489A25459EECDCC0E39@ME3PR01MB6088.ausprd01.prod.outlook.com>

Hi ArchivesSpace folks,
I've been trying to get the find_by_id API call to work and haven't had any luck. What I really want is to be able to find archival objects by ARK, but I tried the other types of IDs to see if they would work and tell me something useful. But I can't get any of them to work. We're on version 3.2.0. I have a program that establishes a connection and gets a session ID, then sends off the API call. When the same program sends this search API, it works:

http://ourhost.com:8089/search?q=component_id:"YLTAD111/51/37" OR component_id:"YLTAD111/51/38" OR component_id:"YLTAD111/51/39"&page=1

Here's what I have tried:

http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ark=https://ourhost.com/ark:/9999/119460
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ark=ark:/9999/119460
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ark=119460
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ark[]=ark:/9999/119460
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ark[]=119460
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id[]=YLTAD111/51/37
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id[]=YLTAD111%2F51%2F37
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id[]='YLTAD111%2F51%2F37'
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id[]='YLTAD111'
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id[]=YLTAD111
http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id[]=YLTAD111
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id[]=YLTAD111;resolve[]=archival_objects
http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id[]=MS%2015856;resolve[]=archival_objects
http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id[]=MS 15856;resolve[]=archival_objects
http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id[]=MS_15856;resolve[]=archival_objects
http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id[]=MS10840-1.1.1;resolve[]=archival_objects
http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id[]=MS10840-1.1.1;resolve[]=archival_objects
http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id[]=MS10840-1.1.1
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ref_id[]=15a419a9464353be174f77bdc8f38874
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ref_id=15a419a9464353be174f77bdc8f38874

Every single call returned a 404 error. Can anyone tell me what I'm doing wrong? I'll feel stupid if it's obvious, but I'll still be thankful. Thanks so much!

Regards,
Alan



Alan Manifold | Library Systems & Digital Preservation Manager | Collection Development & Description
State Library Victoria | 328 Swanston Street | Melbourne VIC 3000
T +61 3 8664 7122 | amanifold at 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>



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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221213/2a766bf9/attachment.html>

From andrew.morrison at bodleian.ox.ac.uk  Tue Dec 13 13:35:57 2022
From: andrew.morrison at bodleian.ox.ac.uk (Andrew Morrison)
Date: Tue, 13 Dec 2022 18:35:57 +0000
Subject: [Archivesspace_Users_Group] Pruning temporary files?
In-Reply-To: <CAA60kZManf7-ckXr-avCBQNGkBvoKCiOtcENYTpSEGiiO2AWGw@mail.gmail.com>
References: <SYZP282MB3132C970AF63D7CCCC5C104DC91C9@SYZP282MB3132.AUSP282.PROD.OUTLOOK.COM>
 <01139e02-45bf-5737-5ae4-db60293a6990@bodleian.ox.ac.uk>
 <CAA60kZManf7-ckXr-avCBQNGkBvoKCiOtcENYTpSEGiiO2AWGw@mail.gmail.com>
Message-ID: <8092237f-4863-4888-30a4-909db273b63c@bodleian.ox.ac.uk>

Sorry, my previous email contained everything I know on the topic of 
temp files.

Andrew.


On 12/12/2022 17:46, Tom Hanstra wrote:
> Thanks, Andrew.
>
> I was waiting for someone with a bit more experience with 
> ArchivesSpace to chime in on this. In my case, we have a number of old 
> jruby directories which contain a set of jar files. What should be 
> cleaning these up? Whatever it might be, it is missing doing that 
> cleanup on my site.? I'm curious how things are supposed to work.
>
> As for cleanup, if the service is somehow not cleaning these up 
> properly, then my usual methodology is to have a cleanup script (or 
> manual intervention) come behind and delete everything which is a 
> certain number of days old. I would guess anything older than 30 days 
> in that directory is fair game for deletion. Do you see anything wrong 
> with that?
>
> Thanks,
> Tom
>
> On Mon, Dec 12, 2022 at 3:52 AM Andrew Morrison 
> <andrew.morrison at bodleian.ox.ac.uk> wrote:
>
>     The tmp folder is used to store files which should be deleted
>     automatically after the process that created them finishes, but
>     that doesn't always happen. On the system I run, it has grown to
>     0.4G in four years, mostly files created during indexing. Some
>     files are also written there during startup.
>
>     So you should be able to stop the ArchivesSpace service, delete
>     everything inside the tmp folder, then restart, although I've
>     never done so myself. But first it would be worth investigating
>     when the bulk of the 9.4G was created. If it has built up over
>     time, the majority before the last restart, it is less of a
>     concern than if most of it is new.
>
>     Andrew.
>
>
>     On 09/12/2022 00:27, Brown, Amanda wrote:
>>     Kia ora koutou,
>>     Our ArchivesSpace UAT has run out of space, and the information
>>     from our developer is :
>>     The space is mainly being taken up by temporary files created by
>>     the archivesspace app itself, eg:
>>     antbrown at ccc-dhr-uat-as1:/opt/archivesspace3/data$ sudo -u
>>     archivesspace du -hs tmp
>>     9.4G??? tmp
>>     Some of these files are used for running the app and it's not
>>     obvious from
>>     https://archivesspace.github.io/tech-docs/readme_implement.html
>>     which are safe to delete.
>>     If you were able to post to the mailing list asking which files
>>     are safe to delete in the data/tmp directory, we could write a
>>     script to make sure it's cleaned daily for example.
>>     Any suggestions which files are safe to delete in the data/tmp
>>     directory?
>>     Ng? mihi
>>     Amanda
>>     Digital Content Librarian | Digital Content Team |
>>     Christchurch City Libraries | Ng? Kete W?nanga-o-?tautahi |
>>     _https://canterburystories.nz/_ <https://canterburystories.nz/>
>>     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 the email.
>>
>>     <https://ccc.govt.nz>
>>
>>     _______________________________________________
>>     Archivesspace_Users_Group mailing list
>>     Archivesspace_Users_Group at lyralists.lyrasis.org
>>     http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>     _______________________________________________
>     Archivesspace_Users_Group mailing list
>     Archivesspace_Users_Group at lyralists.lyrasis.org
>     http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>
>
> -- 
> *Tom Hanstra*
> /Sr. Systems Administrator/
> hanstra at nd.edu
>
>
>
> _______________________________________________
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group at lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221213/250d56b3/attachment.html>

From Corey.Schmidt at uga.edu  Tue Dec 13 16:26:55 2022
From: Corey.Schmidt at uga.edu (Corey Schmidt)
Date: Tue, 13 Dec 2022 21:26:55 +0000
Subject: [Archivesspace_Users_Group] Find by ID API call
In-Reply-To: <ME3PR01MB6088246898489A25459EECDCC0E39@ME3PR01MB6088.ausprd01.prod.outlook.com>
References: <ME3PR01MB6088246898489A25459EECDCC0E39@ME3PR01MB6088.ausprd01.prod.outlook.com>
Message-ID: <SJ0PR02MB77748FBC0CE0A20623DF4CA7F3E39@SJ0PR02MB7774.namprd02.prod.outlook.com>

Hey Alan,

Big caveat first: we don't use ARKs where I work, so I'm flying a little blind here. I enabled ARKs on our testing space just to see if I could replicate your request. Here's what I tried and it returned the correct archival object:

curl -H "X-ArchivesSpace-Session: $SESSION" "https://our_api_url/repositories/2/find_by_id/archival_objects?ark[]=www.testarkurl.com/ark:/YLTAD111/51/37;resolve[]=archival_objects"

I added an external ARK URL to the archival object and put www.testarkurl.com/ark:/YLTAD111/51/37 in that field. Are you using something like this or trying to access internal ARKs? If it's internal, I don't have a way to test that, I'm afraid. Though it seems like the following requests are constructed properly:

http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id[]=YLTAD111/51/37
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ref_id[]=15a419a9464353be174f77bdc8f38874   (our ref_ids look something like this usually: "ref36_286", that looks like the container_id found in an EAD export)

If you're still getting a 404 error, I might also try using the "--url-encode" parameter to see if that helps. Dave Mayo at Harvard pointed me in this direction which works great for the find_by_id endpoint for resources. Using that would look something like:

curl -H "X-ArchivesSpace-Session: $SESSION" -G http://ourhost.com:8089/repositories/5/find_by_id/archival_objects --data-urlencode 'component_id[]=YLTAD111/51/37'

If you do find a solution, would you mind sharing it with the listserv or me? I wrote the API cURL and Python examples for that endpoint and I couldn't find anyone using ARKs to build an example from. Adding that would be the last piece of the puzzle for that documentation.

Hope this helps,

Corey
Corey Schmidt
Special Collections Libraries | Project Management Librarian/Archivist
Corey.Schmidt at uga.edu<mailto:Corey.Schmidt at uga.edu>
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Alan Manifold
Sent: Monday, December 12, 2022 10:50 PM
To: ArchivesSpace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Find by ID API call

[EXTERNAL SENDER - PROCEED CAUTIOUSLY]
Hi ArchivesSpace folks,
I've been trying to get the find_by_id API call to work and haven't had any luck. What I really want is to be able to find archival objects by ARK, but I tried the other types of IDs to see if they would work and tell me something useful. But I can't get any of them to work. We're on version 3.2.0. I have a program that establishes a connection and gets a session ID, then sends off the API call. When the same program sends this search API, it works:

http://ourhost.com:8089/search?q=component_id:"YLTAD111/51/37<http://ourhost.com:8089/search?q=component_id:%22YLTAD111/51/37>" OR component_id:"YLTAD111/51/38" OR component_id:"YLTAD111/51/39"&page=1

Here's what I have tried:

http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ark=https://ourhost.com/ark:/9999/119460
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ark=ark:/9999/119460
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ark=119460
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ark[]=ark:/9999/119460<http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ark%5b%5d=ark:/9999/119460>
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ark[]=119460<http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ark%5b%5d=119460>
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id[]=YLTAD111/51/37<http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id%5b%5d=YLTAD111/51/37>
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id[]=YLTAD111%2F51%2F37<http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id%5b%5d=YLTAD111%2F51%2F37>
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id[]='YLTAD111%2F51%2F37<http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id%5b%5d='YLTAD111%2F51%2F37>'
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id[]='YLTAD111<http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id%5b%5d='YLTAD111>'
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id[]=YLTAD111<http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id%5b%5d=YLTAD111>
http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id[]=YLTAD111<http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id%5b%5d=YLTAD111>
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id[]=YLTAD111;resolve[]=archival_objects<http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id%5b%5d=YLTAD111;resolve%5b%5d=archival_objects>
http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id[]=MS%2015856;resolve[]=archival_objects<http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id%5b%5d=MS%2015856;resolve%5b%5d=archival_objects>
http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id[]=MS<http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id%5b%5d=MS> 15856;resolve[]=archival_objects
http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id[]=MS_15856;resolve[]=archival_objects<http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id%5b%5d=MS_15856;resolve%5b%5d=archival_objects>
http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id[]=MS10840-1.1.1;resolve[]=archival_objects<http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id%5b%5d=MS10840-1.1.1;resolve%5b%5d=archival_objects>
http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id[]=MS10840-1.1.1;resolve[]=archival_objects<http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id%5b%5d=MS10840-1.1.1;resolve%5b%5d=archival_objects>
http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id[]=MS10840-1.1.1<http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id%5b%5d=MS10840-1.1.1>
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ref_id[]=15a419a9464353be174f77bdc8f38874<http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ref_id%5b%5d=15a419a9464353be174f77bdc8f38874>
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ref_id=15a419a9464353be174f77bdc8f38874

Every single call returned a 404 error. Can anyone tell me what I'm doing wrong? I'll feel stupid if it's obvious, but I'll still be thankful. Thanks so much!

Regards,
Alan



Alan Manifold | Library Systems & Digital Preservation Manager | Collection Development & Description
State Library Victoria | 328 Swanston Street | Melbourne VIC 3000
T +61 3 8664 7122 | amanifold at slv.vic.gov.au<mailto:amanifold at 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>



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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221213/1f62647b/attachment.html>

From amanifold at slv.vic.gov.au  Tue Dec 13 17:14:51 2022
From: amanifold at slv.vic.gov.au (Alan Manifold)
Date: Tue, 13 Dec 2022 22:14:51 +0000
Subject: [Archivesspace_Users_Group] Find by ID API call
In-Reply-To: <SJ0PR02MB77748FBC0CE0A20623DF4CA7F3E39@SJ0PR02MB7774.namprd02.prod.outlook.com>
References: <ME3PR01MB6088246898489A25459EECDCC0E39@ME3PR01MB6088.ausprd01.prod.outlook.com>
 <SJ0PR02MB77748FBC0CE0A20623DF4CA7F3E39@SJ0PR02MB7774.namprd02.prod.outlook.com>
Message-ID: <ME3PR01MB608849F6AF9F5CFE9090F1A9C0E39@ME3PR01MB6088.ausprd01.prod.outlook.com>

Thanks, Corey,
This one finally worked for me, based on using the --data-urlencode option and seeing what it did, along with the URL that worked for you (which included the host but not the http:// part).

                http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ark[]=ark%3A%2F9999%2F119460<http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ark%5b%5d=ark%3A%2F9999%2F119460>

Embarrassingly, I was using POST instead of GET, which didn't help my testing of the other aspects of the find_by_id API.

I have to say that the answer here was not at all obvious. There was no indication in the doco that you would have to encode the ARK, although all ARKs will have a colon and slashes. Most of our component_id's also have slashes and that wasn't indicated for them, either. Perhaps it's obvious to everyone else, but I have no idea why we include the "[]" after "ark". I guess you can use multiple values or something, but there's no indication of how that is done. It's great to have the full doco for all the APIs, but most of it is pretty cryptic. A few examples of actually use of them would really go a long way. I guess the fact that not so many sites are using ARKs is part of the problem here.

In any case, thank you very much for your help. I'm on my way now and that's down to you.

Regards,
Alan





Alan Manifold | Library Systems & Digital Preservation Manager | Collection Development & Description
State Library Victoria | 328 Swanston Street | Melbourne VIC 3000
T +61 3 8664 7122 | amanifold at 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-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Corey Schmidt
Sent: Wednesday, 14 December 2022 8:27 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Find by ID API call

Hey Alan,

Big caveat first: we don't use ARKs where I work, so I'm flying a little blind here. I enabled ARKs on our testing space just to see if I could replicate your request. Here's what I tried and it returned the correct archival object:

curl -H "X-ArchivesSpace-Session: $SESSION" "https://our_api_url/repositories/2/find_by_id/archival_objects?ark[]=www.testarkurl.com/ark:/YLTAD111/51/37;resolve[]=archival_objects<https://our_api_url/repositories/2/find_by_id/archival_objects?ark%5b%5d=www.testarkurl.com/ark:/YLTAD111/51/37;resolve%5b%5d=archival_objects>"

I added an external ARK URL to the archival object and put www.testarkurl.com/ark:/YLTAD111/51/37<http://www.testarkurl.com/ark:/YLTAD111/51/37> in that field. Are you using something like this or trying to access internal ARKs? If it's internal, I don't have a way to test that, I'm afraid. Though it seems like the following requests are constructed properly:

http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id[]=YLTAD111/51/37<http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id%5b%5d=YLTAD111/51/37>
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ref_id[]=15a419a9464353be174f77bdc8f38874<http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ref_id%5b%5d=15a419a9464353be174f77bdc8f38874>   (our ref_ids look something like this usually: "ref36_286", that looks like the container_id found in an EAD export)

If you're still getting a 404 error, I might also try using the "--url-encode" parameter to see if that helps. Dave Mayo at Harvard pointed me in this direction which works great for the find_by_id endpoint for resources. Using that would look something like:

curl -H "X-ArchivesSpace-Session: $SESSION" -G http://ourhost.com:8089/repositories/5/find_by_id/archival_objects --data-urlencode 'component_id[]=YLTAD111/51/37'

If you do find a solution, would you mind sharing it with the listserv or me? I wrote the API cURL and Python examples for that endpoint and I couldn't find anyone using ARKs to build an example from. Adding that would be the last piece of the puzzle for that documentation.

Hope this helps,

Corey
Corey Schmidt
Special Collections Libraries | Project Management Librarian/Archivist
Corey.Schmidt at uga.edu<mailto:Corey.Schmidt at uga.edu>
From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> On Behalf Of Alan Manifold
Sent: Monday, December 12, 2022 10:50 PM
To: ArchivesSpace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] Find by ID API call

[EXTERNAL SENDER - PROCEED CAUTIOUSLY]
Hi ArchivesSpace folks,
I've been trying to get the find_by_id API call to work and haven't had any luck. What I really want is to be able to find archival objects by ARK, but I tried the other types of IDs to see if they would work and tell me something useful. But I can't get any of them to work. We're on version 3.2.0. I have a program that establishes a connection and gets a session ID, then sends off the API call. When the same program sends this search API, it works:

http://ourhost.com:8089/search?q=component_id:"YLTAD111/51/37<http://ourhost.com:8089/search?q=component_id:%22YLTAD111/51/37>" OR component_id:"YLTAD111/51/38" OR component_id:"YLTAD111/51/39"&page=1

Here's what I have tried:

http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ark=https://ourhost.com/ark:/9999/119460
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ark=ark:/9999/119460
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ark=119460
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ark[]=ark:/9999/119460<http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ark%5b%5d=ark:/9999/119460>
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ark[]=119460<http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ark%5b%5d=119460>
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id[]=YLTAD111/51/37<http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id%5b%5d=YLTAD111/51/37>
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id[]=YLTAD111%2F51%2F37<http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id%5b%5d=YLTAD111%2F51%2F37>
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id[]='YLTAD111%2F51%2F37<http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id%5b%5d='YLTAD111%2F51%2F37>'
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id[]='YLTAD111<http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id%5b%5d='YLTAD111>'
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id[]=YLTAD111<http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id%5b%5d=YLTAD111>
http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id[]=YLTAD111<http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id%5b%5d=YLTAD111>
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id[]=YLTAD111;resolve[]=archival_objects<http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id%5b%5d=YLTAD111;resolve%5b%5d=archival_objects>
http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id[]=MS%2015856;resolve[]=archival_objects<http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id%5b%5d=MS%2015856;resolve%5b%5d=archival_objects>
http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id[]=MS<http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id%5b%5d=MS> 15856;resolve[]=archival_objects
http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id[]=MS_15856;resolve[]=archival_objects<http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id%5b%5d=MS_15856;resolve%5b%5d=archival_objects>
http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id[]=MS10840-1.1.1;resolve[]=archival_objects<http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id%5b%5d=MS10840-1.1.1;resolve%5b%5d=archival_objects>
http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id[]=MS10840-1.1.1;resolve[]=archival_objects<http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id%5b%5d=MS10840-1.1.1;resolve%5b%5d=archival_objects>
http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id[]=MS10840-1.1.1<http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id%5b%5d=MS10840-1.1.1>
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ref_id[]=15a419a9464353be174f77bdc8f38874<http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ref_id%5b%5d=15a419a9464353be174f77bdc8f38874>
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ref_id=15a419a9464353be174f77bdc8f38874

Every single call returned a 404 error. Can anyone tell me what I'm doing wrong? I'll feel stupid if it's obvious, but I'll still be thankful. Thanks so much!

Regards,
Alan



Alan Manifold | Library Systems & Digital Preservation Manager | Collection Development & Description
State Library Victoria | 328 Swanston Street | Melbourne VIC 3000
T +61 3 8664 7122 | amanifold at slv.vic.gov.au<mailto:amanifold at 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>



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.
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221213/d3465c2d/attachment.html>

From brijmcla at iu.edu  Tue Dec 13 17:26:26 2022
From: brijmcla at iu.edu (McLaughlin, Brianna Jean)
Date: Tue, 13 Dec 2022 22:26:26 +0000
Subject: [Archivesspace_Users_Group] BCE-CE inclusive dates in ArchivesSpace
Message-ID: <PH0PR08MB7244735B8BF5E6A8F79892DDACE39@PH0PR08MB7244.namprd08.prod.outlook.com>

Hi everyone,

How do you all create a range of BCE-CE dates in ArchivesSpace at the finding aid and/or item level? Our ArcLight integration isn't cooperating with the "0001" begin date that a collection manager entered.

Thanks in advance!

Bri McLaughlin, she/her/hers
Visiting Metadata Services Librarian
Indiana University
812-856-3321

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

From philip.webster at sheffield.ac.uk  Wed Dec 14 06:44:52 2022
From: philip.webster at sheffield.ac.uk (Philip Webster)
Date: Wed, 14 Dec 2022 11:44:52 -0000
Subject: [Archivesspace_Users_Group] New user creation issue "Must be
	one of: ISAAR (CPF) and NCA Rules"
In-Reply-To: <bd6a76c0-7b58-ef5f-db0f-70f9b586bb0e@bodleian.ox.ac.uk>
References: <00a601d8fe64$c6ae3540$540a9fc0$@sheffield.ac.uk>
 <bd6a76c0-7b58-ef5f-db0f-70f9b586bb0e@bodleian.ox.ac.uk>
Message-ID: <123401d90fb1$7b4110b0$71c33210$@sheffield.ac.uk>

Thanks ? this was the solution.

 

Ideally, it would be nice if the drop-down entry could be hidden in some way without breaking the back-end  functionality.

 

Regards,

 

Phil

 

 

From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Andrew Morrison
Sent: 22 November 2022 12:15
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: Re: [Archivesspace_Users_Group] New user creation issue "Must be one of: ISAAR (CPF) and NCA Rules"

 

In the staff interface, go to System > Manage Controlled Value Lists. Then select "Name Rule (name_rule)" from the List Name drop-down. If that list doesn't have a value of "local", or that value has been suppressed, that could be the cause of your problem.

The issue is that creating system users also creates an (unpublished) agent record. So, if you've suppressed local rules for the naming of persons in your metadata, it'll won't be able to create the agent, so it won't be able to create the user either.

Andrew.

 

On 22/11/2022 11:22, Philip Webster wrote:

Hi,

 

I?m the admin for ArchivesSpace at the University of Sheffield, in the UK. We?ve had ArchivesSpace since version 2.7, and we currently run 2.8.1 with plans to move to 3.2.0 within the next month.

 

During our initial setup and launch, a number of user accounts were created for our permanent archival, metadata and technical staff. Since then we have had two new members of staff who qualified for ArchivesSpace accounts on our local system.

 

Unfortunately, it hasn?t been possible to create these accounts due to an issue in the staff user interface. I have populated the fields on the user form, and this is always done using the ?admin? account. When the form is submitted, the response is as follows:

 

Invalid value 'local'. Must be one of 'ISAAR (CPF) and NCA Rules'

User not created

 

Looking at the logs, I see that the frontend is sending the following data to the server (response lines are also shown, sensitive information redacted):

I, [2022-11-17T17:45:11.671710 #98122]  INFO -- : Started POST "/users" for REDACTED-IP at 2022-11-17 17:45:11 +0000

I, [2022-11-17T17:45:11.822783 #98122]  INFO -- : Processing by UsersController#create as HTML

I, [2022-11-17T17:45:11.823274 #98122]  INFO -- :   Parameters: {"utf8"=>"?", "authenticity_token"=>"REDACTED", "user"=>{"lock_version"=>"", "username"=>"testuser_t", "name"=>"testuser", "email"=>dummy at sheffield.ac.uk <mailto:dummy at sheffield.ac.uk> , "first_name"=>"test", "last_name"=>"user", "telephone"=>"", "title"=>"", "department"=>"Library", "additional_contact"=>"", "password"=>"[FILTERED]", "confirm_password"=>"[FILTERED]", "is_active_user"=>"1"}}

D, [2022-11-17T17:45:12.171371 #98122] DEBUG -- : Thread-3254: POST /users?repo_id=2&password=[FILTERED] [session: #<Session:REDACTED @store={:user=>"admin", :login_time=>2022-11-17 17:15:54 +0000, :expirable=>true}, @system_mtime=2022-11-17 17:44:46 UTC, @id="REDACTED">]

D, [2022-11-17T17:45:12.185350 #98122] DEBUG -- : Thread-3254: Post-processed params: {"password"=>"[FILTERED]", "user"=>#<JSONModel(:user) {"username"=>"testuser_t", "name"=>"testuser", "email"=>dummy at sheffield.ac.uk <mailto:dummy at sheffield.ac.uk> , "first_name"=>"test", "last_name"=>"user", "department"=>"Library", "is_active_user"=>true, "is_admin"=>false, "jsonmodel_type"=>"user", "groups"=>[]}>}

D, [2022-11-17T17:45:12.252354 #98122] DEBUG -- : Thread-3254: Responded with [400, {"Content-Type"=>"application/json", "Cache-Control"=>"private, must-revalidate, max-age=0", "Content-Length"=>"424"}, ["{\"error\":{\"rules\":[\"Invalid value 'local'.  Must be one of: ISAAR (CPF) and NCA Rules\"]},\"warning\":{},\"invalid_object\":\"#<JSONModel(:name_person) {\\\"primary_name\\\"=>\\\ <file:///%22testuser/> "testuser\\\", \\\ <file:///%22source/%22=%3e/%22local/> "source\\\"=>\\\"local\\\", \\\ <file:///%22rules/%22=%3e/%22local/> "rules\\\"=>\\\"local\\\", \\\ <file:///%22name_order/%22=%3e/%22direct/> "name_order\\\"=>\\\"direct\\\", \\\ <file:///%22sort_name_auto_generate/%22=%3etrue> "sort_name_auto_generate\\\"=>true, \\\ <file:///%22use_dates/%22=> "use_dates\\\"=>[], \\\ <file:///%22authorized/%22=%3etrue> "authorized\\\"=>true... in 83ms

I, [2022-11-17T17:45:12.307673 #98122]  INFO -- :   Rendering users/new.html.erb within layouts/application

I, [2022-11-17T17:45:12.383514 #98122]  INFO -- :   Rendered shared/_breadcrumb.html.erb (38.6ms)

I, [2022-11-17T17:45:12.385550 #98122]  INFO -- :   Rendered users/_toolbar.html.erb (0.3ms)

I, [2022-11-17T17:45:12.434052 #98122]  INFO -- :   Rendered shared/_flash_messages.html.erb (31.9ms)

I, [2022-11-17T17:45:12.434746 #98122]  INFO -- :   Rendered shared/_form_messages.html.erb (33.4ms)

I, [2022-11-17T17:45:12.639900 #98122]  INFO -- :   Rendered users/_form.html.erb (232.9ms)

I, [2022-11-17T17:45:12.645463 #98122]  INFO -- :   Rendered users/new.html.erb within layouts/application (329.1ms)

I, [2022-11-17T17:45:12.769050 #98122]  INFO -- :   Rendered shared/_header_user.html.erb (69.8ms)

I, [2022-11-17T17:45:12.777940 #98122]  INFO -- :   Rendered shared/_header_global.html.erb (87.0ms)

I, [2022-11-17T17:45:12.781522 #98122]  INFO -- :   Rendered site/_branding.html.erb (0.5ms)

I, [2022-11-17T17:45:13.045561 #98122]  INFO -- :   Rendered shared/_advanced_search.html.erb (25.5ms)

I, [2022-11-17T17:45:13.105096 #98122]  INFO -- :   Rendered shared/_header_repository.html.erb (322.2ms)

I, [2022-11-17T17:45:13.110247 #98122]  INFO -- :   Rendered site/_footer.html.erb (0.5ms)

I, [2022-11-17T17:45:13.139762 #98122]  INFO -- :   Rendered shared/_templates.html.erb (24.2ms)

I, [2022-11-17T17:45:13.167381 #98122]  INFO -- : Completed 200 OK in 1343ms (Views: 857.1ms)

 

 

I?ve tested this on a dev server with a backup of our production database, with the ArchivesSpace code replaced with stock builds of 2.8.1 and 3.2.0 from GitHub, using a near-default config that only had the changes necessary to allow connection to MySQL and to specify the PUI/SUI URLs. In these cases the problem still occurs.

 

I have also tried dropping the entire database and created a fresh set of tables (without data) using the database setup script. This seems to work. Thus I conclude that something in the database affects the operation of the user creation component, and this is independent from the config file or code.

 

The key issue is that a value of ?local? is being passed, and the error message is telling me that it should instead "Must be one of: ISAAR (CPF) and NCA Rules?.

 

What do I need to do to get rid of the ?local? value that is being passed and to get the correct value instead?

 

Regards,

 

Philip Webster

The University Library

University of Sheffield

 

 

 

 





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

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

From Corey.Schmidt at uga.edu  Wed Dec 14 09:06:04 2022
From: Corey.Schmidt at uga.edu (Corey Schmidt)
Date: Wed, 14 Dec 2022 14:06:04 +0000
Subject: [Archivesspace_Users_Group] Find by ID API call
In-Reply-To: <ME3PR01MB608849F6AF9F5CFE9090F1A9C0E39@ME3PR01MB6088.ausprd01.prod.outlook.com>
References: <ME3PR01MB6088246898489A25459EECDCC0E39@ME3PR01MB6088.ausprd01.prod.outlook.com>
 <SJ0PR02MB77748FBC0CE0A20623DF4CA7F3E39@SJ0PR02MB7774.namprd02.prod.outlook.com>
 <ME3PR01MB608849F6AF9F5CFE9090F1A9C0E39@ME3PR01MB6088.ausprd01.prod.outlook.com>
Message-ID: <SJ0PR02MB7774838B1A756365B4425BE1F3E09@SJ0PR02MB7774.namprd02.prod.outlook.com>

Alan,

I'm happy to help and glad it's working!

I share your sentiments and frustrations with the API documentation. When I was first starting out, I was pinging the listserv and other places/people for help trying to understand how it works. Some stuff, like including [] in your cURL request parameters or encoding special characters, are just not there. Regarding the lack of documentation surrounding ARKs, I hope to include your example in the API docs for others to use in the future. The examples listed for that find_by_id endpoint don't include the --url-encode as an option, so I may include that in a comment for people having trouble.

Also, I am thinking about hosting an API workshop for people looking to get started or figure out how to use it to help automate their workflows. This isn't confirmed or official in any way, but I am curious to see how many people want something like this to see if it's worth doing. So if you, or others, would be interested - let me or the ASpace team know.

Thanks,

Corey

From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Alan Manifold
Sent: Tuesday, December 13, 2022 5:15 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Find by ID API call

[EXTERNAL SENDER - PROCEED CAUTIOUSLY]
Thanks, Corey,
This one finally worked for me, based on using the --data-urlencode option and seeing what it did, along with the URL that worked for you (which included the host but not the http:// part).

                http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ark[]=ark%3A%2F9999%2F119460<http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ark%5b%5d=ark%3A%2F9999%2F119460>

Embarrassingly, I was using POST instead of GET, which didn't help my testing of the other aspects of the find_by_id API.

I have to say that the answer here was not at all obvious. There was no indication in the doco that you would have to encode the ARK, although all ARKs will have a colon and slashes. Most of our component_id's also have slashes and that wasn't indicated for them, either. Perhaps it's obvious to everyone else, but I have no idea why we include the "[]" after "ark". I guess you can use multiple values or something, but there's no indication of how that is done. It's great to have the full doco for all the APIs, but most of it is pretty cryptic. A few examples of actually use of them would really go a long way. I guess the fact that not so many sites are using ARKs is part of the problem here.

In any case, thank you very much for your help. I'm on my way now and that's down to you.

Regards,
Alan





Alan Manifold | Library Systems & Digital Preservation Manager | Collection Development & Description
State Library Victoria | 328 Swanston Street | Melbourne VIC 3000
T +61 3 8664 7122 | amanifold at slv.vic.gov.au<mailto:amanifold at 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-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> On Behalf Of Corey Schmidt
Sent: Wednesday, 14 December 2022 8:27 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Find by ID API call

Hey Alan,

Big caveat first: we don't use ARKs where I work, so I'm flying a little blind here. I enabled ARKs on our testing space just to see if I could replicate your request. Here's what I tried and it returned the correct archival object:

curl -H "X-ArchivesSpace-Session: $SESSION" "https://our_api_url/repositories/2/find_by_id/archival_objects?ark[]=www.testarkurl.com/ark:/YLTAD111/51/37;resolve[]=archival_objects<https://our_api_url/repositories/2/find_by_id/archival_objects?ark%5b%5d=www.testarkurl.com/ark:/YLTAD111/51/37;resolve%5b%5d=archival_objects>"

I added an external ARK URL to the archival object and put www.testarkurl.com/ark:/YLTAD111/51/37<http://www.testarkurl.com/ark:/YLTAD111/51/37> in that field. Are you using something like this or trying to access internal ARKs? If it's internal, I don't have a way to test that, I'm afraid. Though it seems like the following requests are constructed properly:

http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id[]=YLTAD111/51/37<http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id%5b%5d=YLTAD111/51/37>
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ref_id[]=15a419a9464353be174f77bdc8f38874<http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ref_id%5b%5d=15a419a9464353be174f77bdc8f38874>   (our ref_ids look something like this usually: "ref36_286", that looks like the container_id found in an EAD export)

If you're still getting a 404 error, I might also try using the "--url-encode" parameter to see if that helps. Dave Mayo at Harvard pointed me in this direction which works great for the find_by_id endpoint for resources. Using that would look something like:

curl -H "X-ArchivesSpace-Session: $SESSION" -G http://ourhost.com:8089/repositories/5/find_by_id/archival_objects --data-urlencode 'component_id[]=YLTAD111/51/37'

If you do find a solution, would you mind sharing it with the listserv or me? I wrote the API cURL and Python examples for that endpoint and I couldn't find anyone using ARKs to build an example from. Adding that would be the last piece of the puzzle for that documentation.

Hope this helps,

Corey
Corey Schmidt
Special Collections Libraries | Project Management Librarian/Archivist
Corey.Schmidt at uga.edu<mailto:Corey.Schmidt at uga.edu>
From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> On Behalf Of Alan Manifold
Sent: Monday, December 12, 2022 10:50 PM
To: ArchivesSpace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] Find by ID API call

[EXTERNAL SENDER - PROCEED CAUTIOUSLY]
Hi ArchivesSpace folks,
I've been trying to get the find_by_id API call to work and haven't had any luck. What I really want is to be able to find archival objects by ARK, but I tried the other types of IDs to see if they would work and tell me something useful. But I can't get any of them to work. We're on version 3.2.0. I have a program that establishes a connection and gets a session ID, then sends off the API call. When the same program sends this search API, it works:

http://ourhost.com:8089/search?q=component_id:"YLTAD111/51/37<http://ourhost.com:8089/search?q=component_id:%22YLTAD111/51/37>" OR component_id:"YLTAD111/51/38" OR component_id:"YLTAD111/51/39"&page=1

Here's what I have tried:

http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ark=https://ourhost.com/ark:/9999/119460
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ark=ark:/9999/119460
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ark=119460
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ark[]=ark:/9999/119460<http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ark%5b%5d=ark:/9999/119460>
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ark[]=119460<http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ark%5b%5d=119460>
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id[]=YLTAD111/51/37<http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id%5b%5d=YLTAD111/51/37>
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id[]=YLTAD111%2F51%2F37<http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id%5b%5d=YLTAD111%2F51%2F37>
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id[]='YLTAD111%2F51%2F37<http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id%5b%5d='YLTAD111%2F51%2F37>'
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id[]='YLTAD111<http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id%5b%5d='YLTAD111>'
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id[]=YLTAD111<http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id%5b%5d=YLTAD111>
http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id[]=YLTAD111<http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id%5b%5d=YLTAD111>
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id[]=YLTAD111;resolve[]=archival_objects<http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?component_id%5b%5d=YLTAD111;resolve%5b%5d=archival_objects>
http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id[]=MS%2015856;resolve[]=archival_objects<http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id%5b%5d=MS%2015856;resolve%5b%5d=archival_objects>
http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id[]=MS<http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id%5b%5d=MS> 15856;resolve[]=archival_objects
http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id[]=MS_15856;resolve[]=archival_objects<http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id%5b%5d=MS_15856;resolve%5b%5d=archival_objects>
http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id[]=MS10840-1.1.1;resolve[]=archival_objects<http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id%5b%5d=MS10840-1.1.1;resolve%5b%5d=archival_objects>
http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id[]=MS10840-1.1.1;resolve[]=archival_objects<http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id%5b%5d=MS10840-1.1.1;resolve%5b%5d=archival_objects>
http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id[]=MS10840-1.1.1<http://ourhost.com:8089/repositories/3/find_by_id/archival_objects?component_id%5b%5d=MS10840-1.1.1>
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ref_id[]=15a419a9464353be174f77bdc8f38874<http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ref_id%5b%5d=15a419a9464353be174f77bdc8f38874>
http://ourhost.com:8089/repositories/5/find_by_id/archival_objects?ref_id=15a419a9464353be174f77bdc8f38874

Every single call returned a 404 error. Can anyone tell me what I'm doing wrong? I'll feel stupid if it's obvious, but I'll still be thankful. Thanks so much!

Regards,
Alan



Alan Manifold | Library Systems & Digital Preservation Manager | Collection Development & Description
State Library Victoria | 328 Swanston Street | Melbourne VIC 3000
T +61 3 8664 7122 | amanifold at slv.vic.gov.au<mailto:amanifold at 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>



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.
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221214/c913ce30/attachment.html>

From mcyzyk at gmail.com  Wed Dec 14 10:34:26 2022
From: mcyzyk at gmail.com (Mark Cyzyk)
Date: Wed, 14 Dec 2022 10:34:26 -0500
Subject: [Archivesspace_Users_Group] ASpace, Bootstrap?
Message-ID: <6902add3-4767-5319-160b-31af75375eed@gmail.com>


All,

I have a question:? Does the current version of ASpace include Bootstrap?

I ask because when I Inspect, say, the footer in the ASpace Sandbox 
(https://sandbox.archivesspace.org/) I see things like:


 ? <div class="row">
 ???? <div class="col-md-12">
 ?????? <p class="footer-items"><a 
href="https://sandbox.archivesspace.org/staff/">Staff Interface</a>
 ???????? | Visit <a href="http://archivesspace.org">ArchivesSpace.org</a>
 ???????? | v3.3.1
 ????????? | <a id="aspaceFeedbackLink" 
href="https://archivesspace.org/contact" target="_blank">Send Feedback 
or Report a Problem</a></p>
 ???? </div>
 ? </div>

Looks like Bootstrap rows and columns to me!

And yet, when I look to see what files are actually coming over the 
Network, in my Inspector, I do not see any mention of the Bootstrap CSS 
and JS files.

I ask because I want to simply plug some text into our Footer and 
thought I'd just break a Bootstrap Row there into two Cols.

But no joy!? My Col div directives appear to be completely ignored. (All 
works great in a template on my local workstation, but I'm loading the 
CDN versions of Bootstrap CSS and JS there...)

Does the current version of ASpace include Bootstrap?? If so, which 
version of Bootstrap?

Puzzled,
And Thanks!

Mark

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

Verba volant, scripta manent.


From kmc35 at psu.edu  Wed Dec 14 10:48:56 2022
From: kmc35 at psu.edu (Clair, Kevin)
Date: Wed, 14 Dec 2022 15:48:56 +0000
Subject: [Archivesspace_Users_Group] ASpace, Bootstrap?
In-Reply-To: <6902add3-4767-5319-160b-31af75375eed@gmail.com>
References: <6902add3-4767-5319-160b-31af75375eed@gmail.com>
Message-ID: <BN6PR02MB24509227BC17820FCB0AFC7DB5E09@BN6PR02MB2450.namprd02.prod.outlook.com>

Hi Mark,

I think it runs on Bootstrap 3, because Bootstrap 4 things that I've attempted to use in plugins don't work unless I supply the CSS directions myself.  -k
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Mark Cyzyk <mcyzyk at gmail.com>
Sent: Wednesday, December 14, 2022 10:34 AM
To: archivesspace_users_group at lyralists.lyrasis.org <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] ASpace, Bootstrap?


All,

I have a question:  Does the current version of ASpace include Bootstrap?

I ask because when I Inspect, say, the footer in the ASpace Sandbox
(https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsandbox.archivesspace.org%2F&data=05%7C01%7Ckmc35%40psu.edu%7Cfdf027e3dcb04b46f22508dadde8b288%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C638066288749094905%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2FvCKU%2BpylNK6yO0Ut7tu2kOkRaqYyP72Iq1VuMTTvYY%3D&reserved=0) I see things like:


   <div class="row">
      <div class="col-md-12">
        <p class="footer-items"><a
href="https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsandbox.archivesspace.org%2Fstaff%2F&data=05%7C01%7Ckmc35%40psu.edu%7Cfdf027e3dcb04b46f22508dadde8b288%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C638066288749094905%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=GqiFSqMLv6eWn0TAZWhNLTSSfn1JSwbWIc3SBtfebow%3D&reserved=0">Staff Interface</a>
          | Visit <a href="https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Farchivesspace.org%2F&data=05%7C01%7Ckmc35%40psu.edu%7Cfdf027e3dcb04b46f22508dadde8b288%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C638066288749094905%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=15Bbxukvu8L4dxqB1Qf7tZAtjkutATl8dOmXkryQAx8%3D&reserved=0">ArchivesSpace.org</a>
          | v3.3.1
           | <a id="aspaceFeedbackLink"
href="https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Farchivesspace.org%2Fcontact&data=05%7C01%7Ckmc35%40psu.edu%7Cfdf027e3dcb04b46f22508dadde8b288%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C638066288749094905%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=jCegREq%2Fa9vKIsKTLHZcZ30x%2BzbJo93lsaT6pYp%2F7y4%3D&reserved=0" target="_blank">Send Feedback
or Report a Problem</a></p>
      </div>
   </div>

Looks like Bootstrap rows and columns to me!

And yet, when I look to see what files are actually coming over the
Network, in my Inspector, I do not see any mention of the Bootstrap CSS
and JS files.

I ask because I want to simply plug some text into our Footer and
thought I'd just break a Bootstrap Row there into two Cols.

But no joy!  My Col div directives appear to be completely ignored. (All
works great in a template on my local workstation, but I'm loading the
CDN versions of Bootstrap CSS and JS there...)

Does the current version of ASpace include Bootstrap?  If so, which
version of Bootstrap?

Puzzled,
And Thanks!

Mark

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

Verba volant, scripta manent.

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org
https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group&data=05%7C01%7Ckmc35%40psu.edu%7Cfdf027e3dcb04b46f22508dadde8b288%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C638066288749094905%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=3GxhI43Ri25lxjuxXHkM0mukodifO%2FpMxX57jczuMFo%3D&reserved=0
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221214/a8b4e57c/attachment.html>

From brian.zelip at lyrasis.org  Wed Dec 14 10:56:24 2022
From: brian.zelip at lyrasis.org (Brian Zelip)
Date: Wed, 14 Dec 2022 15:56:24 +0000
Subject: [Archivesspace_Users_Group] ASpace, Bootstrap?
In-Reply-To: <BN6PR02MB24509227BC17820FCB0AFC7DB5E09@BN6PR02MB2450.namprd02.prod.outlook.com>
References: <6902add3-4767-5319-160b-31af75375eed@gmail.com>
 <BN6PR02MB24509227BC17820FCB0AFC7DB5E09@BN6PR02MB2450.namprd02.prod.outlook.com>
Message-ID: <PH0PR22MB3428947126D4CC7C24C71755F3E09@PH0PR22MB3428.namprd22.prod.outlook.com>

Hi all ? yes AS runs on Bootstrap 3 currently. Here are the related docs per app:


  *   Public interface, https://getbootstrap.com/docs/3.4/
  *   Staff interface, https://getbootstrap.com/docs/3.3/

We?ll all be glad when these are updated to latest!

Brian Zelip

---
Front End Developer, ArchivesSpace
brian.zelip at lyrasis.org
he/him



From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Clair, Kevin <kmc35 at psu.edu>
Date: Wednesday, December 14, 2022 at 10:49 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] ASpace, Bootstrap?
Hi Mark,

I think it runs on Bootstrap 3, because Bootstrap 4 things that I've attempted to use in plugins don't work unless I supply the CSS directions myself.  -k
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Mark Cyzyk <mcyzyk at gmail.com>
Sent: Wednesday, December 14, 2022 10:34 AM
To: archivesspace_users_group at lyralists.lyrasis.org <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] ASpace, Bootstrap?


All,

I have a question:  Does the current version of ASpace include Bootstrap?

I ask because when I Inspect, say, the footer in the ASpace Sandbox
(https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsandbox.archivesspace.org%2F&data=05%7C01%7Ckmc35%40psu.edu%7Cfdf027e3dcb04b46f22508dadde8b288%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C638066288749094905%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2FvCKU%2BpylNK6yO0Ut7tu2kOkRaqYyP72Iq1VuMTTvYY%3D&reserved=0) I see things like:


   <div class="row">
      <div class="col-md-12">
        <p class="footer-items"><a
href="https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsandbox.archivesspace.org%2Fstaff%2F&data=05%7C01%7Ckmc35%40psu.edu%7Cfdf027e3dcb04b46f22508dadde8b288%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C638066288749094905%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=GqiFSqMLv6eWn0TAZWhNLTSSfn1JSwbWIc3SBtfebow%3D&reserved=0">Staff Interface</a>
          | Visit <a href="https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Farchivesspace.org%2F&data=05%7C01%7Ckmc35%40psu.edu%7Cfdf027e3dcb04b46f22508dadde8b288%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C638066288749094905%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=15Bbxukvu8L4dxqB1Qf7tZAtjkutATl8dOmXkryQAx8%3D&reserved=0">ArchivesSpace.org</a<https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Farchivesspace.org%2F&data=05%7C01%7Ckmc35%40psu.edu%7Cfdf027e3dcb04b46f22508dadde8b288%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C638066288749094905%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=15Bbxukvu8L4dxqB1Qf7tZAtjkutATl8dOmXkryQAx8%3D&reserved=0%22%3eArchivesSpace.org%3c/a>>
          | v3.3.1
           | <a id="aspaceFeedbackLink"
href="https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Farchivesspace.org%2Fcontact&data=05%7C01%7Ckmc35%40psu.edu%7Cfdf027e3dcb04b46f22508dadde8b288%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C638066288749094905%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=jCegREq%2Fa9vKIsKTLHZcZ30x%2BzbJo93lsaT6pYp%2F7y4%3D&reserved=0" target="_blank">Send Feedback
or Report a Problem</a></p>
      </div>
   </div>

Looks like Bootstrap rows and columns to me!

And yet, when I look to see what files are actually coming over the
Network, in my Inspector, I do not see any mention of the Bootstrap CSS
and JS files.

I ask because I want to simply plug some text into our Footer and
thought I'd just break a Bootstrap Row there into two Cols.

But no joy!  My Col div directives appear to be completely ignored. (All
works great in a template on my local workstation, but I'm loading the
CDN versions of Bootstrap CSS and JS there...)

Does the current version of ASpace include Bootstrap?  If so, which
version of Bootstrap?

Puzzled,
And Thanks!

Mark

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

Verba volant, scripta manent.

_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org
https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group&data=05%7C01%7Ckmc35%40psu.edu%7Cfdf027e3dcb04b46f22508dadde8b288%7C7cf48d453ddb4389a9c1c115526eb52e%7C0%7C0%7C638066288749094905%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=3GxhI43Ri25lxjuxXHkM0mukodifO%2FpMxX57jczuMFo%3D&reserved=0
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221214/1d8a9e4c/attachment.html>

From jagriffis at mail.wvu.edu  Wed Dec 14 13:14:30 2022
From: jagriffis at mail.wvu.edu (Jesse Griffis)
Date: Wed, 14 Dec 2022 18:14:30 +0000
Subject: [Archivesspace_Users_Group] Issue with searching by identifier in
	PUI
Message-ID: <SN6PR03MB35843B68CBDE241955E5359B9EE09@SN6PR03MB3584.namprd03.prod.outlook.com>

Good Afternoon All,

My team is in the process of upgrading from 2.8.0 to 3.3.1 and we're encountering an odd error. In our 2.8.0 version we are able to search by identifier and obtain a specific record in the PUI. The same search in 3.3.1 returns no records. We would greatly appreciate any advice or tips to point us in the right direction on this issue.

Jesse Griffis
Prof. Tech. 2
Systems Development
WVU Libraries
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221214/20baa773/attachment.html>

From andrew-holland at uiowa.edu  Thu Dec 15 08:25:04 2022
From: andrew-holland at uiowa.edu (Holland, Andrew S)
Date: Thu, 15 Dec 2022 13:25:04 +0000
Subject: [Archivesspace_Users_Group] Preferred Citation Notes
Message-ID: <CH2PR04MB7000254157EB049CF59667FC8FE19@CH2PR04MB7000.namprd04.prod.outlook.com>

Hello all,

I can seem to figure out how to get our notes put in to the Preferred Citation field to show up on the public site. Can anyone help me?

Thanks,

Andrew Holland
University of Iowa Libraries



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

From etu at iisg.nl  Thu Dec 15 10:38:02 2022
From: etu at iisg.nl (Erhan Tuskan)
Date: Thu, 15 Dec 2022 15:38:02 +0000
Subject: [Archivesspace_Users_Group] Modifying User Defined fields
Message-ID: <5df0e9b16dbe459ba5021f1a9eef78ee@EXCH35.ia.knaw.local>

Hello Everybody,

At IISH we would like to use a few user defined fields for the Accessions. We have changed the translations in the en.yml as explained in the User manual but all our attempts failed, resulting in the following:

[cid:image002.jpg at 01D910A3.98CB1520]

We have also tried, without success, the plug-in at https://github.com/hudmol/user_defined_in_basic. Our developer thinks that this is not compatible with v3.3.1 any more

Any tips and suggestions will be appreciated.

Thanks in advance,

Erhan Tuskan

International Institute of Social History
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221215/75897d9d/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 19036 bytes
Desc: image002.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221215/75897d9d/attachment.jpg>

From kbatyuk at whoi.edu  Thu Dec 15 12:24:57 2022
From: kbatyuk at whoi.edu (Kirill Batyuk)
Date: Thu, 15 Dec 2022 17:24:57 +0000
Subject: [Archivesspace_Users_Group] Archivematica DIP upload into
	Archivesspace problem
Message-ID: <DM6PR16MB3545528CB10E0F4FA83C459EC2E19@DM6PR16MB3545.namprd16.prod.outlook.com>

Hello,

Possible I can get some help with setting up DIP upload from Archivematica to ArchivesSpace.
I see to have set everything up per instructions. But, when I try to upload the DIP I get an error. The Archivematica log shows the following:

ERROR     2022-12-15 17:12:53  agentarchives.archivesspace.client:client:_request:165:  Response code: 404
ERROR     2022-12-15 17:12:53  agentarchives.archivesspace.client:client:_request:166:  Response body: {"error":"Sinatra::NotFound"}

ERROR     2022-12-15 17:12:53  django.request:exception:handle_uncaught_exception:135:  Internal Server Error: /ingest/865b46b7-f16f-40a2-af7a-52e0ef433f85/upload/as/
Traceback (most recent call last):
  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/django/core/handlers/exception.py", line 41, in inner
    response = get_response(request)
  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/django/core/handlers/base.py", line 187, in _get_response
    response = self.process_exception_by_middleware(e, request)
  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/django/core/handlers/base.py", line 185, in _get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File "/usr/share/archivematica/dashboard/components/ingest/views_as.py", line 79, in wrapper
    return func(client, *args, **kwargs)
  File "/usr/share/archivematica/dashboard/components/ingest/views_as.py", line 102, in ingest_upload_as
    uuid,
  File "/usr/share/archivematica/dashboard/components/ingest/pair_matcher.py", line 74, in list_records
    page = helpers.pager(resources, PAGE_SIZE, page_number)
  File "/usr/share/archivematica/dashboard/components/helpers.py", line 126, in pager
    page = paginator.page(current_page_number)
  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/django/core/paginator.py", line 62, in page
    return self._get_page(self.object_list[bottom:top], number, self)
  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/lazy_paged_sequence.py", line 57, in __getitem__
    return [self.__getitem__(i) for i in range(index.start, index.stop, step)]
  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/lazy_paged_sequence.py", line 57, in <listcomp>
    return [self.__getitem__(i) for i in range(index.start, index.stop, step)]
  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/lazy_paged_sequence.py", line 64, in __getitem__
    self.__cache[page_number] = self.page_func(page_number, self.page_size)
  File "/usr/share/archivematica/dashboard/components/ingest/pair_matcher.py", line 69, in <lambda>
    sort_by=sort_by,
  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/agentarchives/archivesspace/client.py", line 739, in find_collections
    return [format_record(json.loads(r["json"])) for r in hits["results"]]
  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/agentarchives/archivesspace/client.py", line 739, in <listcomp>
    return [format_record(json.loads(r["json"])) for r in hits["results"]]
  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/agentarchives/archivesspace/client.py", line 703, in format_record
    self._get(record["uri"] + "/tree", params={"page": 1}).json()[
  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/agentarchives/archivesspace/client.py", line 185, in _get
    self.session.get, url, params=params, expected_response=expected_response
  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/agentarchives/archivesspace/client.py", line 167, in _request
    raise CommunicationError(response.status_code, response)
agentarchives.archivesspace.client.CommunicationError: ArchivesSpace server responded 404

What is interesting, is if I change my settings from repository 2 to repository 1 it lets me to continue to next step, but it does not see any titles because repo 1 is empty . Repository 2 is a default and that is what giving me an error.

Any help would be greatly appreciated.

Thank you,



Kirill Batyuk [A button for name playback in email signature] <https://www.name-coach.com/kirill-batyuk>
Systems Librarian
MBLWHOI Library
Data Library and Archives
Woods Hole Oceanographic Institution
508-289-2850
kbatyuk at whoi.edu<mailto:kbatyuk at whoi.edu>
mblwhoilibrary.org<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.com%2Fv3%2F__http%3A%2Fmblwhoilibrary.org%2F__%3B!!NkSChLMW7qAT!qzl-Bw_htCSDBNQJszDywSpH7dOtkXO9Vs5MFihCtlGhhw559rfEgq-mCQ8O4cqor2tQ47n6Alhw%24&data=02%7C01%7Ckbatyuk%40whoi.edu%7C22c0a3f635574b32bbc708d869775c57%7Cd44c5cc6d18c46cc8abd4fdf5b6e5944%7C0%7C0%7C637375308676908325&sdata=JUxSBfV4tndevzK45XLBwhtOIu6glwiUh4J15EFAEiA%3D&reserved=0> --- whoi.edu<https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwhoi.edu%2F&data=02%7C01%7Ckbatyuk%40whoi.edu%7C22c0a3f635574b32bbc708d869775c57%7Cd44c5cc6d18c46cc8abd4fdf5b6e5944%7C0%7C0%7C637375308676918319&sdata=RKd1NDGHHeIeKE7Fnf%2BT0hgmxfQymHBSR2TdbmL%2Bvqg%3D&reserved=0>
ORCID<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.com%2Fv3%2F__http%3A%2Forcid.org%2F0000-0003-0240-2209__%3B!!NkSChLMW7qAT!qzl-Bw_htCSDBNQJszDywSpH7dOtkXO9Vs5MFihCtlGhhw559rfEgq-mCQ8O4cqor2tQ46IK8ae6%24&data=02%7C01%7Ckbatyuk%40whoi.edu%7C22c0a3f635574b32bbc708d869775c57%7Cd44c5cc6d18c46cc8abd4fdf5b6e5944%7C0%7C0%7C637375308676918319&sdata=dpSW2YomKCqBKXj4aGam%2BrIpKqFhF2%2FV9hxt9Nu6wGI%3D&reserved=0>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221215/f570eed3/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 1734 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221215/f570eed3/attachment.png>

From blake.carver at lyrasis.org  Thu Dec 15 12:46:36 2022
From: blake.carver at lyrasis.org (Blake Carver)
Date: Thu, 15 Dec 2022 17:46:36 +0000
Subject: [Archivesspace_Users_Group] Archivematica DIP upload
	into	Archivesspace problem
In-Reply-To: <DM6PR16MB3545528CB10E0F4FA83C459EC2E19@DM6PR16MB3545.namprd16.prod.outlook.com>
References: <DM6PR16MB3545528CB10E0F4FA83C459EC2E19@DM6PR16MB3545.namprd16.prod.outlook.com>
Message-ID: <DM6PR22MB230998AFEF7E02A4AAE6CD209FE19@DM6PR22MB2309.namprd22.prod.outlook.com>

Are you sure the repository ID is 2? Could it be 3?

________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Kirill Batyuk <kbatyuk at whoi.edu>
Sent: Thursday, December 15, 2022 12:24 PM
To: archivesspace_users_group at lyralists.lyrasis.org <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Archivematica DIP upload into Archivesspace problem


Hello,



Possible I can get some help with setting up DIP upload from Archivematica to ArchivesSpace.

I see to have set everything up per instructions. But, when I try to upload the DIP I get an error. The Archivematica log shows the following:



ERROR     2022-12-15 17:12:53  agentarchives.archivesspace.client:client:_request:165:  Response code: 404

ERROR     2022-12-15 17:12:53  agentarchives.archivesspace.client:client:_request:166:  Response body: {"error":"Sinatra::NotFound"}



ERROR     2022-12-15 17:12:53  django.request:exception:handle_uncaught_exception:135:  Internal Server Error: /ingest/865b46b7-f16f-40a2-af7a-52e0ef433f85/upload/as/

Traceback (most recent call last):

  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/django/core/handlers/exception.py", line 41, in inner

    response = get_response(request)

  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/django/core/handlers/base.py", line 187, in _get_response

    response = self.process_exception_by_middleware(e, request)

  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/django/core/handlers/base.py", line 185, in _get_response

    response = wrapped_callback(request, *callback_args, **callback_kwargs)

  File "/usr/share/archivematica/dashboard/components/ingest/views_as.py", line 79, in wrapper

    return func(client, *args, **kwargs)

  File "/usr/share/archivematica/dashboard/components/ingest/views_as.py", line 102, in ingest_upload_as

    uuid,

  File "/usr/share/archivematica/dashboard/components/ingest/pair_matcher.py", line 74, in list_records

    page = helpers.pager(resources, PAGE_SIZE, page_number)

  File "/usr/share/archivematica/dashboard/components/helpers.py", line 126, in pager

    page = paginator.page(current_page_number)

  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/django/core/paginator.py", line 62, in page

    return self._get_page(self.object_list[bottom:top], number, self)

  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/lazy_paged_sequence.py", line 57, in __getitem__

    return [self.__getitem__(i) for i in range(index.start, index.stop, step)]

  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/lazy_paged_sequence.py", line 57, in <listcomp>

    return [self.__getitem__(i) for i in range(index.start, index.stop, step)]

  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/lazy_paged_sequence.py", line 64, in __getitem__

    self.__cache[page_number] = self.page_func(page_number, self.page_size)

  File "/usr/share/archivematica/dashboard/components/ingest/pair_matcher.py", line 69, in <lambda>

    sort_by=sort_by,

  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/agentarchives/archivesspace/client.py", line 739, in find_collections

    return [format_record(json.loads(r["json"])) for r in hits["results"]]

  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/agentarchives/archivesspace/client.py", line 739, in <listcomp>

    return [format_record(json.loads(r["json"])) for r in hits["results"]]

  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/agentarchives/archivesspace/client.py", line 703, in format_record

    self._get(record["uri"] + "/tree", params={"page": 1}).json()[

  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/agentarchives/archivesspace/client.py", line 185, in _get

    self.session.get, url, params=params, expected_response=expected_response

  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/agentarchives/archivesspace/client.py", line 167, in _request

    raise CommunicationError(response.status_code, response)

agentarchives.archivesspace.client.CommunicationError: ArchivesSpace server responded 404



What is interesting, is if I change my settings from repository 2 to repository 1 it lets me to continue to next step, but it does not see any titles because repo 1 is empty . Repository 2 is a default and that is what giving me an error.



Any help would be greatly appreciated.



Thank you,







Kirill Batyuk [A button for name playback in email signature] <https://www.name-coach.com/kirill-batyuk>

Systems Librarian

MBLWHOI Library

Data Library and Archives

Woods Hole Oceanographic Institution

508-289-2850

kbatyuk at whoi.edu<mailto:kbatyuk at whoi.edu>

mblwhoilibrary.org<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.com%2Fv3%2F__http%3A%2Fmblwhoilibrary.org%2F__%3B!!NkSChLMW7qAT!qzl-Bw_htCSDBNQJszDywSpH7dOtkXO9Vs5MFihCtlGhhw559rfEgq-mCQ8O4cqor2tQ47n6Alhw%24&data=02%7C01%7Ckbatyuk%40whoi.edu%7C22c0a3f635574b32bbc708d869775c57%7Cd44c5cc6d18c46cc8abd4fdf5b6e5944%7C0%7C0%7C637375308676908325&sdata=JUxSBfV4tndevzK45XLBwhtOIu6glwiUh4J15EFAEiA%3D&reserved=0> --- whoi.edu<https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwhoi.edu%2F&data=02%7C01%7Ckbatyuk%40whoi.edu%7C22c0a3f635574b32bbc708d869775c57%7Cd44c5cc6d18c46cc8abd4fdf5b6e5944%7C0%7C0%7C637375308676918319&sdata=RKd1NDGHHeIeKE7Fnf%2BT0hgmxfQymHBSR2TdbmL%2Bvqg%3D&reserved=0>

ORCID<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.com%2Fv3%2F__http%3A%2Forcid.org%2F0000-0003-0240-2209__%3B!!NkSChLMW7qAT!qzl-Bw_htCSDBNQJszDywSpH7dOtkXO9Vs5MFihCtlGhhw559rfEgq-mCQ8O4cqor2tQ46IK8ae6%24&data=02%7C01%7Ckbatyuk%40whoi.edu%7C22c0a3f635574b32bbc708d869775c57%7Cd44c5cc6d18c46cc8abd4fdf5b6e5944%7C0%7C0%7C637375308676918319&sdata=dpSW2YomKCqBKXj4aGam%2BrIpKqFhF2%2FV9hxt9Nu6wGI%3D&reserved=0>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221215/d3bd4d4b/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 1734 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221215/d3bd4d4b/attachment.png>

From blake.carver at lyrasis.org  Thu Dec 15 12:46:54 2022
From: blake.carver at lyrasis.org (Blake Carver)
Date: Thu, 15 Dec 2022 17:46:54 +0000
Subject: [Archivesspace_Users_Group] Modifying User Defined fields
In-Reply-To: <5df0e9b16dbe459ba5021f1a9eef78ee@EXCH35.ia.knaw.local>
References: <5df0e9b16dbe459ba5021f1a9eef78ee@EXCH35.ia.knaw.local>
Message-ID: <DM6PR22MB2309CC78C0F3FE571D1C30889FE19@DM6PR22MB2309.namprd22.prod.outlook.com>

Where do you have your locales en.yml file for that?

________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Erhan Tuskan <etu at iisg.nl>
Sent: Thursday, December 15, 2022 10:38 AM
To: archivesspace_users_group at lyralists.lyrasis.org <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Modifying User Defined fields


Hello Everybody,



At IISH we would like to use a few user defined fields for the Accessions. We have changed the translations in the en.yml as explained in the User manual but all our attempts failed, resulting in the following:



[cid:image002.jpg at 01D910A3.98CB1520]



We have also tried, without success, the plug-in at https://github.com/hudmol/user_defined_in_basic. Our developer thinks that this is not compatible with v3.3.1 any more



Any tips and suggestions will be appreciated.



Thanks in advance,



Erhan Tuskan



International Institute of Social History
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221215/78d39307/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 19036 bytes
Desc: image002.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221215/78d39307/attachment.jpg>

From blake.carver at lyrasis.org  Thu Dec 15 12:48:41 2022
From: blake.carver at lyrasis.org (Blake Carver)
Date: Thu, 15 Dec 2022 17:48:41 +0000
Subject: [Archivesspace_Users_Group] Preferred Citation Notes
In-Reply-To: <CH2PR04MB7000254157EB049CF59667FC8FE19@CH2PR04MB7000.namprd04.prod.outlook.com>
References: <CH2PR04MB7000254157EB049CF59667FC8FE19@CH2PR04MB7000.namprd04.prod.outlook.com>
Message-ID: <DM6PR22MB2309B7A177264BEAD688030D9FE19@DM6PR22MB2309.namprd22.prod.outlook.com>

I think the docs explain it here?

https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/103209762/Public+Interface+Documentation+for+staff#PublicInterfaceDocumentation(forstaff)-CitationactionbuttonandthePreferredCitationnote

________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Holland, Andrew S <andrew-holland at uiowa.edu>
Sent: Thursday, December 15, 2022 8:25 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Preferred Citation Notes


Hello all,



I can seem to figure out how to get our notes put in to the Preferred Citation field to show up on the public site. Can anyone help me?



Thanks,



Andrew Holland

University of Iowa Libraries






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

From blake.carver at lyrasis.org  Thu Dec 15 12:51:35 2022
From: blake.carver at lyrasis.org (Blake Carver)
Date: Thu, 15 Dec 2022 17:51:35 +0000
Subject: [Archivesspace_Users_Group] Issue with searching by identifier
	in	PUI
In-Reply-To: <SN6PR03MB35843B68CBDE241955E5359B9EE09@SN6PR03MB3584.namprd03.prod.outlook.com>
References: <SN6PR03MB35843B68CBDE241955E5359B9EE09@SN6PR03MB3584.namprd03.prod.outlook.com>
Message-ID: <DM6PR22MB2309FF7AE09FF4D9428613AD9FE19@DM6PR22MB2309.namprd22.prod.outlook.com>

Are you sure the 3.3.1 has finished up indexing 100% of everything? Could be it's stuck. Check the logs for ERROR or FATAL
It may also be the search just returns things a bit differently in 3 vs 2, but I'd make sure there's not an indexing issue first.
Can you get the record to show up in results other ways?

________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Jesse Griffis <jagriffis at mail.wvu.edu>
Sent: Wednesday, December 14, 2022 1:14 PM
To: archivesspace_users_group at lyralists.lyrasis.org <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Issue with searching by identifier in PUI

Good Afternoon All,

My team is in the process of upgrading from 2.8.0 to 3.3.1 and we're encountering an odd error. In our 2.8.0 version we are able to search by identifier and obtain a specific record in the PUI. The same search in 3.3.1 returns no records. We would greatly appreciate any advice or tips to point us in the right direction on this issue.

Jesse Griffis
Prof. Tech. 2
Systems Development
WVU Libraries
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221215/bd5d8b95/attachment.html>

From Jessica.Crouch at lyrasis.org  Thu Dec 15 13:00:17 2022
From: Jessica.Crouch at lyrasis.org (Jessica Crouch)
Date: Thu, 15 Dec 2022 18:00:17 +0000
Subject: [Archivesspace_Users_Group] Member Discussion Notes - Future
 Development of the ArchivesSpace Digital Objects Module
In-Reply-To: <DM5PR22MB054063A543B4197F15716F358B3E9@DM5PR22MB0540.namprd22.prod.outlook.com>
References: <E2EAD981-9305-4512-B6EA-F73688764342@lyrasis.org>
 <MN2PR22MB19498F036210B24D708423858BE19@MN2PR22MB1949.namprd22.prod.outlook.com>
 <MN2PR22MB1949A65C83F87516CE51545E8BFD9@MN2PR22MB1949.namprd22.prod.outlook.com>
 <MN2PR22MB1949BE931B72D3249131900C8BDC9@MN2PR22MB1949.namprd22.prod.outlook.com>
 <MN2PR22MB1949E5B6EE730B5A4C1C66448BBA9@MN2PR22MB1949.namprd22.prod.outlook.com>
 <DM5PR22MB05407922B6CDC870AD3A665A8B999@DM5PR22MB0540.namprd22.prod.outlook.com>
 <DM5PR22MB05402F3626F4B5CC7A479C3E8B789@DM5PR22MB0540.namprd22.prod.outlook.com>
 <DM5PR22MB054029E347B7CF8AC6835A708B569@DM5PR22MB0540.namprd22.prod.outlook.com>
 <DM5PR22MB0540182519A854A7757357018B379@DM5PR22MB0540.namprd22.prod.outlook.com>
 <DM5PR22MB054063A543B4197F15716F358B3E9@DM5PR22MB0540.namprd22.prod.outlook.com>
Message-ID: <DM5PR22MB0540A51260D0C820445549EA8BE19@DM5PR22MB0540.namprd22.prod.outlook.com>

Dear ArchivesSpace Members,



Thank you to everyone who joined the ArchivesSpace program team and fellow ArchivesSpace members yesterday for a discussion of the ArchivesSpace Digital Objects Module.



The discussion was not recorded but notes from this discussion are available at https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/3253141506/2022-12-14+Digital+Objects+Member+Discussion<https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/edit-v2/3253141506>.



The survey circulated in advance of this discussion will remain open until December 21, 2022.  This survey is intended to gauge experience with the digital objects module and expectations for future development and all members with an interest in digital objects are welcome to respond to this survey, even if you were not able to attend the discussion.  To complete the survey visit https://www.surveymonkey.com/r/JRCV9F7.



Responses to this survey, in addition to feedback from the discussion, user comments on Digital Object-specific JIRA tickets and results from user testing of new features, will factor into the consideration of next steps for activity around the Digital Objects module.  If you have any questions, please email ArchivesSpaceHome at lyrasis.org<mailto:ArchivesSpaceHome at lyrasis.org>.

Jessica Dowd Crouch
Community Engagement Coordinator for ArchivesSpace
jessica.crouch at lyrasis.org<mailto:jessica.crouch at lyrasis.org>
[page1image482511520]

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

From kbatyuk at whoi.edu  Thu Dec 15 13:04:35 2022
From: kbatyuk at whoi.edu (Kirill Batyuk)
Date: Thu, 15 Dec 2022 18:04:35 +0000
Subject: [Archivesspace_Users_Group] Archivematica DIP
	upload	into	Archivesspace problem
In-Reply-To: <DM6PR22MB230998AFEF7E02A4AAE6CD209FE19@DM6PR22MB2309.namprd22.prod.outlook.com>
References: <DM6PR16MB3545528CB10E0F4FA83C459EC2E19@DM6PR16MB3545.namprd16.prod.outlook.com>
 <DM6PR22MB230998AFEF7E02A4AAE6CD209FE19@DM6PR22MB2309.namprd22.prod.outlook.com>
Message-ID: <DM6PR16MB354563C1A80A4E1B32943831C2E19@DM6PR16MB3545.namprd16.prod.outlook.com>

I am sure it is. All the records in public interface in our ASpace are in /repositories/2/

Kirill.

From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Blake Carver
Sent: Thursday, December 15, 2022 12:47 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Archivematica DIP upload into Archivesspace problem

Are you sure the repository ID is 2? Could it be 3?

________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Kirill Batyuk <kbatyuk at whoi.edu<mailto:kbatyuk at whoi.edu>>
Sent: Thursday, December 15, 2022 12:24 PM
To: archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org> <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] Archivematica DIP upload into Archivesspace problem


Hello,



Possible I can get some help with setting up DIP upload from Archivematica to ArchivesSpace.

I see to have set everything up per instructions. But, when I try to upload the DIP I get an error. The Archivematica log shows the following:



ERROR     2022-12-15 17:12:53  agentarchives.archivesspace.client:client:_request:165:  Response code: 404

ERROR     2022-12-15 17:12:53  agentarchives.archivesspace.client:client:_request:166:  Response body: {"error":"Sinatra::NotFound"}



ERROR     2022-12-15 17:12:53  django.request:exception:handle_uncaught_exception:135:  Internal Server Error: /ingest/865b46b7-f16f-40a2-af7a-52e0ef433f85/upload/as/

Traceback (most recent call last):

  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/django/core/handlers/exception.py", line 41, in inner

    response = get_response(request)

  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/django/core/handlers/base.py", line 187, in _get_response

    response = self.process_exception_by_middleware(e, request)

  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/django/core/handlers/base.py", line 185, in _get_response

    response = wrapped_callback(request, *callback_args, **callback_kwargs)

  File "/usr/share/archivematica/dashboard/components/ingest/views_as.py", line 79, in wrapper

    return func(client, *args, **kwargs)

  File "/usr/share/archivematica/dashboard/components/ingest/views_as.py", line 102, in ingest_upload_as

    uuid,

  File "/usr/share/archivematica/dashboard/components/ingest/pair_matcher.py", line 74, in list_records

    page = helpers.pager(resources, PAGE_SIZE, page_number)

  File "/usr/share/archivematica/dashboard/components/helpers.py", line 126, in pager

    page = paginator.page(current_page_number)

  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/django/core/paginator.py", line 62, in page

    return self._get_page(self.object_list[bottom:top], number, self)

  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/lazy_paged_sequence.py", line 57, in __getitem__

    return [self.__getitem__(i) for i in range(index.start, index.stop, step)]

  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/lazy_paged_sequence.py", line 57, in <listcomp>

    return [self.__getitem__(i) for i in range(index.start, index.stop, step)]

  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/lazy_paged_sequence.py", line 64, in __getitem__

    self.__cache[page_number] = self.page_func(page_number, self.page_size)

  File "/usr/share/archivematica/dashboard/components/ingest/pair_matcher.py", line 69, in <lambda>

    sort_by=sort_by,

  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/agentarchives/archivesspace/client.py", line 739, in find_collections

    return [format_record(json.loads(r["json"])) for r in hits["results"]]

  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/agentarchives/archivesspace/client.py", line 739, in <listcomp>

    return [format_record(json.loads(r["json"])) for r in hits["results"]]

  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/agentarchives/archivesspace/client.py", line 703, in format_record

    self._get(record["uri"] + "/tree", params={"page": 1}).json()[

  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/agentarchives/archivesspace/client.py", line 185, in _get

    self.session.get, url, params=params, expected_response=expected_response

  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/agentarchives/archivesspace/client.py", line 167, in _request

    raise CommunicationError(response.status_code, response)

agentarchives.archivesspace.client.CommunicationError: ArchivesSpace server responded 404



What is interesting, is if I change my settings from repository 2 to repository 1 it lets me to continue to next step, but it does not see any titles because repo 1 is empty . Repository 2 is a default and that is what giving me an error.



Any help would be greatly appreciated.



Thank you,







Kirill Batyuk [A button for name playback in email signature] <https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.name-coach.com%2Fkirill-batyuk&data=05%7C01%7Ckbatyuk%40whoi.edu%7Cafc722cd6e9749a6eafd08dadec4567f%7Cd44c5cc6d18c46cc8abd4fdf5b6e5944%7C0%7C0%7C638067232099054482%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=9VJBZp32VNs0O6hWbA1N1ekBXRPIq9Yvwxhrz%2B%2FawY0%3D&reserved=0>

Systems Librarian

MBLWHOI Library

Data Library and Archives

Woods Hole Oceanographic Institution

508-289-2850

kbatyuk at whoi.edu<mailto:kbatyuk at whoi.edu>

mblwhoilibrary.org<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.com%2Fv3%2F__http%3A%2Fmblwhoilibrary.org%2F__%3B!!NkSChLMW7qAT!qzl-Bw_htCSDBNQJszDywSpH7dOtkXO9Vs5MFihCtlGhhw559rfEgq-mCQ8O4cqor2tQ47n6Alhw%24&data=05%7C01%7Ckbatyuk%40whoi.edu%7Cafc722cd6e9749a6eafd08dadec4567f%7Cd44c5cc6d18c46cc8abd4fdf5b6e5944%7C0%7C0%7C638067232099054482%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2B2o%2Bq8I0qvQm1lqIlphNdehZNoEZvchzHgaSHZYYXJI%3D&reserved=0> --- whoi.edu<https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwhoi.edu%2F&data=05%7C01%7Ckbatyuk%40whoi.edu%7Cafc722cd6e9749a6eafd08dadec4567f%7Cd44c5cc6d18c46cc8abd4fdf5b6e5944%7C0%7C0%7C638067232099054482%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=hoamv71%2FhADuFTjAbHlrfEVWCKu9ymyAqcHID320mek%3D&reserved=0>

ORCID<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.com%2Fv3%2F__http%3A%2Forcid.org%2F0000-0003-0240-2209__%3B!!NkSChLMW7qAT!qzl-Bw_htCSDBNQJszDywSpH7dOtkXO9Vs5MFihCtlGhhw559rfEgq-mCQ8O4cqor2tQ46IK8ae6%24&data=05%7C01%7Ckbatyuk%40whoi.edu%7Cafc722cd6e9749a6eafd08dadec4567f%7Cd44c5cc6d18c46cc8abd4fdf5b6e5944%7C0%7C0%7C638067232099054482%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2FQhijf%2FSORJdPdFq7qfvqQinG6D3aDXpbXdXpZrDF6g%3D&reserved=0>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221215/5e39357d/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 1734 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221215/5e39357d/attachment-0001.png>

From blake.carver at lyrasis.org  Thu Dec 15 13:12:27 2022
From: blake.carver at lyrasis.org (Blake Carver)
Date: Thu, 15 Dec 2022 18:12:27 +0000
Subject: [Archivesspace_Users_Group] Archivematica
	DIP	upload	into	Archivesspace problem
In-Reply-To: <DM6PR16MB354563C1A80A4E1B32943831C2E19@DM6PR16MB3545.namprd16.prod.outlook.com>
References: <DM6PR16MB3545528CB10E0F4FA83C459EC2E19@DM6PR16MB3545.namprd16.prod.outlook.com>
 <DM6PR22MB230998AFEF7E02A4AAE6CD209FE19@DM6PR22MB2309.namprd22.prod.outlook.com>
 <DM6PR16MB354563C1A80A4E1B32943831C2E19@DM6PR16MB3545.namprd16.prod.outlook.com>
Message-ID: <DM6PR22MB23092815529B4D68AF914A8D9FE19@DM6PR22MB2309.namprd22.prod.outlook.com>

I don't know much about Archivematica, but it looks like it's just throwing a "I can't find that URL" error.
When you go to that same URL in a web browser, do you get anything?
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Kirill Batyuk <kbatyuk at whoi.edu>
Sent: Thursday, December 15, 2022 1:04 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Archivematica DIP upload into Archivesspace problem


I am sure it is. All the records in public interface in our ASpace are in /repositories/2/



Kirill.



From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Blake Carver
Sent: Thursday, December 15, 2022 12:47 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Archivematica DIP upload into Archivesspace problem



Are you sure the repository ID is 2? Could it be 3?



________________________________

From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Kirill Batyuk <kbatyuk at whoi.edu<mailto:kbatyuk at whoi.edu>>
Sent: Thursday, December 15, 2022 12:24 PM
To: archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org> <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] Archivematica DIP upload into Archivesspace problem



Hello,



Possible I can get some help with setting up DIP upload from Archivematica to ArchivesSpace.

I see to have set everything up per instructions. But, when I try to upload the DIP I get an error. The Archivematica log shows the following:



ERROR     2022-12-15 17:12:53  agentarchives.archivesspace.client:client:_request:165:  Response code: 404

ERROR     2022-12-15 17:12:53  agentarchives.archivesspace.client:client:_request:166:  Response body: {"error":"Sinatra::NotFound"}



ERROR     2022-12-15 17:12:53  django.request:exception:handle_uncaught_exception:135:  Internal Server Error: /ingest/865b46b7-f16f-40a2-af7a-52e0ef433f85/upload/as/

Traceback (most recent call last):

  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/django/core/handlers/exception.py", line 41, in inner

    response = get_response(request)

  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/django/core/handlers/base.py", line 187, in _get_response

    response = self.process_exception_by_middleware(e, request)

  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/django/core/handlers/base.py", line 185, in _get_response

    response = wrapped_callback(request, *callback_args, **callback_kwargs)

  File "/usr/share/archivematica/dashboard/components/ingest/views_as.py", line 79, in wrapper

    return func(client, *args, **kwargs)

  File "/usr/share/archivematica/dashboard/components/ingest/views_as.py", line 102, in ingest_upload_as

    uuid,

  File "/usr/share/archivematica/dashboard/components/ingest/pair_matcher.py", line 74, in list_records

    page = helpers.pager(resources, PAGE_SIZE, page_number)

  File "/usr/share/archivematica/dashboard/components/helpers.py", line 126, in pager

    page = paginator.page(current_page_number)

  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/django/core/paginator.py", line 62, in page

    return self._get_page(self.object_list[bottom:top], number, self)

  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/lazy_paged_sequence.py", line 57, in __getitem__

    return [self.__getitem__(i) for i in range(index.start, index.stop, step)]

  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/lazy_paged_sequence.py", line 57, in <listcomp>

    return [self.__getitem__(i) for i in range(index.start, index.stop, step)]

  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/lazy_paged_sequence.py", line 64, in __getitem__

    self.__cache[page_number] = self.page_func(page_number, self.page_size)

  File "/usr/share/archivematica/dashboard/components/ingest/pair_matcher.py", line 69, in <lambda>

    sort_by=sort_by,

  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/agentarchives/archivesspace/client.py", line 739, in find_collections

    return [format_record(json.loads(r["json"])) for r in hits["results"]]

  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/agentarchives/archivesspace/client.py", line 739, in <listcomp>

    return [format_record(json.loads(r["json"])) for r in hits["results"]]

  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/agentarchives/archivesspace/client.py", line 703, in format_record

    self._get(record["uri"] + "/tree", params={"page": 1}).json()[

  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/agentarchives/archivesspace/client.py", line 185, in _get

    self.session.get, url, params=params, expected_response=expected_response

  File "/usr/share/archivematica/virtualenvs/archivematica/lib/python3.6/site-packages/agentarchives/archivesspace/client.py", line 167, in _request

    raise CommunicationError(response.status_code, response)

agentarchives.archivesspace.client.CommunicationError: ArchivesSpace server responded 404



What is interesting, is if I change my settings from repository 2 to repository 1 it lets me to continue to next step, but it does not see any titles because repo 1 is empty . Repository 2 is a default and that is what giving me an error.



Any help would be greatly appreciated.



Thank you,







Kirill Batyuk [A button for name playback in email signature] <https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.name-coach.com%2Fkirill-batyuk&data=05%7C01%7Ckbatyuk%40whoi.edu%7Cafc722cd6e9749a6eafd08dadec4567f%7Cd44c5cc6d18c46cc8abd4fdf5b6e5944%7C0%7C0%7C638067232099054482%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=9VJBZp32VNs0O6hWbA1N1ekBXRPIq9Yvwxhrz%2B%2FawY0%3D&reserved=0>

Systems Librarian

MBLWHOI Library

Data Library and Archives

Woods Hole Oceanographic Institution

508-289-2850

kbatyuk at whoi.edu<mailto:kbatyuk at whoi.edu>

mblwhoilibrary.org<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.com%2Fv3%2F__http%3A%2Fmblwhoilibrary.org%2F__%3B!!NkSChLMW7qAT!qzl-Bw_htCSDBNQJszDywSpH7dOtkXO9Vs5MFihCtlGhhw559rfEgq-mCQ8O4cqor2tQ47n6Alhw%24&data=05%7C01%7Ckbatyuk%40whoi.edu%7Cafc722cd6e9749a6eafd08dadec4567f%7Cd44c5cc6d18c46cc8abd4fdf5b6e5944%7C0%7C0%7C638067232099054482%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2B2o%2Bq8I0qvQm1lqIlphNdehZNoEZvchzHgaSHZYYXJI%3D&reserved=0> --- whoi.edu<https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwhoi.edu%2F&data=05%7C01%7Ckbatyuk%40whoi.edu%7Cafc722cd6e9749a6eafd08dadec4567f%7Cd44c5cc6d18c46cc8abd4fdf5b6e5944%7C0%7C0%7C638067232099054482%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=hoamv71%2FhADuFTjAbHlrfEVWCKu9ymyAqcHID320mek%3D&reserved=0>

ORCID<https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.com%2Fv3%2F__http%3A%2Forcid.org%2F0000-0003-0240-2209__%3B!!NkSChLMW7qAT!qzl-Bw_htCSDBNQJszDywSpH7dOtkXO9Vs5MFihCtlGhhw559rfEgq-mCQ8O4cqor2tQ46IK8ae6%24&data=05%7C01%7Ckbatyuk%40whoi.edu%7Cafc722cd6e9749a6eafd08dadec4567f%7Cd44c5cc6d18c46cc8abd4fdf5b6e5944%7C0%7C0%7C638067232099054482%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2FQhijf%2FSORJdPdFq7qfvqQinG6D3aDXpbXdXpZrDF6g%3D&reserved=0>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221215/142b63af/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 1734 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221215/142b63af/attachment.png>

From Jessica.Crouch at lyrasis.org  Thu Dec 15 13:45:06 2022
From: Jessica.Crouch at lyrasis.org (Jessica Crouch)
Date: Thu, 15 Dec 2022 18:45:06 +0000
Subject: [Archivesspace_Users_Group] Member Discussion Notes - Future
 Development of the ArchivesSpace Digital Objects Module
In-Reply-To: <DM5PR22MB0540A51260D0C820445549EA8BE19@DM5PR22MB0540.namprd22.prod.outlook.com>
References: <E2EAD981-9305-4512-B6EA-F73688764342@lyrasis.org>
 <MN2PR22MB19498F036210B24D708423858BE19@MN2PR22MB1949.namprd22.prod.outlook.com>
 <MN2PR22MB1949A65C83F87516CE51545E8BFD9@MN2PR22MB1949.namprd22.prod.outlook.com>
 <MN2PR22MB1949BE931B72D3249131900C8BDC9@MN2PR22MB1949.namprd22.prod.outlook.com>
 <MN2PR22MB1949E5B6EE730B5A4C1C66448BBA9@MN2PR22MB1949.namprd22.prod.outlook.com>
 <DM5PR22MB05407922B6CDC870AD3A665A8B999@DM5PR22MB0540.namprd22.prod.outlook.com>
 <DM5PR22MB05402F3626F4B5CC7A479C3E8B789@DM5PR22MB0540.namprd22.prod.outlook.com>
 <DM5PR22MB054029E347B7CF8AC6835A708B569@DM5PR22MB0540.namprd22.prod.outlook.com>
 <DM5PR22MB0540182519A854A7757357018B379@DM5PR22MB0540.namprd22.prod.outlook.com>
 <DM5PR22MB054063A543B4197F15716F358B3E9@DM5PR22MB0540.namprd22.prod.outlook.com>
 <DM5PR22MB0540A51260D0C820445549EA8BE19@DM5PR22MB0540.namprd22.prod.outlook.com>
Message-ID: <DM5PR22MB054060F1892609387356C2428BE19@DM5PR22MB0540.namprd22.prod.outlook.com>

Dear ArchivesSpace members,

If you are having trouble accessing the discussion notes using the link below, you can either copy that link directly into your browser or click this link<https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/3253141506/2022-12-14+Digital+Objects+Member+Discussion> to navigate directly to the notes.

Best,
Jessica Crouch

Jessica Dowd Crouch
Community Engagement Coordinator for ArchivesSpace
jessica.crouch at lyrasis.org<mailto:jessica.crouch at lyrasis.org>





From: archivesspace_member_match-bounces at lyralists.lyrasis.org <archivesspace_member_match-bounces at lyralists.lyrasis.org> on behalf of Jessica Crouch <Jessica.Crouch at lyrasis.org>
Date: Thursday, December 15, 2022 at 1:00 PM
To: archivesspace_member_match at lyralists.lyrasis.org <archivesspace_member_match at lyralists.lyrasis.org>, Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>, Archivesspace Member Reps <archivesspace_member_reps at lyralists.lyrasis.org>, Archivesspace Small Archives Users Group <archivesspace_small_archives_users_group at lyralists.lyrasis.org>, archivesspace_bot_members at lyralists.lyrasis.org <archivesspace_bot_members at lyralists.lyrasis.org>, archivesspace_tac at lyralists.lyrasis.org <archivesspace_tac at lyralists.lyrasis.org>, archivesspace_uac at lyralists.lyrasis.org <archivesspace_uac at lyralists.lyrasis.org>
Subject: [Archivesspace_member_match] Member Discussion Notes - Future Development of the ArchivesSpace Digital Objects Module

Dear ArchivesSpace Members,



Thank you to everyone who joined the ArchivesSpace program team and fellow ArchivesSpace members yesterday for a discussion of the ArchivesSpace Digital Objects Module.



The discussion was not recorded but notes from this discussion are available at https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/3253141506/2022-12-14+Digital+Objects+Member+Discussion<https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/edit-v2/3253141506>.



The survey circulated in advance of this discussion will remain open until December 21, 2022.  This survey is intended to gauge experience with the digital objects module and expectations for future development and all members with an interest in digital objects are welcome to respond to this survey, even if you were not able to attend the discussion.  To complete the survey visit https://www.surveymonkey.com/r/JRCV9F7.



Responses to this survey, in addition to feedback from the discussion, user comments on Digital Object-specific JIRA tickets and results from user testing of new features, will factor into the consideration of next steps for activity around the Digital Objects module.  If you have any questions, please email ArchivesSpaceHome at lyrasis.org<mailto:ArchivesSpaceHome at lyrasis.org>.

Jessica Dowd Crouch
Community Engagement Coordinator for ArchivesSpace
jessica.crouch at lyrasis.org<mailto:jessica.crouch at lyrasis.org>
[page1image482511520]

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

From jagriffis at mail.wvu.edu  Thu Dec 15 14:23:37 2022
From: jagriffis at mail.wvu.edu (Jesse Griffis)
Date: Thu, 15 Dec 2022 19:23:37 +0000
Subject: [Archivesspace_Users_Group] Issue with searching by identifier
 in	PUI
Message-ID: <SN6PR03MB358412620299365613F2BB519EE19@SN6PR03MB3584.namprd03.prod.outlook.com>

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

From Joshua.D.Shaw at dartmouth.edu  Thu Dec 15 14:33:36 2022
From: Joshua.D.Shaw at dartmouth.edu (Joshua D. Shaw)
Date: Thu, 15 Dec 2022 19:33:36 +0000
Subject: [Archivesspace_Users_Group] Issue with searching by identifier
	in	PUI
In-Reply-To: <SN6PR03MB358412620299365613F2BB519EE19@SN6PR03MB3584.namprd03.prod.outlook.com>
References: <SN6PR03MB358412620299365613F2BB519EE19@SN6PR03MB3584.namprd03.prod.outlook.com>
Message-ID: <BL0PR03MB4292BFB96D8F97F65F5CA627ABE19@BL0PR03MB4292.namprd03.prod.outlook.com>

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

jds
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Jesse Griffis <jagriffis at mail.wvu.edu>
Sent: Thursday, December 15, 2022 2:23 PM
To: archivesspace_users_group at lyralists.lyrasis.org <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Issue with searching by identifier in PUI

You don't often get email from jagriffis at mail.wvu.edu. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>

Thank you for the advice. I believe we waited for the index to finish completely, but I will double check that. We are able to find the record through regular keyword searches, and in the staff UI we can find it using the exact same identifier search term. I have a theory that it may have something to do with input sanitization on the PUI side as well as the issue with identifier truncation mentioned in https://archivesspace.atlassian.net/browse/ANW-1556<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Farchivesspace.atlassian.net%2Fbrowse%2FANW-1556&data=05%7C01%7Cjoshua.d.shaw%40dartmouth.edu%7C285e48f5beaa440cd58408daded1e1ac%7C995b093648d640e5a31ebf689ec9446f%7C0%7C0%7C638067290885360987%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=bOlRnYdKFFIjFL8tGmvHyzfOLB6A1QB7gnKOhZiLEJk%3D&reserved=0> . The identifier in question has an ampersand which gets translated to "&amp;" in the PUI search and since that isn't an exact match to the identifier it doesn't get returned. I've been trying to figure out a way to fix the ampersand issue and test this theory.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221215/cba2f283/attachment.html>

From jagriffis at mail.wvu.edu  Thu Dec 15 14:52:57 2022
From: jagriffis at mail.wvu.edu (Jesse Griffis)
Date: Thu, 15 Dec 2022 19:52:57 +0000
Subject: [Archivesspace_Users_Group] Issue with searching by
	identifier	in	PUI
In-Reply-To: <BL0PR03MB4292BFB96D8F97F65F5CA627ABE19@BL0PR03MB4292.namprd03.prod.outlook.com>
References: <SN6PR03MB358412620299365613F2BB519EE19@SN6PR03MB3584.namprd03.prod.outlook.com>
 <BL0PR03MB4292BFB96D8F97F65F5CA627ABE19@BL0PR03MB4292.namprd03.prod.outlook.com>
Message-ID: <SN6PR03MB3584E821575FFCEC43A2A8B19EE19@SN6PR03MB3584.namprd03.prod.outlook.com>

Thanks for the idea. From a quick test it appears that searching by identifier requires an exact match and doesn't work with wildcards in 3.3.1. Strangely partial matches and wildcards do work in 2.8.0.

Jesse Griffis
Prof. Tech. 2
Systems Development
WVU Libraries
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Joshua D. Shaw <Joshua.D.Shaw at dartmouth.edu>
Sent: Thursday, December 15, 2022 2:33 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Issue with searching by identifier in PUI

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

jds
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Jesse Griffis <jagriffis at mail.wvu.edu>
Sent: Thursday, December 15, 2022 2:23 PM
To: archivesspace_users_group at lyralists.lyrasis.org <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Issue with searching by identifier in PUI

You don't often get email from jagriffis at mail.wvu.edu. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>

Thank you for the advice. I believe we waited for the index to finish completely, but I will double check that. We are able to find the record through regular keyword searches, and in the staff UI we can find it using the exact same identifier search term. I have a theory that it may have something to do with input sanitization on the PUI side as well as the issue with identifier truncation mentioned in https://archivesspace.atlassian.net/browse/ANW-1556<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Farchivesspace.atlassian.net%2Fbrowse%2FANW-1556&data=05%7C01%7Cjoshua.d.shaw%40dartmouth.edu%7C285e48f5beaa440cd58408daded1e1ac%7C995b093648d640e5a31ebf689ec9446f%7C0%7C0%7C638067290885360987%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=bOlRnYdKFFIjFL8tGmvHyzfOLB6A1QB7gnKOhZiLEJk%3D&reserved=0> . The identifier in question has an ampersand which gets translated to "&amp;" in the PUI search and since that isn't an exact match to the identifier it doesn't get returned. I've been trying to figure out a way to fix the ampersand issue and test this theory.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221215/d6c4f46d/attachment.html>

From mcyzyk at gmail.com  Fri Dec 16 09:19:34 2022
From: mcyzyk at gmail.com (Mark Cyzyk)
Date: Fri, 16 Dec 2022 09:19:34 -0500
Subject: [Archivesspace_Users_Group] ASpace, Bootstrap?
In-Reply-To: <6902add3-4767-5319-160b-31af75375eed@gmail.com>
References: <6902add3-4767-5319-160b-31af75375eed@gmail.com>
Message-ID: <24b6b32a-087f-78c7-ccb8-aa3300b35c64@gmail.com>


Thanks Brian and Kevin!

For some reason, I cannot get the simplest Bootstrap 3 code to work in 
my ASpace.? Columns just are not rendering.

So something simple like this:

        <div class="container-fluid">

         ?? <div class="row">

         ?????? <div class="col-md-6">
         ????????? COLUMN ONE
         ?????? </div>

         ?????? <div class="col-md-6">
         ????????? COLUMN TWO
         ?????? </div>

         ?? </div>

        </div>


Is not working.?? Columns render as rows, stacked on top one another.

Do you have a working example of use of Columns in your ASpace you might 
share?

Much appreciated,

Mark

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

Verba volant, scripta manent.

On 12/14/22 10:34, Mark Cyzyk wrote:
>
> All,
>
> I have a question:? Does the current version of ASpace include Bootstrap?
>
> I ask because when I Inspect, say, the footer in the ASpace Sandbox 
> (https://sandbox.archivesspace.org/) I see things like:
>
>
> ? <div class="row">
> ???? <div class="col-md-12">
> ?????? <p class="footer-items"><a 
> href="https://sandbox.archivesspace.org/staff/">Staff Interface</a>
> ???????? | Visit <a href="http://archivesspace.org">ArchivesSpace.org</a>
> ???????? | v3.3.1
> ????????? | <a id="aspaceFeedbackLink" 
> href="https://archivesspace.org/contact" target="_blank">Send Feedback 
> or Report a Problem</a></p>
> ???? </div>
> ? </div>
>
> Looks like Bootstrap rows and columns to me!
>
> And yet, when I look to see what files are actually coming over the 
> Network, in my Inspector, I do not see any mention of the Bootstrap 
> CSS and JS files.
>
> I ask because I want to simply plug some text into our Footer and 
> thought I'd just break a Bootstrap Row there into two Cols.
>
> But no joy!? My Col div directives appear to be completely ignored. 
> (All works great in a template on my local workstation, but I'm 
> loading the CDN versions of Bootstrap CSS and JS there...)
>
> Does the current version of ASpace include Bootstrap?? If so, which 
> version of Bootstrap?
>
> Puzzled,
> And Thanks!
>
> Mark
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221216/f7bdcc8f/attachment.html>

From brian.zelip at lyrasis.org  Fri Dec 16 09:39:12 2022
From: brian.zelip at lyrasis.org (Brian Zelip)
Date: Fri, 16 Dec 2022 14:39:12 +0000
Subject: [Archivesspace_Users_Group] ASpace, Bootstrap?
In-Reply-To: <24b6b32a-087f-78c7-ccb8-aa3300b35c64@gmail.com>
References: <6902add3-4767-5319-160b-31af75375eed@gmail.com>
 <24b6b32a-087f-78c7-ccb8-aa3300b35c64@gmail.com>
Message-ID: <PH0PR22MB3428443CE7CE6FFB32029B08F3E69@PH0PR22MB3428.namprd22.prod.outlook.com>

Try updating the two responsive classes each to just col-6? and see if that works. Perhaps you were looking at a viewport that was less than the md? breakpoint?


bz
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Mark Cyzyk <mcyzyk at gmail.com>
Sent: Friday, December 16, 2022 9:19:34 AM
To: archivesspace_users_group at lyralists.lyrasis.org <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] ASpace, Bootstrap?


Thanks Brian and Kevin!

For some reason, I cannot get the simplest Bootstrap 3 code to work in my ASpace.  Columns just are not rendering.

So something simple like this:

<div class="container-fluid">

   <div class="row">

       <div class="col-md-6">
          COLUMN ONE
       </div>

       <div class="col-md-6">
          COLUMN TWO
       </div>

   </div>

</div>

Is not working.   Columns render as rows, stacked on top one another.

Do you have a working example of use of Columns in your ASpace you might share?

Much appreciated,

Mark

<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
Mark Cyzyk, M.A., M.L.S.
Library Applications Group
The Sheridan Libraries
The Johns Hopkins University
mcyzyk at jhu.edu<mailto:mcyzyk at jhu.edu>

Verba volant, scripta manent.


On 12/14/22 10:34, Mark Cyzyk wrote:

All,

I have a question:  Does the current version of ASpace include Bootstrap?

I ask because when I Inspect, say, the footer in the ASpace Sandbox (https://sandbox.archivesspace.org/) I see things like:


  <div class="row">
     <div class="col-md-12">
       <p class="footer-items"><a href="https://sandbox.archivesspace.org/staff/"<https://sandbox.archivesspace.org/staff/>>Staff Interface</a>
         | Visit <a href="http://archivesspace.org"<http://archivesspace.org>>ArchivesSpace.org</a>
         | v3.3.1
          | <a id="aspaceFeedbackLink" href="https://archivesspace.org/contact"<https://archivesspace.org/contact> target="_blank">Send Feedback or Report a Problem</a></p>
     </div>
  </div>

Looks like Bootstrap rows and columns to me!

And yet, when I look to see what files are actually coming over the Network, in my Inspector, I do not see any mention of the Bootstrap CSS and JS files.

I ask because I want to simply plug some text into our Footer and thought I'd just break a Bootstrap Row there into two Cols.

But no joy!  My Col div directives appear to be completely ignored. (All works great in a template on my local workstation, but I'm loading the CDN versions of Bootstrap CSS and JS there...)

Does the current version of ASpace include Bootstrap?  If so, which version of Bootstrap?

Puzzled,
And Thanks!

Mark


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

From mcyzyk at gmail.com  Fri Dec 16 09:46:30 2022
From: mcyzyk at gmail.com (Mark Cyzyk)
Date: Fri, 16 Dec 2022 09:46:30 -0500
Subject: [Archivesspace_Users_Group] ASpace, Bootstrap?
In-Reply-To: <PH0PR22MB3428443CE7CE6FFB32029B08F3E69@PH0PR22MB3428.namprd22.prod.outlook.com>
References: <6902add3-4767-5319-160b-31af75375eed@gmail.com>
 <24b6b32a-087f-78c7-ccb8-aa3300b35c64@gmail.com>
 <PH0PR22MB3428443CE7CE6FFB32029B08F3E69@PH0PR22MB3428.namprd22.prod.outlook.com>
Message-ID: <8257307c-0012-a3aa-09da-b23b94443e1d@gmail.com>


Darn! |col-6 does not work on my ASpace, nor here on my generic 
Bootstrap 3 test page on my workstation.? Columns still stacking on 
ASpace, and now stacking on generic test page.

Thinking...

Mark
|

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

Verba volant, scripta manent.

On 12/16/22 09:39, Brian Zelip wrote:
> Try updating the two responsive classes each to just |col-6|? and see 
> if that works. Perhaps you were looking at a viewport that was less 
> than the |md|? breakpoint?
>
>
> bz
> ------------------------------------------------------------------------
> *From:* archivesspace_users_group-bounces at lyralists.lyrasis.org 
> <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of 
> Mark Cyzyk <mcyzyk at gmail.com>
> *Sent:* Friday, December 16, 2022 9:19:34 AM
> *To:* archivesspace_users_group at lyralists.lyrasis.org 
> <archivesspace_users_group at lyralists.lyrasis.org>
> *Subject:* Re: [Archivesspace_Users_Group] ASpace, Bootstrap?
>
> Thanks Brian and Kevin!
>
> For some reason, I cannot get the simplest Bootstrap 3 code to work in 
> my ASpace.? Columns just are not rendering.
>
> So something simple like this:
>
>         <div class="container-fluid">
>
>         ?? <div class="row">
>
>         ?????? <div class="col-md-6">
>         ????????? COLUMN ONE
>         ?????? </div>
>
>         ?????? <div class="col-md-6">
>         ????????? COLUMN TWO
>         ?????? </div>
>
>         ?? </div>
>
>         </div>
>
>
> Is not working.?? Columns render as rows, stacked on top one another.
>
> Do you have a working example of use of Columns in your ASpace you 
> might share?
>
> Much appreciated,
>
> Mark
> <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
> Mark Cyzyk, M.A., M.L.S.
> Library Applications Group
> The Sheridan Libraries
> The Johns Hopkins University
> mcyzyk at jhu.edu  <mailto:mcyzyk at jhu.edu>
>
> Verba volant, scripta manent.
> On 12/14/22 10:34, Mark Cyzyk wrote:
>>
>> All,
>>
>> I have a question:? Does the current version of ASpace include 
>> Bootstrap?
>>
>> I ask because when I Inspect, say, the footer in the ASpace Sandbox 
>> (https://sandbox.archivesspace.org/ 
>> <https://sandbox.archivesspace.org/>) I see things like:
>>
>>
>> ? <div class="row">
>> ???? <div class="col-md-12">
>> ?????? <p class="footer-items"><a 
>> href="https://sandbox.archivesspace.org/staff/" 
>> <https://sandbox.archivesspace.org/staff/>>Staff Interface</a>
>> ???????? | Visit <a href="http://archivesspace.org" 
>> <http://archivesspace.org>>ArchivesSpace.org</a>
>> ???????? | v3.3.1
>> ????????? | <a id="aspaceFeedbackLink" 
>> href="https://archivesspace.org/contact" 
>> <https://archivesspace.org/contact> target="_blank">Send Feedback or 
>> Report a Problem</a></p>
>> ???? </div>
>> ? </div>
>>
>> Looks like Bootstrap rows and columns to me!
>>
>> And yet, when I look to see what files are actually coming over the 
>> Network, in my Inspector, I do not see any mention of the Bootstrap 
>> CSS and JS files.
>>
>> I ask because I want to simply plug some text into our Footer and 
>> thought I'd just break a Bootstrap Row there into two Cols.
>>
>> But no joy!? My Col div directives appear to be completely ignored. 
>> (All works great in a template on my local workstation, but I'm 
>> loading the CDN versions of Bootstrap CSS and JS there...)
>>
>> Does the current version of ASpace include Bootstrap?? If so, which 
>> version of Bootstrap?
>>
>> Puzzled,
>> And Thanks!
>>
>> Mark
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221216/1e296636/attachment.html>

From brian.harrington at lyrasis.org  Fri Dec 16 12:13:35 2022
From: brian.harrington at lyrasis.org (Brian Harrington)
Date: Fri, 16 Dec 2022 17:13:35 +0000
Subject: [Archivesspace_Users_Group] Issue with searching
	by	identifier	in	PUI
In-Reply-To: <SN6PR03MB3584E821575FFCEC43A2A8B19EE19@SN6PR03MB3584.namprd03.prod.outlook.com>
References: <SN6PR03MB358412620299365613F2BB519EE19@SN6PR03MB3584.namprd03.prod.outlook.com>
 <BL0PR03MB4292BFB96D8F97F65F5CA627ABE19@BL0PR03MB4292.namprd03.prod.outlook.com>
 <SN6PR03MB3584E821575FFCEC43A2A8B19EE19@SN6PR03MB3584.namprd03.prod.outlook.com>
Message-ID: <CY4PR22MB1656B33EE8D7BA3B15329E2F85E69@CY4PR22MB1656.namprd22.prod.outlook.com>

Hi Jesse,

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

Brian

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

Jesse Griffis
Prof. Tech. 2
Systems Development
WVU Libraries
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Joshua D. Shaw <Joshua.D.Shaw at dartmouth.edu>
Sent: Thursday, December 15, 2022 2:33 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Issue with searching by identifier in PUI

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

jds
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Jesse Griffis <jagriffis at mail.wvu.edu>
Sent: Thursday, December 15, 2022 2:23 PM
To: archivesspace_users_group at lyralists.lyrasis.org <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Issue with searching by identifier in PUI

You don't often get email from jagriffis at mail.wvu.edu. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>

Thank you for the advice. I believe we waited for the index to finish completely, but I will double check that. We are able to find the record through regular keyword searches, and in the staff UI we can find it using the exact same identifier search term. I have a theory that it may have something to do with input sanitization on the PUI side as well as the issue with identifier truncation mentioned in https://archivesspace.atlassian.net/browse/ANW-1556<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Farchivesspace.atlassian.net%2Fbrowse%2FANW-1556&data=05%7C01%7Cjoshua.d.shaw%40dartmouth.edu%7C285e48f5beaa440cd58408daded1e1ac%7C995b093648d640e5a31ebf689ec9446f%7C0%7C0%7C638067290885360987%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=bOlRnYdKFFIjFL8tGmvHyzfOLB6A1QB7gnKOhZiLEJk%3D&reserved=0> . The identifier in question has an ampersand which gets translated to "&amp;" in the PUI search and since that isn't an exact match to the identifier it doesn't get returned. I've been trying to figure out a way to fix the ampersand issue and test this theory.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221216/60a4ac9a/attachment.html>

From jagriffis at mail.wvu.edu  Fri Dec 16 13:48:55 2022
From: jagriffis at mail.wvu.edu (Jesse Griffis)
Date: Fri, 16 Dec 2022 18:48:55 +0000
Subject: [Archivesspace_Users_Group] Issue with
	searching	by	identifier	in	PUI
In-Reply-To: <CY4PR22MB1656B33EE8D7BA3B15329E2F85E69@CY4PR22MB1656.namprd22.prod.outlook.com>
References: <SN6PR03MB358412620299365613F2BB519EE19@SN6PR03MB3584.namprd03.prod.outlook.com>
 <BL0PR03MB4292BFB96D8F97F65F5CA627ABE19@BL0PR03MB4292.namprd03.prod.outlook.com>
 <SN6PR03MB3584E821575FFCEC43A2A8B19EE19@SN6PR03MB3584.namprd03.prod.outlook.com>
 <CY4PR22MB1656B33EE8D7BA3B15329E2F85E69@CY4PR22MB1656.namprd22.prod.outlook.com>
Message-ID: <SN6PR03MB3584E0D68F7AECDCEC5A1E119EE69@SN6PR03MB3584.namprd03.prod.outlook.com>

Thanks, Brian. That JIRA is actually what helped me come up with my theory earlier in this thread. In our case all of our identifiers have ampersands, which combined with the exact match issue from the JIRA causes the PUI identifier search to completely break. Upon digging deeper, it uses "ActionView::Helpers::SanitizeHelper" to sanitize queries which will automatically convert <, &, >, etc. without any way to modify that behavior. Hopefully when that JIRA is addressed we can just use partial matches and avoid searching using ampersands. Until then I'm looking at ways to manipulate the search string post-sanitization.

Jesse Griffis
Prof. Tech. 2
Systems Development
WVU Libraries
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Brian Harrington <brian.harrington at lyrasis.org>
Sent: Friday, December 16, 2022 12:13 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Issue with searching by identifier in PUI


Hi Jesse,



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



Brian



From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Jesse Griffis <jagriffis at mail.wvu.edu>
Date: Thursday, December 15, 2022 at 2:53 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Issue with searching by identifier in PUI

Thanks for the idea. From a quick test it appears that searching by identifier requires an exact match and doesn't work with wildcards in 3.3.1. Strangely partial matches and wildcards do work in 2.8.0.



Jesse Griffis

Prof. Tech. 2

Systems Development

WVU Libraries

________________________________

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



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



jds

________________________________

From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Jesse Griffis <jagriffis at mail.wvu.edu>
Sent: Thursday, December 15, 2022 2:23 PM
To: archivesspace_users_group at lyralists.lyrasis.org <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Issue with searching by identifier in PUI



You don't often get email from jagriffis at mail.wvu.edu. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>

Thank you for the advice. I believe we waited for the index to finish completely, but I will double check that. We are able to find the record through regular keyword searches, and in the staff UI we can find it using the exact same identifier search term. I have a theory that it may have something to do with input sanitization on the PUI side as well as the issue with identifier truncation mentioned in https://archivesspace.atlassian.net/browse/ANW-1556<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Farchivesspace.atlassian.net%2Fbrowse%2FANW-1556&data=05%7C01%7Cjoshua.d.shaw%40dartmouth.edu%7C285e48f5beaa440cd58408daded1e1ac%7C995b093648d640e5a31ebf689ec9446f%7C0%7C0%7C638067290885360987%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=bOlRnYdKFFIjFL8tGmvHyzfOLB6A1QB7gnKOhZiLEJk%3D&reserved=0> . The identifier in question has an ampersand which gets translated to "&amp;" in the PUI search and since that isn't an exact match to the identifier it doesn't get returned. I've been trying to figure out a way to fix the ampersand issue and test this theory.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221216/b3df5efa/attachment.html>

From zachary.pelli at shu.edu  Fri Dec 16 14:53:20 2022
From: zachary.pelli at shu.edu (Zachary L Pelli)
Date: Fri, 16 Dec 2022 19:53:20 +0000
Subject: [Archivesspace_Users_Group] Print to PDF background job fail
Message-ID: <BL3PR01MB7114F19D83619B674BB6D6AFE6E69@BL3PR01MB7114.prod.exchangelabs.com>

Hey, we are seeing this error when attempting to export a PDF of a collection:


Generating PDF for UNA-USA Collection
Internal error evaluating template rule  at line 123 in module file:/var/local/archivesspace/archivesspace/stylesheets/as-ead-pdf.xsl
net.sf.saxon.expr.instruct.TemplateRule.applyLeavingTail(net/sf/saxon/expr/instruct/TemplateRule.java:371)
net.sf.saxon.trans.Mode.applyTemplates(net/sf/saxon/trans/Mode.java:533)
net.sf.saxon.trans.XsltController.applyTemplates(net/sf/saxon/trans/XsltController.java:746)
net.sf.saxon.s9api.Xslt30Transformer.applyTemplates(net/sf/saxon/s9api/Xslt30Transformer.java:441)
java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498)
org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:426)
org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:293)
org.jruby.RubyClass.finvokeWithRefinements(org/jruby/RubyClass.java:514)
org.jruby.RubyBasicObject.send(org/jruby/RubyBasicObject.java:1755)
org.jruby.RubyKernel.send(org/jruby/RubyKernel.java:2200)
org.jruby.RubyKernel$INVOKER$s$send.call(org/jruby/RubyKernel$INVOKER$s$send.gen)
RUBY.invocation_lambda(/var/local/archivesspace/archivesspace/gems/gems/saxon-rb-0.8.3-java/lib/saxon/xslt/executable.rb:270)
org.jruby.RubyProc.call(org/jruby/RubyProc.java:291)
org.jruby.RubyProc$INVOKER$i$call.call(org/jruby/RubyProc$INVOKER$i$call.gen)
RUBY.to_destination(/var/local/archivesspace/archivesspace/gems/gems/saxon-rb-0.8.3-java/lib/saxon/xslt/invocation.rb:73)
RUBY.to_fo(/var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:44)
RUBY.to_pdf(/var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/AS_fop.rb:58)
RUBY.run(/var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:50)
var.local.archivesspace.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.request_context.open(/var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/request_context.rb:24)
RUBY.run(/var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/job_runners/print_to_pdf_runner.rb:13)
var.local.archivesspace.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.invokeOther31:run(var/local/archivesspace/archivesspace/data/tmp/jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_/webapp/WEB_minus_INF/app/lib//var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126)
var.local.archivesspace.archivesspace.data.tmp.jetty_minus_0_dot_0_dot_0_dot_0_minus_8089_minus_backend_dot_war_minus___minus_any_minus_.webapp.WEB_minus_INF.app.lib.background_job_queue.run_pending_job(/var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:126)
RUBY.start_background_thread(/var/local/archivesspace/archivesspace/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/background_job_queue.rb:169)
org.jruby.RubyProc.call(org/jruby/RubyProc.java:318)
java.lang.Thread.run(java/lang/Thread.java:750)



And here is the section in the XSL file the error seems to be referring to:


 <!--  Start main page design and layout -->
    <xsl:template match="/">
        <fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format" font-size="12pt" font-family="KurintoText,KurintoTextJP,KurintoTextKR,KurintoTextSC,NotoSerif">
            <!-- Set up page types and page layouts -->
            <fo:layout-master-set>
                <!-- Page master for Cover Page -->
                <fo:simple-page-master master-name="cover-page" page-width="8.5in" page-height="11in" margin="0.5in">
                    <fo:region-body margin="0.5in 0.5in 1in 0.5in"/>
                    <fo:region-before extent="0.2in"/>
                    <fo:region-after extent="2in"/>
                </fo:simple-page-master>
                <!-- Page master for Table of Contents -->
                <fo:simple-page-master master-name="toc" page-width="8.5in" page-height="11in" margin="0.5in">
                    <fo:region-body margin-top="0.25in" margin-bottom="0.25in"/>
                    <fo:region-before extent="0.5in"/>
                    <fo:region-after extent="0.2in"/>
                </fo:simple-page-master>
                <!-- Page master for Finding Aid Contents -->
                <fo:simple-page-master master-name="contents" page-width="8.5in" page-height="11in" margin="0.5in">
                    <fo:region-body margin-top="0.25in" margin-bottom="0.25in"/>
                    <fo:region-before extent="0.5in"/>
                    <fo:region-after extent="0.2in"/>
                </fo:simple-page-master>
            </fo:layout-master-set>
            <!-- Builds PDF bookmarks for all major sections  -->
            <xsl:apply-templates select="/ead:ead/ead:archdesc" mode="bookmarks"/>
            <!-- The fo:page-sequence establishes headers, footers and the body of the page.-->
            <!-- Cover page layout -->
            <fo:page-sequence master-reference="cover-page">
                <xsl:if test="/ead:ead/ead:eadheader/ead:filedesc/ead:publicationstmt">
                  <fo:static-content flow-name="xsl-region-after">
                        <xsl:apply-templates select="/ead:ead/ead:eadheader/ead:filedesc/ead:publicationstmt" mode="coverPage"/>
                    </fo:static-content>
               </xsl:if>
                <fo:flow flow-name="xsl-region-body">
                    <xsl:apply-templates select="/ead:ead/ead:eadheader/ead:filedesc/ead:titlestmt" mode="coverPage"/>
                </fo:flow>
            </fo:page-sequence>
            <!-- Table of Contents layout -->
            <fo:page-sequence master-reference="toc">
                <!-- Page header -->
                <fo:static-content flow-name="xsl-region-before" margin-top=".15in">
                    <fo:block color="dimgray" font-size="10pt" text-align="center">
                        <xsl:apply-templates select="ead:ead/ead:eadheader/ead:filedesc/ead:titlestmt" mode="pageHeader"/>
                    </fo:block>
                </fo:static-content>
                <!-- Page footer-->
                <fo:static-content flow-name="xsl-region-after">
                    <fo:block text-align="center" color="dimgray">
                        <xsl:text>- Page </xsl:text>
                        <fo:page-number/>
                        <xsl:text> -</xsl:text>
                    </fo:block>
                </fo:static-content>
                <!-- Content of page -->
                <fo:flow flow-name="xsl-region-body">
                    <xsl:apply-templates select="/ead:ead/ead:archdesc" mode="toc"/>
                </fo:flow>
            </fo:page-sequence>
            <!-- All the rest -->
            <fo:page-sequence master-reference="contents">
                <!-- Page header -->
                <fo:static-content flow-name="xsl-region-before" margin-top=".15in">
                 <fo:block color="dimgray" font-size="10pt" text-align="center">
                        <xsl:apply-templates select="ead:ead/ead:eadheader/ead:filedesc/ead:titlestmt" mode="pageHeader"/>
                    </fo:block>
                </fo:static-content>
                <!-- Page footer-->
                <fo:static-content flow-name="xsl-region-after">
                    <fo:block text-align="center">
                        <xsl:text>- Page </xsl:text>
                        <fo:page-number/>
                        <xsl:text>- </xsl:text>
                    </fo:block>
                </fo:static-content>
                <!-- Content of page -->
                <fo:flow flow-name="xsl-region-body">
                    <xsl:apply-templates select="/ead:ead/ead:archdesc"/>
                </fo:flow>
            </fo:page-sequence>
        </fo:root>
    </xsl:template>


Unfortunately my XML/XSL knowledge is limited. I suspect that it may be related to the notes that Preservica adds which includes HTML code, but I'm not sure. Its one of the few things differentiating this collection from others which export successfully.

Regards,


Zach Pelli

Digital Collections Infrastructure Developer

Seton Hall University Libraries

973.275.2046
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221216/7bf050d1/attachment.html>

From Jessica.Crouch at lyrasis.org  Mon Dec 19 09:19:23 2022
From: Jessica.Crouch at lyrasis.org (Jessica Crouch)
Date: Mon, 19 Dec 2022 14:19:23 +0000
Subject: [Archivesspace_Users_Group] Webinar Reminder: Local Contexts
 Initiative and Integration Plugin for ArchivesSpace
In-Reply-To: <DM5PR22MB05407B52120E50B14051D14F8B049@DM5PR22MB0540.namprd22.prod.outlook.com>
References: <E2EAD981-9305-4512-B6EA-F73688764342@lyrasis.org>
 <MN2PR22MB19498F036210B24D708423858BE19@MN2PR22MB1949.namprd22.prod.outlook.com>
 <MN2PR22MB1949A65C83F87516CE51545E8BFD9@MN2PR22MB1949.namprd22.prod.outlook.com>
 <MN2PR22MB1949BE931B72D3249131900C8BDC9@MN2PR22MB1949.namprd22.prod.outlook.com>
 <MN2PR22MB1949E5B6EE730B5A4C1C66448BBA9@MN2PR22MB1949.namprd22.prod.outlook.com>
 <DM5PR22MB05407922B6CDC870AD3A665A8B999@DM5PR22MB0540.namprd22.prod.outlook.com>
 <DM5PR22MB05402F3626F4B5CC7A479C3E8B789@DM5PR22MB0540.namprd22.prod.outlook.com>
 <DM5PR22MB054029E347B7CF8AC6835A708B569@DM5PR22MB0540.namprd22.prod.outlook.com>
 <DM5PR22MB0540182519A854A7757357018B379@DM5PR22MB0540.namprd22.prod.outlook.com>
 <DM5PR22MB05407B52120E50B14051D14F8B049@DM5PR22MB0540.namprd22.prod.outlook.com>
Message-ID: <DM5PR22MB0540257B38944BB3399CEFA78BE59@DM5PR22MB0540.namprd22.prod.outlook.com>

Dear ArchivesSpace Users,

Join ArchivesSpace community members and Local Contexts<https://localcontexts.org/> project members for a webinar on January 18, 2023, at 2:00pm ET/11:00am PT on the Local Contexts initiative and the new ArchivesSpace plugin<https://github.com/dartmouth-dltg/local_contexts_projects> developed by ArchivesSpace community member Joshua Shaw that integrates the Traditional Knowledge and Biocultural Labels in ArchivesSpace.

Date: January 18, 2023
Time: 2:00pm ? 3:00pm ET (11:00am ? 12:00pm PT)
Where: Zoom
Registration: https://lyrasis.zoom.us/webinar/register/WN_xzG-JH8GRtGd8-Xfed0xJQ

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

Webinar description:

In this webinar, Jane Anderson of New York University and Co-Director of Local Contexts<http://www.localcontexts.org/> will give an introduction to the Local Contexts initiative and newly launched Local Contexts Hub.  Local Contexts is an initiative offering digital strategies for Indigenous communities, institutions, and researchers through the TK (Traditional Knowledge) & BC (Biocultural) Labels and Notices. Local Contexts is focused on increasing Indigenous involvement in data governance through the integration of Indigenous values into data systems.

After, ArchivesSpace community member Joshua Shaw will demonstrate the Local Contexts integration plugin<https://github.com/dartmouth-dltg/local_contexts_projects> he developed that integrates Local Contexts Labels and Notices with ArchivesSpace. Feedback from the ArchivesSpace community would be appreciated to ensure that the plugin works for a variety of institutions. Feature requests, bug reports, or suggestions for changes are encouraged. Exports (EAD, EAD3, and MARCXML) are of special interest and suggestions for improvement would be very welcome.

Dr. Jane Anderson is an Associate Professor at New York University in Lenapehoking (New York) and Global Fellow in the Engelberg Center for Innovation Law and Policy in the Law School at NYU. Jane has a Ph.D. in Law from the Law School at University of New South Wales in Australia. Their work is focused on intellectual and cultural property law, Indigenous rights, and the protection of Indigenous/traditional knowledge, cultural heritage, and data.

Joshua Shaw is a web and application developer at Dartmouth Library and works with a variety of applications including ArchivesSpace, Omeka-S, Drupal, and other digital collection software. He has been working with ArchivesSpace since 2014 and is a member of the Core Committers group. Recently, Joshua has been working on ArchivesSpace plugins focused on issues related to reparative description.

This webinar is being held to further the ArchivesSpace anti-racism and inclusion initiatives identified by the community to support and amplify those that document and empower individuals, organizations and communities that work to make the world a more inclusive place. To learn more, visit our wiki at https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/1737261057/Anti-racism+and+Inclusion+Initiatives.


Jessica Dowd Crouch
Community Engagement Coordinator for ArchivesSpace
jessica.crouch at lyrasis.org<mailto:jessica.crouch at lyrasis.org>




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

From jsharp at hplct.org  Tue Dec 20 12:11:39 2022
From: jsharp at hplct.org (Sharp, Jennifer)
Date: Tue, 20 Dec 2022 17:11:39 +0000
Subject: [Archivesspace_Users_Group] analytics?
Message-ID: <MN2PR15MB27350C34BBB2A3859279B1DFDFEA9@MN2PR15MB2735.namprd15.prod.outlook.com>

Hi,

Does anyone use Google Analytics to count how many times people look at your finding aids (using the PUI)? Is this even possible?

Thanks,
Jennifer

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

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

From Joshua.D.Shaw at dartmouth.edu  Tue Dec 20 12:42:02 2022
From: Joshua.D.Shaw at dartmouth.edu (Joshua D. Shaw)
Date: Tue, 20 Dec 2022 17:42:02 +0000
Subject: [Archivesspace_Users_Group] analytics?
In-Reply-To: <MN2PR15MB27350C34BBB2A3859279B1DFDFEA9@MN2PR15MB2735.namprd15.prod.outlook.com>
References: <MN2PR15MB27350C34BBB2A3859279B1DFDFEA9@MN2PR15MB2735.namprd15.prod.outlook.com>
Message-ID: <BL0PR03MB42926C8C037B419C7C373DD2ABEA9@BL0PR03MB4292.namprd03.prod.outlook.com>

HI Jennifer

Yep. You need a plugin to do it, but its a super simple plugin. Here's what we use at Dartmouth. https://github.com/dartmouth-dltg/aspace_analytics as an example.

Joshua
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Sharp, Jennifer <jsharp at hplct.org>
Sent: Tuesday, December 20, 2022 12:11 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] analytics?


Hi,



Does anyone use Google Analytics to count how many times people look at your finding aids (using the PUI)? Is this even possible?



Thanks,

Jennifer



---

Jennifer Sharp, MSI

Archivist, Hartford History Center

Hartford Public Library

jsharp at hplct.org<mailto:jsharp at hplct.org>

o: 860.695.6332

c: 860.929.6915


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

From sara.j.szakaly at usda.gov  Tue Dec 20 12:56:19 2022
From: sara.j.szakaly at usda.gov (Szakaly, Sara J - APHIS)
Date: Tue, 20 Dec 2022 17:56:19 +0000
Subject: [Archivesspace_Users_Group] File versions not appearing in reports
Message-ID: <DM8PR09MB6152D50668B365F0FA149370B5EA9@DM8PR09MB6152.namprd09.prod.outlook.com>

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.Szakaly at usda.gov<mailto:Sara.J.Szakaly at 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221220/d4b4f4f6/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 3453 bytes
Desc: image001.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221220/d4b4f4f6/attachment.jpg>

From jsharp at hplct.org  Tue Dec 20 13:50:04 2022
From: jsharp at hplct.org (Sharp, Jennifer)
Date: Tue, 20 Dec 2022 18:50:04 +0000
Subject: [Archivesspace_Users_Group] analytics?
In-Reply-To: <BL0PR03MB42926C8C037B419C7C373DD2ABEA9@BL0PR03MB4292.namprd03.prod.outlook.com>
References: <MN2PR15MB27350C34BBB2A3859279B1DFDFEA9@MN2PR15MB2735.namprd15.prod.outlook.com>
 <BL0PR03MB42926C8C037B419C7C373DD2ABEA9@BL0PR03MB4292.namprd03.prod.outlook.com>
Message-ID: <MN2PR15MB2735672A4E75B58F190DE1A9DFEA9@MN2PR15MB2735.namprd15.prod.outlook.com>

Thanks, Joshua!

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


From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Joshua D. Shaw
Sent: Tuesday, December 20, 2022 12:42 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] analytics?

HI Jennifer

Yep. You need a plugin to do it, but its a super simple plugin. Here's what we use at Dartmouth. https://github.com/dartmouth-dltg/aspace_analytics as an example.

Joshua
________________________________
From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> on behalf of Sharp, Jennifer <jsharp at hplct.org<mailto:jsharp at hplct.org>>
Sent: Tuesday, December 20, 2022 12:11 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] analytics?


Hi,



Does anyone use Google Analytics to count how many times people look at your finding aids (using the PUI)? Is this even possible?



Thanks,

Jennifer



---

Jennifer Sharp, MSI

Archivist, Hartford History Center

Hartford Public Library

jsharp at hplct.org<mailto:jsharp at hplct.org>

o: 860.695.6332

c: 860.929.6915



CAUTION: This email originated from outside of the organization. Do not click links, open attachments, or provide sensitive information unless you recognize the sender and know the content/source is safe.

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

From lbirrell at udel.edu  Tue Dec 20 17:04:17 2022
From: lbirrell at udel.edu (Lori Birrell)
Date: Tue, 20 Dec 2022 17:04:17 -0500
Subject: [Archivesspace_Users_Group] analytics?
Message-ID: <CAGCQ86tdKbJz8B+dvYn3bsJtC8HQukg=LamXbPU1=D1vQNeP0w@mail.gmail.com>

Hi Jennifer,

Great question! I'm pretty new in my role and have started to look at our
finding aid traffic through Google analytics. I used this tool at my
previous institution to guide preservation, digitization, and enhanced
description projects.

As to the how- this blog post might get you started if there isn't a
systems admin or IT support at the History Center.

Cheers!

Lori Birrell

Director of Special Collections and Museums

Library, Museums, and Press

University of Delaware
(302) 831-8003
<https://www1.udel.edu/ocm/signature/#>
From: Sharp, Jennifer <jsharp at hplct.org>
Date: Tue, Dec 20, 2022 at 12:11 PM
Subject: [Archivesspace_Users_Group] analytics?
To: Archivesspace Users Group <
archivesspace_users_group at lyralists.lyrasis.org>


Hi,



Does anyone use Google Analytics to count how many times people look at
your finding aids (using the PUI)? Is this even possible?



Thanks,

Jennifer



---

Jennifer Sharp, MSI

Archivist, Hartford History Center

Hartford Public Library

jsharp at hplct.org

o: 860.695.6332

c: 860.929.6915
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221220/e0a88876/attachment.html>

From christine.dibella at lyrasis.org  Tue Dec 20 18:00:10 2022
From: christine.dibella at lyrasis.org (Christine Di Bella)
Date: Tue, 20 Dec 2022 23:00:10 +0000
Subject: [Archivesspace_Users_Group] File versions not appearing in
	reports
In-Reply-To: <DM8PR09MB6152D50668B365F0FA149370B5EA9@DM8PR09MB6152.namprd09.prod.outlook.com>
References: <DM8PR09MB6152D50668B365F0FA149370B5EA9@DM8PR09MB6152.namprd09.prod.outlook.com>
Message-ID: <MN2PR22MB1887C0C2790B6EF4327676B9F1EA9@MN2PR22MB1887.namprd22.prod.outlook.com>

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.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
678-235-2905

[ASpaceOrgHomeMedium]


From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Szakaly, Sara J - APHIS
Sent: Tuesday, December 20, 2022 12:56 PM
To: archivesspace_users_group at 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.Szakaly at usda.gov<mailto:Sara.J.Szakaly at 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221220/18f5567e/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 13904 bytes
Desc: image002.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221220/18f5567e/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 3453 bytes
Desc: image003.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221220/18f5567e/attachment-0001.jpg>

From sara.j.szakaly at usda.gov  Wed Dec 21 10:27:31 2022
From: sara.j.szakaly at usda.gov (Szakaly, Sara J - APHIS)
Date: Wed, 21 Dec 2022 15:27:31 +0000
Subject: [Archivesspace_Users_Group] File versions not appearing
	in	reports
In-Reply-To: <MN2PR22MB1887C0C2790B6EF4327676B9F1EA9@MN2PR22MB1887.namprd22.prod.outlook.com>
References: <DM8PR09MB6152D50668B365F0FA149370B5EA9@DM8PR09MB6152.namprd09.prod.outlook.com>
 <MN2PR22MB1887C0C2790B6EF4327676B9F1EA9@MN2PR22MB1887.namprd22.prod.outlook.com>
Message-ID: <SA0PR09MB61567E1D077EEDBB9B91B2A6B5EB9@SA0PR09MB6156.namprd09.prod.outlook.com>

Thanks Christine! That bug is the likely culprit. The exports worked as I'd expect in the test server.


[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.Szakaly at usda.gov<mailto:Sara.J.Szakaly at usda.gov>
In office: M, W, Th | Telework: Tu, F


From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Christine Di Bella
Sent: Tuesday, December 20, 2022 4:00 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] File versions not appearing in reports

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<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Farchivesspace.atlassian.net%2Fbrowse%2FANW-1526&data=05%7C01%7C%7C84df30ae4a554e365de808dae2ddfb99%7Ced5b36e701ee4ebc867ee03cfa0d4697%7C0%7C0%7C638071740282110248%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=LX3FFjCY6GEvRpeRqYN8GBZsiZ6LGsKW70ToDwc4ycQ%3D&reserved=0>. The fix is up on our test server at https://test.archivesspace.org/staff<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftest.archivesspace.org%2Fstaff&data=05%7C01%7C%7C84df30ae4a554e365de808dae2ddfb99%7Ced5b36e701ee4ebc867ee03cfa0d4697%7C0%7C0%7C638071740282266026%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=heIBhQkjtQBAo2K2rwZS9e9cKlx91jeNiw%2BSBZG05ew%3D&reserved=0>. 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.dibella at lyrasis.org<mailto:christine.dibella at lyrasis.org>
800.999.8558 x2905
678-235-2905

[ASpaceOrgHomeMedium]


From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> On Behalf Of Szakaly, Sara J - APHIS
Sent: Tuesday, December 20, 2022 12:56 PM
To: archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at 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.Szakaly at usda.gov<mailto:Sara.J.Szakaly at 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221221/69997715/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 3453 bytes
Desc: image001.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221221/69997715/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 13904 bytes
Desc: image002.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221221/69997715/attachment-0001.jpg>

From Jessica.Crouch at lyrasis.org  Fri Dec 23 10:04:33 2022
From: Jessica.Crouch at lyrasis.org (Jessica Crouch)
Date: Fri, 23 Dec 2022 15:04:33 +0000
Subject: [Archivesspace_Users_Group] =?windows-1252?q?ArchivesSpace_Update?=
	=?windows-1252?q?_=96_December_2022?=
In-Reply-To: <DM5PR22MB0540A0920E44D8A9F13475CA8BE99@DM5PR22MB0540.namprd22.prod.outlook.com>
References: <DM5PR22MB0540A0920E44D8A9F13475CA8BE99@DM5PR22MB0540.namprd22.prod.outlook.com>
Message-ID: <DM5PR22MB05407505339D965917F2FFB48BE99@DM5PR22MB0540.namprd22.prod.outlook.com>

  [cid:image001.jpg at 01D916B2.210C3C20]



Upcoming Schedule at a Glance:


January 18: Webinar: Local Contexts Initiative and Integration Plugin for ArchivesSpace<https://archivesspace.org/archives/7683>

January 31: Live Demonstration: Overview of the ArchivesSpace Application and Member Benefits <https://archivesspace.org/archives/7704>



Development
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. We are especially thankful to our members for all they do to move ArchivesSpace forward. 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 us know.

We continue to gather up development and testing work for the next release, including work on some outstanding feature requests related to digital objects. New development is always up on our test server at https://test.archivesspace.org/staff/.



Member Discussion Notes - Future Development of the ArchivesSpace Digital Objects Module

Thank you to everyone who joined the ArchivesSpace program team and fellow ArchivesSpace members on December 14 for a discussion of the ArchivesSpace Digital Objects Module.



The discussion was not recorded but notes from this discussion are available at https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/3253141506/2022-12-14+Digital+Objects+Member+Discussion.



Responses to the survey that was circulated in conjunction with the discussion, in addition to feedback from the discussion, user comments on Digital Object-specific JIRA tickets and results from user testing of new features, will factor into the consideration of next steps for activity around the Digital Objects module.  If you have any questions, please email ArchivesSpaceHome at lyrasis.org<mailto:ArchivesSpaceHome at lyrasis.org>.







Webinar Announcement: Local Contexts Initiative and Integration Plugin for ArchivesSpace

Join ArchivesSpace community members and Local Contexts<https://localcontexts.org/> project members for a webinar on January 18, 2023, at 2:00pm ET/11:00am PT on the Local Contexts initiative and the new ArchivesSpace plugin<https://github.com/dartmouth-dltg/local_contexts_projects> developed by ArchivesSpace community member Joshua Shaw that integrates the Traditional Knowledge and Biocultural Labels in ArchivesSpace.



Date: January 18, 2023

Time: 2:00pm ? 3:00pm ET (11:00am ? 12:00pm PT)

Where: Zoom

Registration: https://lyrasis.zoom.us/webinar/register/WN_xzG-JH8GRtGd8-Xfed0xJQ

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



Webinar description:

In this webinar, Jane Anderson of New York University and Co-Director of Local Contexts<http://www.localcontexts.org/> will give an introduction to the Local Contexts initiative and newly launched Local Contexts Hub.  Local Contexts is an initiative offering digital strategies for Indigenous communities, institutions, and researchers through the TK (Traditional Knowledge) & BC (Biocultural) Labels and Notices. Local Contexts is focused on increasing Indigenous involvement in data governance through the integration of Indigenous values into data systems.



After, ArchivesSpace community member Joshua Shaw will demonstrate the Local Contexts integration plugin<https://github.com/dartmouth-dltg/local_contexts_projects> he developed that integrates Local Contexts Labels and Notices with ArchivesSpace. Feedback from the ArchivesSpace community would be appreciated to ensure that the plugin works for a variety of institutions. Feature requests, bug reports, or suggestions for changes are encouraged. Exports (EAD, EAD3, and MARCXML) are of special interest and suggestions for improvement would be very welcome.



Dr. Jane Anderson is an Associate Professor at New York University in Lenapehoking (New York) and Global Fellow in the Engelberg Center for Innovation Law and Policy in the Law School at NYU. Jane has a Ph.D. in Law from the Law School at University of New South Wales in Australia. Their work is focused on intellectual and cultural property law, Indigenous rights, and the protection of Indigenous/traditional knowledge, cultural heritage, and data.



Joshua Shaw is a web and application developer at Dartmouth Library and works with a variety of applications including ArchivesSpace, Omeka-S, Drupal, and other digital collection software. He has been working with ArchivesSpace since 2014 and is a member of the Core Committers group. Recently, Joshua has been working on ArchivesSpace plugins focused on issues related to reparative description.



This webinar is being held to further the ArchivesSpace anti-racism and inclusion initiatives identified by the community to support and amplify those that document and empower individuals, organizations and communities that work to make the world a more inclusive place. To learn more, visit our wiki at https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/1737261057/Anti-racism+and+Inclusion+Initiatives.







Live Demonstration: Overview of the ArchivesSpace Application and Membership Benefits
Beginning in January 2023, ArchivesSpace will be offering regularly scheduled 60-minute demonstrations of the ArchivesSpace application open to anyone interested in ArchivesSpace. The first demonstration will be offered on January 31, 2023, at 12:00pm ET / 9:00am PT.



Date: January 31, 2023

Time: 12:00pm ? 1:00pm ET (9:00am ? 10:00am PT)

Where: Zoom

Registration: https://lyrasis.zoom.us/webinar/register/WN_BmOhIyg2TrGCPmr0DelBFg



These demos will feature an overview of the application, a brief explanation of the ArchivesSpace Staff and Public User Interfaces and an introduction to the ArchivesSpace member community<https://archivesspace.org/community/whos-using-archivesspace> and member benefits<https://archivesspace.org/community/member-benefits>.  A brief Q&A will follow the demo.  These demos are intended to assist those who are considering using the ArchivesSpace application at their organization to determine if ArchivesSpace is the right tool for their needs.



These demonstrations are not intended for those already using ArchivesSpace or those looking for ArchivesSpace training opportunities<https://archivesspace.org/using-archivesspace/trainings>. The January 31 demo will be recorded and made available with the other freely available resources on our Getting Started webpage<https://archivesspace.org/using-archivesspace/getting-started>.



For more information about this demo, ArchivesSpace, and ArchivesSpace membership, email ArchivesSpaceHome at lyrasis.org<mailto:ArchivesSpaceHome at lyrasis.org>.





ArchivesSpace Holiday Hours

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





Membership Update

We are excited to welcome our newest members to our community! Our new members since November 30th include:

  *   Des Moines University, (Des Moines, IA)
  *   Michigan Technological University, (Houghton, MI)
  *   Musical Instrument Research Catalog, (Williamsburg, VA)

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

________________________________

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


Jessica Dowd Crouch
Community Engagement Coordinator for ArchivesSpace
jessica.crouch at lyrasis.org<mailto:jessica.crouch at lyrasis.org>








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

From jodi.allisonbunnell at montana.edu  Thu Dec 29 20:42:45 2022
From: jodi.allisonbunnell at montana.edu (Allison-Bunnell, Jodi)
Date: Fri, 30 Dec 2022 01:42:45 +0000
Subject: [Archivesspace_Users_Group] [EXTERNAL] Re: Managing
	media	instances	in	collection
In-Reply-To: <DM8PR09MB7128A32B30FD21218AE59776C8749@DM8PR09MB7128.namprd09.prod.outlook.com>
References: <2747812E-672E-41B8-AEB3-8218B54B8935@montana.edu>
 <DM8PR09MB71283FC2AE2357B6800B0D50C8749@DM8PR09MB7128.namprd09.prod.outlook.com>
 <8343BC04-FFB9-442B-839B-52E73A47FFE7@montana.edu>
 <SJ0PR05MB753295458D57DD4E8E5B78ADE6749@SJ0PR05MB7532.namprd05.prod.outlook.com>
 <DM8PR09MB7128A32B30FD21218AE59776C8749@DM8PR09MB7128.namprd09.prod.outlook.com>
Message-ID: <D1933182-41BD-489E-8067-BD83F6F69BC4@montana.edu>

The end of the calendar year is apparently when I catch up with finally circling back to colleagues who have generously shared their expertise.

Based on the responses from John Rees, Noah Huffman, and Maureen Callahan, we?ve settled on an approach that adds media as instances. We use a list of instance types derived from the Art and Architecture Thesaurus with just a couple of exceptions. A practicum student (Sarah Huth) has made amazing progress on getting these recorded (thanks to Heather Mulliner for supervising that practicum), and we are growing ever closer to having a much better handle on all the media lurking on our shelves.

I?ve attached our documentation for anyone who is interested. Thanks again to you all for your always generous advice!

Best, Jodi

Jodi Allison-Bunnell
(pronouns: She, her)
Head of Archives and Special Collections, Senior Archivist
Montana State University Library
jodi.allisonbunnell at montana.edu<mailto:jodi.allisonbunnell at montana.edu> ?
406-994-5297





On Dec 13, 2021, at 2:24 PM, Rees, John (NIH/NLM) [E] <reesj at mail.nlm.nih.gov<mailto:reesj at mail.nlm.nih.gov>> wrote:


Jodi,



About our history/sources, +1 to what Noah said. We apply/gather these archival object values at accession time, as we create accession box/folder lists so these terms persist there rather than deleting them. We later got a bit smarter and decided to start making media counts for our separate shelflist database, so many of our AV terms are dbase fields we crafted for a retrospective project. And they are colloquially used across our dept which includes a separate AV unit. We now grow the term list/dbase fields as necessary.



I?d like to think some of the terms came from RDA media carrier lists. I don?t recall anymore, but I think a lot of this work was done around the same time RDA first appeared and sounds like something I would have done back then while sussing out RDA implementations with Tech Services. And I probably did some internet finding aid searching looking for comfort in the approaches others have tried.



John





From: Noah Huffman <noah.huffman at duke.edu<mailto:noah.huffman at duke.edu>>
Sent: Monday, December 13, 2021 12:22 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: [EXTERNAL] Re: [Archivesspace_Users_Group] Managing media instances in collection



CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and are confident the content is safe.



Hi Jodi,



We also use a more-or-less locally-developed vocabulary / code list to identify format types. We have a short list of controlled container type values for broad categories of formats (boxes, videocassettes, film-reel, etc.), but more granular format information is communicated using format codes that we store as part of the item?s identifier in the container identifier field. So, in both cases we are storing the format information at the instance/container level and not necessarily at the archival object level. This has been helpful for reporting and for maintaining consistency across systems (many of these physical items are also represented as item records in our ILS).



Here?s a link to a Google sheet where we define the formats and corresponding format codes: https://docs.google.com/spreadsheets/d/1NfbeugxEOuGI1YQcudWcQoMUU6UyhijZtirFPL0NcuE/edit?usp=sharing<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.google.com%2Fspreadsheets%2Fd%2F1NfbeugxEOuGI1YQcudWcQoMUU6UyhijZtirFPL0NcuE%2Fedit%3Fusp%3Dsharing&data=04%7C01%7Cjodi.allisonbunnell%40montana.edu%7C081af839de444c8b322c08d9be7f024e%7C324aa97a03a644fc91e43846fbced113%7C0%7C0%7C637750275589403440%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=1OGdUkcpqf6iEv9sWL7Dxd7GAQlaWwZeGx65A1g3Uzo%3D&reserved=0>



Here?s an example finding aid where many of the item identifiers include format codes for various video formats (e.g. : RL11360-UMATIC-003): https://archives.lib.duke.edu/catalog/jwtdetroitav_aspace_536753340d54f53d8b3db51d8598c5d9<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Farchives.lib.duke.edu%2Fcatalog%2Fjwtdetroitav_aspace_536753340d54f53d8b3db51d8598c5d9&data=04%7C01%7Cjodi.allisonbunnell%40montana.edu%7C081af839de444c8b322c08d9be7f024e%7C324aa97a03a644fc91e43846fbced113%7C0%7C0%7C637750275589403440%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=UVpAOEnu03Sh6nBm%2F2AJAgFeSyBkWpLbDPk4LkXlpTw%3D&reserved=0>



Again, this is locally-developed and not based on any external standard or vocabulary, but perhaps useful for reference.



-Noah



================

Noah Huffman

Archivist for Metadata, Systems, and Digital Records

David M. Rubenstein Rare Book & Manuscript Library

Duke University | 919-660-5982

http://library.duke.edu/rubenstein/<https://nam10.safelinks.protection.outlook.com/?url=http%3A%2F%2Flibrary.duke.edu%2Frubenstein%2F&data=04%7C01%7Cjodi.allisonbunnell%40montana.edu%7C081af839de444c8b322c08d9be7f024e%7C324aa97a03a644fc91e43846fbced113%7C0%7C0%7C637750275589403440%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=4BuVpFXFdciEbEDwjv07mWZ4M%2FwubMDQaKkYd9OSJ0w%3D&reserved=0>

Pronouns: he / him / his





From: archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org> <archivesspace_users_group-bounces at lyralists.lyrasis.org<mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org>> On Behalf Of Allison-Bunnell, Jodi
Sent: Monday, December 13, 2021 11:50 AM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Managing media instances in collection



Hello John:

Thank you, this is exactly the approach that I had in mind! I appreciate your reply very much.



So far you and one other institution have shared their internally developed CV lists?I?m hoping to find something more standardized, or drawn from a particular standard. Can you tell me anything more about what source(s) you used for this list?



Best, Jodi



Jodi Allison-Bunnell
(pronouns: She, her)
Head of Archives and Special Collections, University Archivist
Montana State University Library
jodi.allisonbunnell at montana.edu<mailto:jodi.allisonbunnell at montana.edu> ?
406-994-5297











On Dec 13, 2021, at 6:39 AM, Rees, John (NIH/NLM) [E] <reesj at mail.nlm.nih.gov<mailto:reesj at mail.nlm.nih.gov>> wrote:



Hi Jodi,



We haven?t leveraged any national/international standards, but historically we use internally developed standardized language within folder title text to identify/highlight instances of non-paper formats within folders. I use these occasionally for kludgie searching exercises. We?ve started to better label these with ASpace container instance controlled values terms. We do similar for free-standing lose items on the shelf like film cans, artifacts. We?ve noticed a roughly similar pattern in use at Duke Rubenstein.



           *   3.5 computer disk
           *   5.25 computer disk
           *   8 computer disk
           *   35mm slides
           *   audio microcassette
           *   audio tape reel
           *   audiocassette
           *   Beta videocassette
           *   CD-ROM
           *   CD-RW
           *   computer tape
           *   DVD
           *   glass slides
           *   microscope slides
           *   negatives
           *   photographs
           *   U-Matic videocassette
           *   VHS videocassette
           *   video tape reel



Example folder title: "Arteriosclerosis and coronary disease" [audiocassette], Family Practice v.23, no.4, Nov. 24, 1975

In Aspace:

<image001.png>



<image002.png>



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









From: Allison-Bunnell, Jodi <jodi.allisonbunnell at montana.edu<mailto:jodi.allisonbunnell at montana.edu>>
Sent: Tuesday, December 7, 2021 8:09 PM
To: archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>
Subject: [Archivesspace_Users_Group] Managing media instances in collection



A question of practice for your collected wisdom.



We would like to be able to pull a report for all media in our collections?audio, video, film, and digital (computer) media. I do not have access to custom reporting and would need to generate this from a standard report. We need to be able to audit by format (e.g. how many reel to reel tapes do we have? How many obsolete floppy discs do we have?) in order to identify vulnerable media and plan migrations.



Since the media is an instantiation of a described object, I?d like to be able to do this from a standard vocabulary in the instance/container type. It looks like PBcore would be a possible choice for the audio, video, and film, but I need a concise list of computer media. Neither DCMI formats nor MIME types fit the bill.



We do not have the resources to take an elaborate approach to this, and I (always!) want to use standardized practices rather than creating local ones whenever possible.



Does anyone have a practice that would fit the bill?



Best, Jodi



Jodi Allison-Bunnell
(pronouns: She, her)
Head of Archives and Special Collections, University Archivist
Montana State University Library
jodi.allisonbunnell at montana.edu<mailto:jodi.allisonbunnell at montana.edu> ?
406-994-5297











_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.com%2Fv3%2F__http%3A%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_group__%3B!!OToaGQ!-3VfaBl_UQMmdQPaQ-oIVpwedhJf3UT2ayq5YgezWSUA8pJMvVgdkQEPHmf1F1lf5YD4%24&data=04%7C01%7Cjodi.allisonbunnell%40montana.edu%7C081af839de444c8b322c08d9be7f024e%7C324aa97a03a644fc91e43846fbced113%7C0%7C0%7C637750275589403440%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=DQElFrkn6fVFGjGNUlxpn8RpM7FuE3aUHvSrs1qk598%3D&reserved=0>



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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221230/022180b8/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Digital_and_Media_in_AS_20220323.pdf
Type: application/pdf
Size: 168711 bytes
Desc: Digital_and_Media_in_AS_20220323.pdf
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20221230/022180b8/attachment.pdf>