[Enhancement]: Filtering within new CoRA prod search results

[lfkennedy]

Context

Ease of locating specific specimens or subsets of specimens within a Specimen Search list result.

Description

Ability to filter or sort by individual columns so that similarly coded specimens show up next to each other in the list would enhance search capabilities.

Related links

• Requesting a change

Use Cases

In particular, I could see filtering or sorting by Individual Number, DNA sample number, or Mito Sequence number being helpful as it would group together specimens or make them similarly easier to find in the larger list. Being able to search by provenience 1, for example, would pull up a bunch of specimens that might be associated by provenience, and sorting by Mito Sequence number within that provenience could give an indication of specimens that might be possible to associate to a specific individual.

Solutions

Sorting "arrows" were available in previous CoRA versions, see circled areas in 2nd photo below.

Alternatives

No response

Visuals

Before submitting

• I have read and followed the change request guidelines.
• I have verified that my idea is a change request and not a bug report.
• I have ensured that, to the best of my knowledge, my idea will benefit the entire community.
• I have included relevant links to the documentation, related issues, and discussions to underline the need for my idea.

[clegarde]

I second this request!

[SachinPawaskarUNO]

@lfkennedy I agree, this is being planned in the near future.
The data-tables will include sorting and searching (by select fields) in the near future.

I see that you have provided with an initial list of fields that you would like to see have the sort capability.
Can you maybe list which fields would should have sort and search capabilities in terms of priority order?

[SachinPawaskarUNO]

@lfkennedy BTW, Thank you for using the issues template and providing me with all the details along with screenshots.

[lfkennedy]

@lfkennedy I agree, this is being planned in the near future. The data-tables will include sorting and searching (by select fields) in the near future.

I see that you have provided with an initial list of fields that you would like to see have the sort capability. Can you maybe list which fields would should have sort and search capabilities in terms of priority order?

For me, I am currently updating DNA so the fields I would prioritize would be "DNA Sample Number" and "Mito Sequence number"; "Bone" would be secondary for me
"Individual number" I believe would be helpful in the future but there aren't that many individuals segregated out as of now.

Tagging Carrie in case she has additional priorities for fields that would be nice to have sorting functionality @clegarde

[clegarde]

I agree. The following are the important ones, and I think in this general order.

• Key
• Mito Seq
• DNA Sample
• Individual Number
• Bone

[clegarde]

Just to add to this - I've started adding some association info and the fact that we can't sort by "Key" is really frustrating! It's adding a lot more time in data entry. @SachinPawaskarUNO

[SachinPawaskarUNO]

@lfkennedy @clegarde For now I have added sortBy capability on Specimen Search screen for Key, Individual Number, External Number and some other specimen fields. Will have to work on sortBy on DNA fields such as Sample Number, Mito Sequence Number.

[lfkennedy]

@lfkennedy @clegarde For now I have added sortBy capability on Specimen Search screen for Key, Individual Number, External Number and some other specimen fields. Will have to work on sortBy on DNA fields such as Sample Number, Mito Sequence Number.

The "key" sort is helpful already, thank you! One question - what does the "1" after the sorted column mean (circled below)?

[SachinPawaskarUNO]

@lfkennedy My plan is to have multi-sort capability for CoRA, which means that you can sort by multiple columns. The 1 in this case would be the first sortBy Column. The subsequent columns would be 2, 3,. ...

Give it a try, First Sort by Side and then by Key within it.

[lfkennedy]

@SachinPawaskarUNO cool! It is working for me, that's nice to have. Thanks!