Re: [Archivesspace_Users_Group] PUI Ordering and Sorting Issue

[Andrew Morrison]

Sorry, make that:

[^\p{L}\d\s]

Otherwise it'll strip out digits.

Andrew.


On 11/05/2022 09:53, Andrew Morrison wrote:


I'd forgotten about clean_for_sort. I've overridden it myself, in a 
plug-in. The simplest way is:


 1. In plugins/local, create a subfolder called "indexer"
 2. Create a file in that subfolder called "indexer_common_override.rb"
 3. In the file, declare "class IndexerCommon"
 4. Copy the def for clean_for_sort into that, and adjust it to meet
your requirements.
 5. Restart and re-index.

Something like:

[^\p{L}\s]

Would be a less anglocentric substitute for:

[^\w\s]

If that works, you probably won't have any empty title_sort values, 
but in general you can control the sorting of records without values 
in schema.xml with the sortMissingLast attribute, see:


https://solr.apache.org/guide/8_8/field-type-definitions-and-properties.html

Andrew.


On 11/05/2022 08:37, 松山 ひとみ wrote:


Hello, again.

We’ve tried as Andrew kindly suggested.

However, it didn’t work as well as expected…

We think using “clean_for_sort; IndexerCommon” may interfere when 
“title” is set to “title_sort”.


“clean_for_sort” looks eliminating anything except alphabets and 
numbers when sorting.


It would affect not only Japanese character but also any non-alphabet 
characters, such as Hangul or Cyrillic, we suppose.


We also wonder what order is applied when “title_sort” is empty.



Thanks,

Hitomi

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 <mailto:matsuyam...@nakka-art.jp>

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

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

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

<mailto: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

<mailto: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 i

Re: [Archivesspace_Users_Group] PUI Ordering and Sorting Issue

[Andrew Morrison]

I'd forgotten about clean_for_sort. I've overridden it myself, in a 
plug-in. The simplest way is:


1. In plugins/local, create a subfolder called "indexer"
2. Create a file in that subfolder called "indexer_common_override.rb"
3. In the file, declare "class IndexerCommon"
4. Copy the def for clean_for_sort into that, and adjust it to meet
   your requirements.
5. Restart and re-index.

Something like:

[^\p{L}\s]

Would be a less anglocentric substitute for:

[^\w\s]

If that works, you probably won't have any empty title_sort values, but 
in general you can control the sorting of records without values in 
schema.xml with the sortMissingLast attribute, see:


https://solr.apache.org/guide/8_8/field-type-definitions-and-properties.html

Andrew.


On 11/05/2022 08:37, 松山 ひとみ wrote:


Hello, again.

We’ve tried as Andrew kindly suggested.

However, it didn’t work as well as expected…

We think using “clean_for_sort; IndexerCommon” may interfere when 
“title” is set to “title_sort”.


“clean_for_sort” looks eliminating anything except alphabets and 
numbers when sorting.


It would affect not only Japanese character but also any non-alphabet 
characters, such as Hangul or Cyrillic, we suppose.


We also wonder what order is applied when “title_sort” is empty.



Thanks,

Hitomi

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 <mailto:matsuyam...@nakka-art.jp>

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

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

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

<mailto: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

<mailto: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

Re: [Archivesspace_Users_Group] PUI Ordering and Sorting Issue

[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

<mailto: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 <mailto: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

[松山 ひとみ]

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<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
<mailto: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<mailto: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<mailto:matsuyam...@nakka-art.jp>






___

Archivesspace_Users_Group mailing list

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

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



___

Archivesspace_Users_Group mailing list

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

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

Re: [Archivesspace_Users_Group] PUI Ordering and Sorting Issue

[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 <mailto: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

[松山 ひとみ]

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<mailto:matsuyam...@nakka-art.jp>





___

Archivesspace_Users_Group mailing list

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

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

Re: [Archivesspace_Users_Group] PUI Ordering and Sorting Issue

[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

[Archivesspace_Users_Group] PUI Ordering and Sorting Issue

[松山 ひとみ]

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