[Archivesspace_Users_Group] ArchivesSpace Update - April 2022

2022-04-28 Thread Jessica Crouch 
   [cid:image001.jpg@01D7E600.7FF2B540]


Upcoming Schedule at a Glance:


Every Friday this month: Take a Break with ArchivesSpace 
 (no break on May 6)

May 5-6: Visit the ArchivesSpace booth at the Midwest Archives 
Conference

May 20: Apply now for the ArchivesSpace Member Match program (due date extended 
to May 20)

May 20-21: Visit the ArchivesSpace booth at the Society of California 
Archivists Annual Conference

May 24: Webinar: Using ArchivesSpace to create EAC-CPF 
records (90 minutes)

May 27: Governance Board community 
session
 (60 minutes)


Development


We are gathering up and testing development work in anticipation of the next 
release. New development is always up on our test server at 
https://test.archivesspace.org/staff/. We'll have information to share about 
the timing for the release in a few weeks.


Final Call: Nominate Yourself or Others for the User Advisory Council or 
Technical Advisory Council


Want to get more involved in ArchivesSpace? The deadline to nominate new 
members for our User Advisory Council (UAC) or Technical Advisory Council (TAC) 
is April 29 at 9:00 p.m. EDT. We have up to 6 openings on each Council for 
terms that begin July 1, 2022. Nominate yourself or others for this fun and 
valuable service to the archives community. The full calls are at 
archivesspace.org/archives/7354 (UAC) and 
archivesspace.org/archives/7352 (TAC).


The form to nominate people is at https://forms.gle/DkDnb2NLRBgy3ecJA. If you 
would like to nominate someone for more than one group, or nominate multiple 
people for the same group, we ask that you complete one nomination form per 
person per group. The Nominating Committee will review all nominations and 
recommend appointments to the Governance Board for approval. We would expect to 
notify all candidates no later than early June.


Discussion Announcement: Governance Board community session


The ArchivesSpace Governance Board invites you to an open community engagement 
session on Friday, May 27, 2022, 11:00am-12:00pm ET (find your local 
time).
 In this session, the ArchivesSpace Governance Board will provide an overview 
of the ArchivesSpace governance model, highlight recent initiatives, and give 
participants an opportunity to interact with the board and their 
representatives.



This is a member-only event. The board welcomes all members to join us with any 
questions you might have about ArchivesSpace sustainability, governance, or 
opportunities for strengthening the community.



Register to join at 
https://lyrasis.zoom.us/meeting/register/tZUkcOCqpjMtGNYQZrJ8ZUpY5Qm8Bv9zrtka




Webinar Announcement: Using ArchivesSpace to create EAC-CPF records (90 minutes)

The next ArchivesSpace webinar will be a 90-minute learning opportunity on May 
24th at 2:00pm ET/11:00am PT led by Regine Heberlein, Library IT Data Analyst 
at Princeton University, and Christine Di Bella, ArchivesSpace Program Manager, 
demonstrating how to create valid EAC-CPF records using ArchivesSpace and 
offering some tips and tricks for making the process easier within your 
repository.



Originally scheduled for February 9th, this 90 minute learning opportunity has 
been postponed to May 24, 2022, at 2:00pm ET/11:00am PT.  If you’ve already 
registered for this webinar, your registration has been transferred to this new 
date.  If you need to cancel your registration, you can do so using the 
connection information provided via Zoom.



Date: May 24, 2022
Time: 2:00pm – 3:30pm ET (11:00am – 12:30pm PT)
Where: Zoom

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



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



Webinar description:
The recent expansion of the agents module in ArchivesSpace greatly expanded the 
application’s support for the metadata standard Encoded Archival Context – 
Corporate Bodies, Persons, and Families (EAC-CPF) and the potential for 
exchanging these records with other systems, including Social Networks and 
Archival Context (SNAC). Taking full advantage of this potential requires some 
work on the record creator’s part as ArchivesSpace’s requirements for creating 
agent records remain minimal.

This learning opportunity will demonstrate how to create valid EAC-CPF records 
using ArchivesSpace and offer some tips and tricks for making the process 
easier within your repository.

An open discussion and Q will follow.


This learning opportunity introduces EAC-CPF in the context of ArchivesSpace 
but is not intended to be a full overview of

Re: [Archivesspace_Users_Group] Subjects: Metadata Rights Declarations

2022-04-28 Thread Dan Michelson 
Hi Jim,

We haven't started using the Metadata Rights Declaration subrecord yet
(still relying on a blanket statement in the PUI footer), so I don't have
an example from NACO (and their license statement isn't as easy to find on
their website as the AAT one).  DACS 13.11

gives examples from SNAC and VIAF that could be used as a model.

All the best,

Dan

On Thu, Apr 28, 2022 at 1:55 PM James E. Cross  wrote:

> Dan,
>
>
>
> Just curious. How do you compose a rights declaration for a NACO name
> authority? Thanks to both you and Kate for answering the question!
>
>
>
> Jim
>
>
>
>
>
> *From:* archivesspace_users_group-boun...@lyralists.lyrasis.org <
> archivesspace_users_group-boun...@lyralists.lyrasis.org> *On Behalf Of *Dan
> Michelson
> *Sent:* Thursday, April 28, 2022 1:19 PM
> *To:* Archivesspace Users Group <
> archivesspace_users_group@lyralists.lyrasis.org>
> *Subject:* Re: [Archivesspace_Users_Group] Subjects: Metadata Rights
> Declarations
>
>
>
> Hi Kate,
>
>
>
> First a disclaimer: I'm neither a lawyer nor a copyright expert.
>
>
>
> I would think that AAT subject records would ideally link to their licensing
> statement
> .
> It's of less importance than making sure an institution's own description
> has clear rights declarations, but it seems like it could be helpful for
> systems outside the GLAM world which may not inherently know that AAT data
> can be reproduced.
>
>
>
> As a side note, I also want to be clear that while *DACS * requires
> metadata rights to be declared, it does *not *have to be done using the
> ArchivesSpace Metadata Rights Declaration subrecord.  That's just a good
> way to make it machine-actionable in a way that a statement on the PUI
> footer (which complies with the *DACS *requirement) is not.
>
>
>
> All the best,
>
>
>
> Dan
>
>
>
> On Thu, Apr 28, 2022 at 12:50 PM Bowers, Kate A. 
> wrote:
>
> If your subjects and agents are coming from thesauri (not initiated in
> your own repository) I’m not sure what rights statements about this
> metadata would be applicable. For example, if you are using AAT or any of
> the Getty thesauri: https://www.getty.edu/legal/copyright.html
> 
>
>
>
> *From:* archivesspace_users_group-boun...@lyralists.lyrasis.org <
> archivesspace_users_group-boun...@lyralists.lyrasis.org> *On Behalf Of *Dan
> Michelson
> *Sent:* Thursday, April 28, 2022 12:20 PM
> *To:* Archivesspace Users Group <
> archivesspace_users_group@lyralists.lyrasis.org>
> *Subject:* Re: [Archivesspace_Users_Group] Subjects: Metadata Rights
> Declarations
>
>
>
> Hi Jim,
>
>
>
> The short answer is no.
>
>
>
> The longer answer is that the only reason this is the case is that "DACS
> does not provide rules for the construction and maintenance of subject
> authorities
> ."
> If it did, TS-DACS would have made the rights statement a requirement for
> subject authorities when it was introduced.  In my view, there is no
> downside to including such declarations in subject authority records.
>
>
>
> All the best,
>
>
>
> Dan Michelson (formerly TS-DACS co-chair)
>
>
>
> On Thu, Apr 28, 2022 at 11:07 AM James E. Cross 
> wrote:
>
> Are metadata rights declarations a required element for subject authority
> records under *DACS* 13.11 as they are for name authority records?
> Unfortunately *DACS* only discusses them in relation to names. Thank you.
>
>
>
> Sincerely,
>
>
>
> Jim Cross
>
> Manuscripts Archivist
>
>
>
>
>
> *James Edward Cross, C.A.* CLEMSON UNIVERSITY
>
> Manuscripts Archivist
>
> Special Collections and Archives
>
> Clemson University Libraries
>
> Box 343001
>
> Clemson, SC  29634-3001
>
> Phone: (864) 656-5182
>
> Website: http://library.clemson.edu/depts/specialcollections/
> 
>
> Pronouns: he/him/his
>
> Traditional Cherokee Lands | Site of Fort Hill Plantation
>
> *Please do not feel obligated to respond to this message outside of your
> normal working hours.*
>
>
>
>

Re: [Archivesspace_Users_Group] Subjects: Metadata Rights Declarations

2022-04-28 Thread James E. Cross 
Dan,

Just curious. How do you compose a rights declaration for a NACO name 
authority? Thanks to both you and Kate for answering the question!

Jim


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Dan 
Michelson
Sent: Thursday, April 28, 2022 1:19 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Subjects: Metadata Rights Declarations

Hi Kate,

First a disclaimer: I'm neither a lawyer nor a copyright expert.

I would think that AAT subject records would ideally link to their licensing 
statement.
  It's of less importance than making sure an institution's own description has 
clear rights declarations, but it seems like it could be helpful for systems 
outside the GLAM world which may not inherently know that AAT data can be 
reproduced.

As a side note, I also want to be clear that while DACS requires metadata 
rights to be declared, it does not have to be done using the ArchivesSpace 
Metadata Rights Declaration subrecord.  That's just a good way to make it 
machine-actionable in a way that a statement on the PUI footer (which complies 
with the DACS requirement) is not.

All the best,

Dan

On Thu, Apr 28, 2022 at 12:50 PM Bowers, Kate A. 
mailto:kate_bow...@harvard.edu>> wrote:
If your subjects and agents are coming from thesauri (not initiated in your own 
repository) I’m not sure what rights statements about this metadata would be 
applicable. For example, if you are using AAT or any of the Getty thesauri: 
https://www.getty.edu/legal/copyright.html

From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org
 
mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 On Behalf Of Dan Michelson
Sent: Thursday, April 28, 2022 12:20 PM
To: Archivesspace Users Group 
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Subjects: Metadata Rights Declarations

Hi Jim,

The short answer is no.

The longer answer is that the only reason this is the case is that "DACS does 
not provide rules for the construction and maintenance of subject 
authorities."
  If it did, TS-DACS would have made the rights statement a requirement for 
subject authorities when it was introduced.  In my view, there is no downside 
to including such declarations in subject authority records.

All the best,

Dan Michelson (formerly TS-DACS co-chair)

On Thu, Apr 28, 2022 at 11:07 AM James E. Cross 
mailto:jcr...@clemson.edu>> wrote:
Are metadata rights declarations a required element for subject authority 
records under DACS 13.11 as they are for name authority records? Unfortunately 
DACS only discusses them in relation to names. Thank you.

Sincerely,

Jim Cross
Manuscripts Archivist


James Edward Cross, C.A. CLEMSON UNIVERSITY
Manuscripts Archivist
Special Collections and Archives
Clemson University Libraries
Box 343001
Clemson, SC  29634-3001
Phone: (864) 656-5182
Website: 
http://library.clemson.edu/depts/specialcollections/
Pronouns: he/him/his
Traditional Cherokee Lands | Site of Fort Hill Plantation
Please do not feel obligated to respond to this message outside of your normal 
working hours.

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


--
Dan Michelson
Collections Archivist
Smith College Special Collections

For current library access and services details, see Library Services During

Re: [Archivesspace_Users_Group] Subjects: Metadata Rights Declarations

2022-04-28 Thread Dan Michelson 
Hi Kate,

First a disclaimer: I'm neither a lawyer nor a copyright expert.

I would think that AAT subject records would ideally link to their licensing
statement
.
It's of less importance than making sure an institution's own description
has clear rights declarations, but it seems like it could be helpful for
systems outside the GLAM world which may not inherently know that AAT data
can be reproduced.

As a side note, I also want to be clear that while *DACS *requires metadata
rights to be declared, it does *not *have to be done using the
ArchivesSpace Metadata Rights Declaration subrecord.  That's just a good
way to make it machine-actionable in a way that a statement on the PUI
footer (which complies with the *DACS *requirement) is not.

All the best,

Dan

On Thu, Apr 28, 2022 at 12:50 PM Bowers, Kate A. 
wrote:

> If your subjects and agents are coming from thesauri (not initiated in
> your own repository) I’m not sure what rights statements about this
> metadata would be applicable. For example, if you are using AAT or any of
> the Getty thesauri: https://www.getty.edu/legal/copyright.html
>
>
>
> *From:* archivesspace_users_group-boun...@lyralists.lyrasis.org <
> archivesspace_users_group-boun...@lyralists.lyrasis.org> *On Behalf Of *Dan
> Michelson
> *Sent:* Thursday, April 28, 2022 12:20 PM
> *To:* Archivesspace Users Group <
> archivesspace_users_group@lyralists.lyrasis.org>
> *Subject:* Re: [Archivesspace_Users_Group] Subjects: Metadata Rights
> Declarations
>
>
>
> Hi Jim,
>
>
>
> The short answer is no.
>
>
>
> The longer answer is that the only reason this is the case is that "DACS
> does not provide rules for the construction and maintenance of subject
> authorities
> ."
> If it did, TS-DACS would have made the rights statement a requirement for
> subject authorities when it was introduced.  In my view, there is no
> downside to including such declarations in subject authority records.
>
>
>
> All the best,
>
>
>
> Dan Michelson (formerly TS-DACS co-chair)
>
>
>
> On Thu, Apr 28, 2022 at 11:07 AM James E. Cross 
> wrote:
>
> Are metadata rights declarations a required element for subject authority
> records under *DACS* 13.11 as they are for name authority records?
> Unfortunately *DACS* only discusses them in relation to names. Thank you.
>
>
>
> Sincerely,
>
>
>
> Jim Cross
>
> Manuscripts Archivist
>
>
>
>
>
> *James Edward Cross, C.A.* CLEMSON UNIVERSITY
>
> Manuscripts Archivist
>
> Special Collections and Archives
>
> Clemson University Libraries
>
> Box 343001
>
> Clemson, SC  29634-3001
>
> Phone: (864) 656-5182
>
> Website: http://library.clemson.edu/depts/specialcollections/
> 
>
> Pronouns: he/him/his
>
> Traditional Cherokee Lands | Site of Fort Hill Plantation
>
> *Please do not feel obligated to respond to this message outside of your
> normal working hours.*
>
>
>
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
> 
>
>
>
> --
>
> Dan Michelson
>
> Collections Archivist
>
> Smith College Special Collections
>
>
>
> For current library access and services details, see Library Services
> During COVID-19
> 
> .
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>


-- 
Dan Michelson
Collections Archivist
Smith College Special Collections

For current library access and services details, see Library Services
During COVID-19

Re: [Archivesspace_Users_Group] Subjects: Metadata Rights Declarations

2022-04-28 Thread Bowers, Kate A. 
If your subjects and agents are coming from thesauri (not initiated in your own 
repository) I’m not sure what rights statements about this metadata would be 
applicable. For example, if you are using AAT or any of the Getty thesauri: 
https://www.getty.edu/legal/copyright.html

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Dan 
Michelson
Sent: Thursday, April 28, 2022 12:20 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Subjects: Metadata Rights Declarations

Hi Jim,

The short answer is no.

The longer answer is that the only reason this is the case is that "DACS does 
not provide rules for the construction and maintenance of subject 
authorities."
  If it did, TS-DACS would have made the rights statement a requirement for 
subject authorities when it was introduced.  In my view, there is no downside 
to including such declarations in subject authority records.

All the best,

Dan Michelson (formerly TS-DACS co-chair)

On Thu, Apr 28, 2022 at 11:07 AM James E. Cross 
mailto:jcr...@clemson.edu>> wrote:
Are metadata rights declarations a required element for subject authority 
records under DACS 13.11 as they are for name authority records? Unfortunately 
DACS only discusses them in relation to names. Thank you.

Sincerely,

Jim Cross
Manuscripts Archivist


James Edward Cross, C.A. CLEMSON UNIVERSITY
Manuscripts Archivist
Special Collections and Archives
Clemson University Libraries
Box 343001
Clemson, SC  29634-3001
Phone: (864) 656-5182
Website: 
http://library.clemson.edu/depts/specialcollections/
Pronouns: he/him/his
Traditional Cherokee Lands | Site of Fort Hill Plantation
Please do not feel obligated to respond to this message outside of your normal 
working hours.

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


--
Dan Michelson
Collections Archivist
Smith College Special Collections

For current library access and services details, see Library Services During 
COVID-19.
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] Request Button and LibAnswers - Duplicates

2022-04-28 Thread Hoffner, Bailey E. 
Hello,

We’ve been using the request button in AS for almost a year. We also utilize 
LibAnswers (Springshare) for request management, so when a user uses the button 
in AS an email is sent to the appropriate repositories account and creates a 
ticket in LibAnswers.

We have found that we end up getting quite a few duplicate (even triplicate) 
requests. Has anyone else dealt with this? My current assumption is that users 
are submitting multiple tickets because they miss the light blue message at the 
top of the user interface letting them know they’ve successfully submitted, and 
then they re-submit, but I’m not sure.

Thanks for any feedback!

-Bailey


Bailey Hoffner, MLIS
Pronouns: she/her or they/them
Metadata and Collections Management Archivist
University of Oklahoma Libraries
bail...@ou.edu
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Subjects: Metadata Rights Declarations

2022-04-28 Thread Dan Michelson 
Hi Jim,

The short answer is no.

The longer answer is that the only reason this is the case is that "DACS
does not provide rules for the construction and maintenance of subject
authorities
."
If it did, TS-DACS would have made the rights statement a requirement for
subject authorities when it was introduced.  In my view, there is no
downside to including such declarations in subject authority records.

All the best,

Dan Michelson (formerly TS-DACS co-chair)

On Thu, Apr 28, 2022 at 11:07 AM James E. Cross  wrote:

> Are metadata rights declarations a required element for subject authority
> records under *DACS* 13.11 as they are for name authority records?
> Unfortunately *DACS* only discusses them in relation to names. Thank you.
>
>
>
> Sincerely,
>
>
>
> Jim Cross
>
> Manuscripts Archivist
>
>
>
>
>
> *James Edward Cross, C.A.* CLEMSON UNIVERSITY
>
> Manuscripts Archivist
>
> Special Collections and Archives
>
> Clemson University Libraries
>
> Box 343001
>
> Clemson, SC  29634-3001
>
> Phone: (864) 656-5182
>
> Website: http://library.clemson.edu/depts/specialcollections/
>
> Pronouns: he/him/his
>
> Traditional Cherokee Lands | Site of Fort Hill Plantation
>
> *Please do not feel obligated to respond to this message outside of your
> normal working hours.*
>
>
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>


-- 
Dan Michelson
Collections Archivist
Smith College Special Collections

For current library access and services details, see Library Services
During COVID-19
.
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] Subjects: Metadata Rights Declarations

2022-04-28 Thread James E. Cross 
Are metadata rights declarations a required element for subject authority 
records under DACS 13.11 as they are for name authority records? Unfortunately 
DACS only discusses them in relation to names. Thank you.

Sincerely,

Jim Cross
Manuscripts Archivist


James Edward Cross, C.A. CLEMSON UNIVERSITY
Manuscripts Archivist
Special Collections and Archives
Clemson University Libraries
Box 343001
Clemson, SC  29634-3001
Phone: (864) 656-5182
Website: http://library.clemson.edu/depts/specialcollections/
Pronouns: he/him/his
Traditional Cherokee Lands | Site of Fort Hill Plantation
Please do not feel obligated to respond to this message outside of your normal 
working hours.

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

[Archivesspace_Users_Group] Take a Break with ArchivesSpace on Friday

2022-04-28 Thread Jessica Crouch 
ArchivesSpace users,



Whether you’ve continued to work from home, have returned to the office, or 
find yourself stuck somewhere in the middle, we could all use a break.  In that 
spirit, ArchivesSpace will be reinstating our popular casual zoom open calls on 
Fridays. With a welcoming and robust member community all over the world, 
ArchivesSpace can offer camaraderie and relaxation, no matter the current state 
of the world.


Each Friday we will have casual open calls via zoom at 12pm ET. We won’t be 
developing agendas or presentations for these calls. We just want to provide an 
opportunity to connect, chat and recharge. Use this as a time to get help or 
talk about ArchivesSpace (or anything else) in an informal setting or just have 
a beverage with other ArchivesSpace users during this stressful time.


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


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


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


Please email 
archivesspaceh...@lyrasis.org with any 
questions.
We hope to see you tomorrow!

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




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

Re: [Archivesspace_Users_Group] PUI Ordering and Sorting Issue

2022-04-28 Thread Andrew Morrison 
I forgot to mention that you probably have to re-index after changing 
schema.xml and reloading the core.


Andrew.


On 28/04/2022 10:51, 松山 ひとみ wrote:


Thanks again Andrew!

We’ll try applying what you gave to our current AS.

Hitomi

*From:*archivesspace_users_group-boun...@lyralists.lyrasis.org 
 *On Behalf 
Of *Andrew Morrison

*Sent:* Thursday, April 28, 2022 6:09 PM
*To:* archivesspace_users_group@lyralists.lyrasis.org
*Subject:* Re: [Archivesspace_Users_Group] PUI Ordering and Sorting Issue

If you're using the schema.xml that came with ArchivesSpace 3.0.1 in 
your external Solr 8.11, then it will still define the "sort_icu" 
fieldType as an instance of the solr.TextField class. If you look 
below that, there is a commented-out alternative fieldType definition 
which is an instance of solr.ICUCollationField. ArchivesSpace 3.2.0 
has changed to that (because it no longer has to support the 
previously-built-in Solr 4.10) but you don't need to upgrade to it, 
you can just edit your schema.xml, then reload the Solr core. See the 
link in my previous email for help on how to set that up to be 
optimized for Japanese characters.


Andrew.

On 28/04/2022 09:44, 松山 ひとみwrote:

Thank you Andrew!

Our IT says we’ve already been using an external Solr 8.11 with
ArchivesSpace 3.0.1, not the one built-in.

We’re thinking of upgrading our AS to 3.2.0. Do you think we will
get a better result?

Hitomi

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


*On Behalf Of *Andrew Morrison
*Sent:* Thursday, April 28, 2022 4:47 PM
*To:* archivesspace_users_group@lyralists.lyrasis.org
*Subject:* Re: [Archivesspace_Users_Group] PUI Ordering and
Sorting Issue

Are you using the built-in Solr search engine that comes with
ArchivesSpace 3.0.1? If so, your sorting problems could be because
it uses a very old version, because newer ones aren't compatible
with the method of embedding it in a bigger application. But there
is the option to configure ArchivesSpace to use an external Solr
service:

https://archivesspace.github.io/tech-docs/provisioning/solr.html

That allows you to run a more up-to-date version, which would
enable use of the solr.ICUCollationField class for sort fields.
That can be adjusted to sort different languages according to
their own sorting rules, as described here:

https://solr.apache.org/guide/8_11/language-analysis.html#unicode-collation

ArchivesSpace 3.2.0 removes the built-in Solr, so running an
external Solr service will be necessary if you upgrade in the future.

As for adding the option to sort on identifiers, I don't think
there is a configuration option or simple interface for adding
them. But it would probably be possible to develop a plug-in to
override certain Ruby methods in the core code to do it.

Andrew.

On 27/04/2022 11:04, 松山 ひとみwrote:

Hello all,

We’ve been stuck in the “ordering and sorting” issue in
[~/repositories/resources]. Our AS is version 3.0.1.

Presumably, because we use Japanese Character, our resource
list cannot be displayed in a right, alphabetical order when
sorted by Title.

Could we add Identifier to the category of sorting;
Relevance/Title(Asc/Desc)/Year(Asc/Desc), as alternative?

We’d very much appreciate you helping solve our issue!

All the best,

Hitomi Matsuyama, Audiovisual Archivist

Nakanoshima Museum of Art, Osaka

4-3-1 Nakanoshima, Kita-ku

Osaka 530-0005 JAPAN

tel. +81 (0)6 64 79 05 58

email. matsuyam...@nakka-art.jp 




___

Archivesspace_Users_Group mailing list

Archivesspace_Users_Group@lyralists.lyrasis.org

http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group



___

Archivesspace_Users_Group mailing list

Archivesspace_Users_Group@lyralists.lyrasis.org

http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


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

Re: [Archivesspace_Users_Group] PUI Ordering and Sorting Issue

2022-04-28 Thread 松山　ひとみ 
Thanks again Andrew!
We’ll try applying what you gave to our current AS.

Hitomi

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Andrew 
Morrison
Sent: Thursday, April 28, 2022 6:09 PM
To: archivesspace_users_group@lyralists.lyrasis.org
Subject: Re: [Archivesspace_Users_Group] PUI Ordering and Sorting Issue


If you're using the schema.xml that came with ArchivesSpace 3.0.1 in your 
external Solr 8.11, then it will still define the "sort_icu" fieldType as an 
instance of the solr.TextField class. If you look below that, there is a 
commented-out alternative fieldType definition which is an instance of 
solr.ICUCollationField. ArchivesSpace 3.2.0 has changed to that (because it no 
longer has to support the previously-built-in Solr 4.10) but you don't need to 
upgrade to it, you can just edit your schema.xml, then reload the Solr core. 
See the link in my previous email for help on how to set that up to be 
optimized for Japanese characters.

Andrew.


On 28/04/2022 09:44, 松山 ひとみ wrote:
Thank you Andrew!

Our IT says we’ve already been using an external Solr 8.11 with ArchivesSpace 
3.0.1, not the one built-in.
We’re thinking of upgrading our AS to 3.2.0. Do you think we will get a better 
result?

Hitomi

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

 On Behalf Of Andrew Morrison
Sent: Thursday, April 28, 2022 4:47 PM
To: 
archivesspace_users_group@lyralists.lyrasis.org
Subject: Re: [Archivesspace_Users_Group] PUI Ordering and Sorting Issue


Are you using the built-in Solr search engine that comes with ArchivesSpace 
3.0.1? If so, your sorting problems could be because it uses a very old 
version, because newer ones aren't compatible with the method of embedding it 
in a bigger application. But there is the option to configure ArchivesSpace to 
use an external Solr service:

https://archivesspace.github.io/tech-docs/provisioning/solr.html

That allows you to run a more up-to-date version, which would enable use of the 
solr.ICUCollationField class for sort fields. That can be adjusted to sort 
different languages according to their own sorting rules, as described here:

https://solr.apache.org/guide/8_11/language-analysis.html#unicode-collation

ArchivesSpace 3.2.0 removes the built-in Solr, so running an external Solr 
service will be necessary if you upgrade in the future.

As for adding the option to sort on identifiers, I don't think there is a 
configuration option or simple interface for adding them. But it would probably 
be possible to develop a plug-in to override certain Ruby methods in the core 
code to do it.

Andrew.


On 27/04/2022 11:04, 松山 ひとみ wrote:
Hello all,

We’ve been stuck in the “ordering and sorting” issue in 
[~/repositories/resources]. Our AS is version 3.0.1.
Presumably, because we use Japanese Character, our resource list cannot be 
displayed in a right, alphabetical order when sorted by Title.

Could we add Identifier to the category of sorting; 
Relevance/Title(Asc/Desc)/Year(Asc/Desc), as alternative?
We’d very much appreciate you helping solve our issue!


All the best,
Hitomi Matsuyama, Audiovisual Archivist

Nakanoshima Museum of Art, Osaka
4-3-1 Nakanoshima, Kita-ku
Osaka 530-0005 JAPAN
tel. +81 (0)6 64 79 05 58
email. matsuyam...@nakka-art.jp






___

Archivesspace_Users_Group mailing list

Archivesspace_Users_Group@lyralists.lyrasis.org

http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group



___

Archivesspace_Users_Group mailing list

Archivesspace_Users_Group@lyralists.lyrasis.org

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

Re: [Archivesspace_Users_Group] PUI Ordering and Sorting Issue

2022-04-28 Thread Andrew Morrison 
If you're using the schema.xml that came with ArchivesSpace 3.0.1 in 
your external Solr 8.11, then it will still define the "sort_icu" 
fieldType as an instance of the solr.TextField class. If you look below 
that, there is a commented-out alternative fieldType definition which is 
an instance of solr.ICUCollationField. ArchivesSpace 3.2.0 has changed 
to that (because it no longer has to support the previously-built-in 
Solr 4.10) but you don't need to upgrade to it, you can just edit your 
schema.xml, then reload the Solr core. See the link in my previous email 
for help on how to set that up to be optimized for Japanese characters.


Andrew.


On 28/04/2022 09:44, 松山 ひとみ wrote:


Thank you Andrew!

Our IT says we’ve already been using an external Solr 8.11 with 
ArchivesSpace 3.0.1, not the one built-in.


We’re thinking of upgrading our AS to 3.2.0. Do you think we will get 
a better result?


Hitomi

*From:*archivesspace_users_group-boun...@lyralists.lyrasis.org 
 *On Behalf 
Of *Andrew Morrison

*Sent:* Thursday, April 28, 2022 4:47 PM
*To:* archivesspace_users_group@lyralists.lyrasis.org
*Subject:* Re: [Archivesspace_Users_Group] PUI Ordering and Sorting Issue

Are you using the built-in Solr search engine that comes with 
ArchivesSpace 3.0.1? If so, your sorting problems could be because it 
uses a very old version, because newer ones aren't compatible with the 
method of embedding it in a bigger application. But there is the 
option to configure ArchivesSpace to use an external Solr service:


https://archivesspace.github.io/tech-docs/provisioning/solr.html

That allows you to run a more up-to-date version, which would enable 
use of the solr.ICUCollationField class for sort fields. That can be 
adjusted to sort different languages according to their own sorting 
rules, as described here:


https://solr.apache.org/guide/8_11/language-analysis.html#unicode-collation

ArchivesSpace 3.2.0 removes the built-in Solr, so running an external 
Solr service will be necessary if you upgrade in the future.


As for adding the option to sort on identifiers, I don't think there 
is a configuration option or simple interface for adding them. But it 
would probably be possible to develop a plug-in to override certain 
Ruby methods in the core code to do it.


Andrew.

On 27/04/2022 11:04, 松山 ひとみwrote:

Hello all,

We’ve been stuck in the “ordering and sorting” issue in
[~/repositories/resources]. Our AS is version 3.0.1.

Presumably, because we use Japanese Character, our resource list
cannot be displayed in a right, alphabetical order when sorted by
Title.

Could we add Identifier to the category of sorting;
Relevance/Title(Asc/Desc)/Year(Asc/Desc), as alternative?

We’d very much appreciate you helping solve our issue!

All the best,

Hitomi Matsuyama, Audiovisual Archivist

Nakanoshima Museum of Art, Osaka

4-3-1 Nakanoshima, Kita-ku

Osaka 530-0005 JAPAN

tel. +81 (0)6 64 79 05 58

email. matsuyam...@nakka-art.jp 



___

Archivesspace_Users_Group mailing list

Archivesspace_Users_Group@lyralists.lyrasis.org

http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


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

Re: [Archivesspace_Users_Group] PUI Ordering and Sorting Issue

2022-04-28 Thread 松山　ひとみ 
Thank you Andrew!

Our IT says we’ve already been using an external Solr 8.11 with ArchivesSpace 
3.0.1, not the one built-in.
We’re thinking of upgrading our AS to 3.2.0. Do you think we will get a better 
result?

Hitomi

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Andrew 
Morrison
Sent: Thursday, April 28, 2022 4:47 PM
To: archivesspace_users_group@lyralists.lyrasis.org
Subject: Re: [Archivesspace_Users_Group] PUI Ordering and Sorting Issue


Are you using the built-in Solr search engine that comes with ArchivesSpace 
3.0.1? If so, your sorting problems could be because it uses a very old 
version, because newer ones aren't compatible with the method of embedding it 
in a bigger application. But there is the option to configure ArchivesSpace to 
use an external Solr service:

https://archivesspace.github.io/tech-docs/provisioning/solr.html

That allows you to run a more up-to-date version, which would enable use of the 
solr.ICUCollationField class for sort fields. That can be adjusted to sort 
different languages according to their own sorting rules, as described here:

https://solr.apache.org/guide/8_11/language-analysis.html#unicode-collation

ArchivesSpace 3.2.0 removes the built-in Solr, so running an external Solr 
service will be necessary if you upgrade in the future.

As for adding the option to sort on identifiers, I don't think there is a 
configuration option or simple interface for adding them. But it would probably 
be possible to develop a plug-in to override certain Ruby methods in the core 
code to do it.

Andrew.


On 27/04/2022 11:04, 松山 ひとみ wrote:
Hello all,

We’ve been stuck in the “ordering and sorting” issue in 
[~/repositories/resources]. Our AS is version 3.0.1.
Presumably, because we use Japanese Character, our resource list cannot be 
displayed in a right, alphabetical order when sorted by Title.

Could we add Identifier to the category of sorting; 
Relevance/Title(Asc/Desc)/Year(Asc/Desc), as alternative?
We’d very much appreciate you helping solve our issue!


All the best,
Hitomi Matsuyama, Audiovisual Archivist

Nakanoshima Museum of Art, Osaka
4-3-1 Nakanoshima, Kita-ku
Osaka 530-0005 JAPAN
tel. +81 (0)6 64 79 05 58
email. matsuyam...@nakka-art.jp





___

Archivesspace_Users_Group mailing list

Archivesspace_Users_Group@lyralists.lyrasis.org

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

Re: [Archivesspace_Users_Group] PUI Ordering and Sorting Issue

2022-04-28 Thread Andrew Morrison 
Are you using the built-in Solr search engine that comes with 
ArchivesSpace 3.0.1? If so, your sorting problems could be because it 
uses a very old version, because newer ones aren't compatible with the 
method of embedding it in a bigger application. But there is the option 
to configure ArchivesSpace to use an external Solr service:


https://archivesspace.github.io/tech-docs/provisioning/solr.html

That allows you to run a more up-to-date version, which would enable use 
of the solr.ICUCollationField class for sort fields. That can be 
adjusted to sort different languages according to their own sorting 
rules, as described here:


https://solr.apache.org/guide/8_11/language-analysis.html#unicode-collation

ArchivesSpace 3.2.0 removes the built-in Solr, so running an external 
Solr service will be necessary if you upgrade in the future.


As for adding the option to sort on identifiers, I don't think there is 
a configuration option or simple interface for adding them. But it would 
probably be possible to develop a plug-in to override certain Ruby 
methods in the core code to do it.


Andrew.


On 27/04/2022 11:04, 松山 ひとみ wrote:


Hello all,

We’ve been stuck in the “ordering and sorting” issue in 
[~/repositories/resources]. Our AS is version 3.0.1.


Presumably, because we use Japanese Character, our resource list 
cannot be displayed in a right, alphabetical order when sorted by Title.


Could we add Identifier to the category of sorting; 
Relevance/Title(Asc/Desc)/Year(Asc/Desc), as alternative?


We’d very much appreciate you helping solve our issue!

All the best,

Hitomi Matsuyama, Audiovisual Archivist

Nakanoshima Museum of Art, Osaka

4-3-1 Nakanoshima, Kita-ku

Osaka 530-0005 JAPAN

tel. +81 (0)6 64 79 05 58

email. matsuyam...@nakka-art.jp 


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