[
https://jira.duraspace.org/browse/DS-997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Donohue closed DS-997.
--------------------------
Resolution: Fixed
Fix Version/s: 1.8.0
Kevin is correct, this issue was resolved by DSCR-25. I've verified that is
the case.
I'm closing this issue & marking it as "fixed" by DSCR-25.
(Sidenote: it seems I was "bitten" by the potential issue I described in
DS-987. After upgrading to latest Trunk I didn't realize that the Discovery
schema was updated. I unfortunately ran 'ant update', which meant I had a
'schema.xml.new' file sitting there. So, as my schema was never updated, I was
running latest Trunk with an old Discovery Schema -- so I still was seeing this
bug occur.)
> Discovery errors out if an item has multiple 'dc.date.accessioned' values
> -------------------------------------------------------------------------
>
> Key: DS-997
> URL: https://jira.duraspace.org/browse/DS-997
> Project: DSpace
> Issue Type: Bug
> Components: Discovery, Solr
> Affects Versions: 1.8.0
> Reporter: Tim Donohue
> Priority: Major
> Fix For: 1.8.0
>
>
> Here's how you can replicate this issue.
> * Modify a single item such that it has two "dc.date.accessioned" values.
> * Restart Tomcat/Solr (may not even be necessary)
> In the Tomcat logs you will see errors like:
> Aug 17, 2011 12:54:18 PM org.apache.solr.common.SolrException log
> SEVERE: org.apache.solr.common.SolrException: can not sort on multivalued
> field: dc.date.accessioned_dt
> at
> org.apache.solr.schema.SchemaField.checkSortability(SchemaField.java:154)
> This error seems to cause the Item to no longer be available from Discovery
> or the UI in general.
> Although most items in DSpace should only ever have one
> 'dc.date.accessioned', it still is not impossible to have multiple values.
> If you import any item which already has an existing 'dc.date.accessioned'
> value (for whatever reason), DSpace will keep that value & also add a new one
> representing the new DSpace Accession Date (see the InstallItem class).
> In general, if possible, it'd be best for Discovery to not assume a single
> value for any 'dc.date' fields.
> This same issue also occurs if you manually add a second 'dc.date.issued'
> value. You'll see similar errors stating "can not sort on multivalued field:
> dc.date.issued.year".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.duraspace.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Get a FREE DOWNLOAD! and learn more about uberSVN rich system,
user administration capabilities and model configuration. Take
the hassle out of deploying and managing Subversion and the
tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
