Arctos: Request - sort by catalog number not by alphanumeric (GUID)

[mkoo]

I dont see this issue listed but I heard it a few times in only the last month!

In search result table, sort by numeric catalog number even if it's being displayed as the alphanumeric GUID. See attached which shows the first 19 records of LINGU where it starts as LINGU:HERP:1, LINGU:HERP:10, LINGU:HERP:11, etc instead of LINGU:HERP:1, LINGU:HERP:2, LINGU:HERP:3 (sorry to being picking on LINGU but applies to any search)

Seems that there may be both a SQL way to do this or something to do with the form such as sort by catalogNumber but display the tripart alphanumeric to achieve the same ends.

would be high value display feature for all arctos users!

[AJLinn]

We use leading zeros to make sure all numbers sort properly (e.g., UAM:EH:UA2020-001-0001). However, we do run into trouble with our pre-2000 numbers that are represented by 2 places in the UA-string (e.g., UA64-021-0001) instead of the UA64 number sorting first, the UA2020 number will preceed it. Haven't figured out a way to make that work yet...other than the terrible though of re-numbering thousands of records with 19xx.

[campmlc]

Agree. I have to download to excel and parse the column to do this now.

On Sat, Jan 9, 2021, 12:14 PM Angela Linn [e-mail] wrote:

• [EXTERNAL]*

We use leading zeros to make sure all numbers sort properly (e.g.,
UAM:EH:UA2020-001-0001). However, we do run into trouble with our pre-2000
numbers that are represented by 2 places in the UA-string (e.g.,
UA64-021-0001) instead of the UA64 number sorting first, the UA2020 number
will preceed it. Haven't figured out a way to make that work yet...

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ArctosDB/arctos/issues/3343#issuecomment-757353679,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADQ7JBDNU4QD3VYB55KICRLSZCTKNANCNFSM4V3LKBRQ
.

[mkoo]

that's what I would hope to fix-- necessitating leading 0's which can cause its own problems and manually sorting in a separate app. probably other annoyances /issues may be addressed too with this fix!

[dustymc]

Catnum isn't numeric, and I don't see any way to fake it. We could add cat_num_integer to FLAT, which would provide a numeric sort for collections that use that.

[Jegelewicz]

We could add cat_num_integer to FLAT, which would provide a numeric sort for collections that use that.

This is long overdue. I say we get it done now.

[KyndallH]

Beyond catnum, I run into this issue other places and it is frustrating.

[KyndallH]

[campmlc]

Yes! I second @KyndallH . We need options to select how we want containers and hierarchies to be sorted and displayed.

[itzuecs]

Hello,

I just want to follow up with this issue. We are facing the same sorting problem. Is there any update about @dustymc suggestion? Thanks!

Catnum isn't numeric, and I don't see any way to fake it. We could add cat_num_integer to FLAT, which would provide a numeric sort for collections that use that.

[Jegelewicz]

Catnum isn't numeric, and I don't see any way to fake it. We could add cat_num_integer to FLAT, which would provide a numeric sort for collections that use that.

@dustymc if this wouldn't be too difficult, I think we should do it. This has been a long-standing complaint.

[dustymc]

Blocked by https://github.com/ArctosDB/arctos/issues/2154

[dustymc]

Done

[itzuecs]

I am not sure how this fix the issue #3334 Request - sort by catalog number not by alphanumeric (GUID). The numbers in our catalogue are still not in order on Arctos. Do you mind explaining how this will help with the ordering to collections that do not need the new_new_catnum?

[dustymc]

[dustymc]

@mkoo @itzuecs can this be closed?

[KyndallH]

What about Next2layers? See my comment above? Or should that be a different issue?

[dustymc]

Or should that be a different issue?

Yes please.