Also ran into this recently during full oai import. Didn't have time to analyze it completely but oai indexer ran aground (same NPE) on items with resourcepolicies set for a specific eperson and thus had a null group. That should be a valid option, though. I didn't check whether oai indexer has always had a problem with it or it's a regression. Definitely worth filing an issue.
SELECT * FROM resourcepolicy WHERE epersongroup_id IS NULL AND resource_id IS NOT NULL; SELECT resource_id, dspace_object FROM resourcepolicy WHERE epersongroup_id IS NULL AND resource_id IS NOT NULL AND resource_type_id=2 GROUP BY 1, 2; Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette On Fri, Sep 7, 2018 at 11:26 PM <[email protected]> wrote: > > Hi Christian, > > I also encountered this while testing 6.3 the other day. > > In my case, I modified both the willChangeStatus() and > getMostRecentModificationDate() methods in XOAI.java to check for a null > ResourcePolicy Group (similar to what you suggested). > > After the change I was able to do a full import (dspace oai import -c). > > However, since I'm new to DSpace, I'm also not clear on whether all > ResourcePolicy objects with READ action should have Groups assigned. > > -- > Sean > > On Tuesday, 24 July 2018 07:44:32 UTC-5, Christian Scheible wrote: >> >> Hi all, >> >> we have recently upgraded to DSpace 6.3 and are experiencing problems >> with the update of the OAI Solr index. >> We have a NullPointerException at >> https://github.com/DSpace/DSpace/blob/dspace-6.3/dspace-oai/src/main/java/org/dspace/xoai/app/XOAI.java#L438 >> which was introduced with DSpace 6.3. >> >> The added code that leads to the problem was added in order to respect >> embargoed items at the OAI interface. >> >> I could easily solve this by changing the line to: if (policy.getGroup() >> != null && policy.getGroup().getName() != null && >> policy.getGroup().getName().equals("Anonymous")) { >> >> But I am wondering if there is something messed up with our >> ResourcePolicies. >> So my question is: >> >> Should ResourcePolicies for Items of type Read always contain a >> EPersonGroup? >> >> Kind Regards >> Christian >> >> -- >> Christian Scheible >> Softwareentwickler / Abt. Content-basierte Dienste >> Kommunikations-, Informations-, Medienzentrum (KIM) >> Universität Konstanz >> 78457 Konstanz >> +49 (0)7531 / 88-2857 >> Raum B 703 >> >> > -- > All messages to this mailing list should adhere to the DuraSpace Code of > Conduct: https://duraspace.org/about/policies/code-of-conduct/ > --- > You received this message because you are subscribed to the Google Groups > "DSpace Technical Support" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/dspace-tech. > For more options, visit https://groups.google.com/d/optout. -- All messages to this mailing list should adhere to the DuraSpace Code of Conduct: https://duraspace.org/about/policies/code-of-conduct/ --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
