ROA Project : index mods:identifier type="ROA" seperately

Project:RUcore SOLR Searching and Indexing
Version:7.4
Component:Code
Category:task
Priority:critical
Assigned:rmarker
Status:closed
Description

For the ROA project mods:identifier type="roa" needs to be indexed in a separate field. This field will be used for sorting, most recent submissions.

Comments

#1

Assigned to:triggs» chadmills
Status:active» test

Created non-repeating field called: "roa_identifier_t" for these. Can be searched - e.g.: roa_identifier_t:1043 - or sorted on.

#2

Assigned to:chadmills» rmarker

Rhonda,

I am not sure how to test this. Please test.

Thanks,
Kalaivani

#3

Assigned to:rmarker» chadmills

Is there a way to test this, or otherwise confirm that it's done?

#4

I think the only way to test for sure is it ingest two objects in test with ROA identifier and sort the search results and see they are ordered correctly.

#5

Well, this hasn't happened for a while -- ingest failed. Here's the error message:
Ingesting ... OK.
<a href="http://rep-test.libraries.rutgers.edu/dlr/showfed.php?pid=rutgers-lib:202392" title="http://rep-test.libraries.rutgers.edu/dlr/showfed.php?pid=rutgers-lib:202392">http://rep-test.libraries.rutgers.edu/dlr/showfed.php?pid=rutgers-lib:20...</a>

Indexing Solr/Lucene search engine ...
Error add index to Solr/Lucene: Error with add action for rutgers-lib:202392...

Purged ingested record: rutgers-lib:202392

(in WMS rep-devel, Marker Test collection, WMS 8237)

#6

Status:test» active

This is definitely related to the ROA number in the identifier element. I ingested another record (same digital file) without an ROA number and it went in just fine. I did "Fedora Edit" in the WMS to add the ROA number in mods:identifier, and got this error message: Error indexing solr: Error with add action for rutgers-lib:202393...Something is not done right!

#7

Assigned to:chadmills» triggs

Kalaivani I am not sure if you want this marked as critical.

#8

Version:7-x» 7.4
Priority:normal» critical

Jeffery,

Please see Rhonda's comment #6. We need to address it, otherwise, we won't be able to ingest ROA objects.

Thanks,
Kalaivani

#9

Assigned to:triggs» rmarker
Status:active» test

I found a weird typo in the roa xslt transformation on devel. Try ingesting now with an roa.

#10

Assigned to:rmarker» chadmills

These two records can be used to sort:
<a href="https://rucore-test.libraries.rutgers.edu/rutgers-lib/202392/" title="https://rucore-test.libraries.rutgers.edu/rutgers-lib/202392/">https://rucore-test.libraries.rutgers.edu/rutgers-lib/202392/</a>
<a href="https://rucore-test.libraries.rutgers.edu/rutgers-lib/202393/" title="https://rucore-test.libraries.rutgers.edu/rutgers-lib/202393/">https://rucore-test.libraries.rutgers.edu/rutgers-lib/202393/</a>

ROA numbers 879 and 878, respectively

#11

Assigned to:chadmills» rmarker

Rhonda,

I created a portal with the two records. I create a order by ROA ascending and descending and configured those options in the portal. Please use the following to test. Note the order by option on the search screen has both options.

<a href="https://rucore-test.libraries.rutgers.edu/partnerportal/search/index.php?key=9Tp0Vx3If" title="https://rucore-test.libraries.rutgers.edu/partnerportal/search/index.php?key=9Tp0Vx3If">https://rucore-test.libraries.rutgers.edu/partnerportal/search/index.php...</a>

#12

Status:test» fixed

Sort by ROA number works correctly.

#13

Status:fixed» closed

Back to top