[Dspace-tech] Problems with solr/full text
Hi
Using dspace snapshot 5.0, I noticed that I was no longer searching over full
text
Looking at SOLR I get the following
{ responseHeader: { status: 0, QTime: 1, params: { fl: fulltext,
indent: true, q: constitution, _: 1403852029740, wt: json } },
response: { numFound: 1024, start: 0, docs: [ { fulltext: [
org.apache.commons.io.input.AutoCloseInputStream@5527652e ] }, { fulltext:
[ org.apache.commons.io.input.AutoCloseInputStream@294205f4 ] }, {
fulltext: [ org.apache.commons.io.input.AutoCloseInputStream@5586468d ] },
{ fulltext: [ org.apache.commons.io.input.AutoCloseInputStream@5e854128 ]
…and so on.
So I think something is going wrong?
Should I just revert to 4.1? and does anyone know if doing so will be painless
(or will I need to use packager to export everything and reimport it into the
reverted version?)
Thanks,
Robin
[cid:1D48A18F-6713-4D10-A644-A8C20DF490E5]
Robin Harper
Director
Infrastructure and Engineering
Level 7
155 King Street
Sydney NSW 2000 Australia
Tel: 8815 9094
Mobile: 0403 260 353
robin.har...@barnet.com.aumailto:robin.har...@barnet.com.au
--
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
[Dspace-tech] setting metadata fields during install time
Hi all, I am trying to define the metadata field set already during install time. The tables metadataschemaregistry and metadatafieldregistry are only created but not filled by the SQL script provided by dspace (dspace/etc/postgres/database_schema.sql) to initialize the database. At which point during build install are these two tables filled with the default schemas (DC DCTERMS)? Is this done during 'ant fresh_install'? How can I influence the set of schemas that is installed? Best, Daniel -- Daniel Scharon Communication, Information, Media Centre (KIM) Content Services Department Room B 703 University of Konstanz 78457 Konstanz, Germany Tel: +49 7531 88-2951 XMPP: daniel.scha...@uni-konstanz.de Web: http://www.kim.uni-konstanz.de smime.p7s Description: S/MIME cryptographic signature -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] setting metadata fields during install time
Hi Daniel, nice question, it's actually pretty easy to do. The initialization of the metadata schemas happens through the ant scripts, that are defined in build.xml Here are the lines where you can find the defintions about which metadata schema's are being loaded: https://github.com/DSpace/DSpace/blob/master/dspace/src/main/config/build.xml#L850 The actual definition of those registraties that can be loaded are found here: https://github.com/DSpace/DSpace/tree/master/dspace/config/registries cheers, Bram Luyten -- [image: logo] *Bram Luyten* +1 202 684 6365 *2888 Loker Avenue East, Suite 315, Carlsbad, CA. 92010* *Esperantolaan 4, Heverlee 3001, Belgium* www.atmire.com http://atmire.com/website/?q=servicesutm_source=emailfooterutm_medium=emailutm_campaign=braml On Fri, Jun 27, 2014 at 10:10 AM, Daniel Scharon daniel.scha...@uni-konstanz.de wrote: Hi all, I am trying to define the metadata field set already during install time. The tables metadataschemaregistry and metadatafieldregistry are only created but not filled by the SQL script provided by dspace (dspace/etc/postgres/database_schema.sql) to initialize the database. At which point during build install are these two tables filled with the default schemas (DC DCTERMS)? Is this done during 'ant fresh_install'? How can I influence the set of schemas that is installed? Best, Daniel -- Daniel Scharon Communication, Information, Media Centre (KIM) Content Services Department Room B 703 University of Konstanz 78457 Konstanz, Germany Tel: +49 7531 88-2951 XMPP: daniel.scha...@uni-konstanz.de Web: http://www.kim.uni-konstanz.de -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
[Dspace-tech] Export to Reference Management Systems
Hello all, I wonder if there is a way to export items on UI level to bibliographic formats like RIS or BibTeX to get it importable into reference management systems. I have found several discussions on that topic (http://dspace.2283337.n4.nabble.com/download-citation-in-EndNote-format-td3284273.html, http://dspace.2283337.n4.nabble.com/Export-facility-into-basic-bibliographic-formats-Endnote-BibTex-RIS-TSV-CSV-into-DSpace-td4668095.html), but none of them has a reusable solution. There is even a ticket for this functionality (https://jira.duraspace.org/browse/DS-1224), but its marked as Wont fix due to licence issues with a third-party-software. Some DSpace instances are offering reference-management-system-export (the Greek National Documentation Center http://helios-eie.ekt.gr/EIE/handle/10442/11354 and OpenRepository http://hzi.openrepository.com/hzi/handle/10033/8666), but I don't see any reusable module. Can anyone help me on that? Thanks Oliver -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] Export to Reference Management Systems
Hi Oliver, you could use the sharing bar for JSPUI [1]. It depends on the OAI module (DSpace 3 or newer). Because not everyone wants to enable this module and sharing bar doesn't currently detect whether you have OAI enabled, sharing bar is not a part of DSpace yet. But if you're running JSPUI, you can use the patch. It should be relatively easy to add the XMLUI part, too. [1] https://jira.duraspace.org/browse/DS-1493 Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] OAI problems, with Dspace 5.0 Snapshot
That's because the error is actually in one of the libraries dspace depends on. So you'll either need to wait until it's fixed there (the place maven pulls it from), or you can patch and build the library locally yourself. Regards, OK 2014-06-27 1:30 GMT+02:00 Robin Harper robin.har...@barnet.com.au: Hi, It certainly looks like it. However I can’t locate the corresponding code in the DSpace source (the link seems to be to a separate XOAI repo). I am probably just showing my ignorance. Thanks, Robin On 25 Jun 2014, at 8:25 pm, Ondřej Košarko kosa...@ufal.mff.cuni.cz wrote: Hey, Isn't this the bug described in https://jira.duraspace.org/browse/DS-1959 ? Regards, OK 2014-06-25 2:16 GMT+02:00 João Melo jm...@lyncode.com: Hi Robin, yes, those namespaces should be in the output and are, currently, missing. That's a bug, a major bug. I'm going to take care of that one. I'm going to create a jira issue to track this one. On 24 June 2014 23:27, Robin Harper robin.har...@barnet.com.au wrote: Forgive me if this should really go into dspace-devel I am having problems with OAI, and unspecified errors if I try and harvest from the 5.0-snapshot dspace I am using. Using a browser to query the OAI all looks well (although different from the demo.dspace) until I send a command like this. /oai/request?verb=ListRecordsmetadataPrefix=oai_dcset=col_11003_2946 Then I get in the browser (firefox) XML Parsing Error: prefix not bound to a namespace Location: http://dspace.barnet.com.au:8080/oai/request?verb=ListRecordsmetadataPrefix=oai_dcset=col_11003_2946 Line Number 1, Column 707: (Safari just fails quietly.) I *think* the problem is that I am missing some headers: Before each record I have metadataoai_dc:dc xsi:schemaLocation=http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd;dc:titleSome title/dc:title But I think there should be more there for instance demo.dspace has metadataoai_dc:dc xmlns:oai_dc= http://www.openarchives.org/OAI/2.0/oai_dc/; xmlns:doc= http://www.lyncode.com/xoai; xmlns:xsi= http://www.w3.org/2001/XMLSchema-instance; xmlns:dc= http://purl.org/dc/elements/1.1/; xsi:schemaLocation= http://www.openarchives.org/OAI/2.0/oai_dc/ http://www.openarchives.org/OAI/2.0/oai_dc.xsd; I can probably fix this - if its the right problem, but just wondered if it was a known problem with a known fix? I may be misreading it, but none of the pull requests in the jira appear to be on point. Thanks Robin -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] Problems with solr/full text
Hi Robin, sorry, I don't know what's wrong with fulltext in Solr but be sure to file a Jira issue. Downgrading to DSpace 4 should be painless so far. There were no DB changes and no Solr schema changes. There aren't many new major features. There was an upgrade to OAI, so after you downgrade, reimport the OAI index (oai import -c) just to be sure. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] OAI problems, with Dspace 5.0 Snapshot
On Fri, Jun 27, 2014 at 1:30 AM, Robin Harper robin.har...@barnet.com.au wrote: It certainly looks like it. However I can’t locate the corresponding code in the DSpace source (the link seems to be to a separate XOAI repo). Hi Robin, like Ondřej said, it's a separate library [1] pulled in via Maven [2]. [1] https://github.com/lyncode/xoai [2] http://search.maven.org/#search%7Cga%7C1%7Cxoai Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] Problem to upload files (pdf) or items
Hi Yelena, Internal system error is just a generic message that there was an error. You'll need to find the specific error in logs before anyone here will be able to help you. Here's how you can do that: https://wiki.duraspace.org/display/DSPACE/Troubleshoot+an+error Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] Export to Reference Management Systems
Hi Helix, thanks for pointing that out. This should be very helpful for me, as I have enabled OAI and am running JSPUI. I'll look into it. Thanks again, regards Oliver Am 27.06.2014 12:50, schrieb helix84: Hi Oliver, you could use the sharing bar for JSPUI [1]. It depends on the OAI module (DSpace 3 or newer). Because not everyone wants to enable this module and sharing bar doesn't currently detect whether you have OAI enabled, sharing bar is not a part of DSpace yet. But if you're running JSPUI, you can use the patch. It should be relatively easy to add the XMLUI part, too. [1] https://jira.duraspace.org/browse/DS-1493 Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] Publication Date Metadata
Hi Sebastien and Trevor, Maybe I've misunderstood things. It might help to take a step back. What is the setup you are trying to achieve in the DSpace submission steps? In other words, what is your use case here? As you mentioned, it's very possible the Initial Question step doesn't meet your use case. If so, it might be good to clarify how you want the submission forms to act, e.g. Are you trying to set dc.date.issued to today's date at all times? What is the reason why you'd rather your submitters not be required to specify the dc.date.issued themselves (which is the default setting in DSpace 4.x)? It's harder for us to debug this issue without a better understanding of what it is you are trying to achieve. It sounds like I had wrongly assumed you just wanted the same setup as in DSpace 3 (which is why I recommended just re-enabling Initial Questions). - Tim On 6/27/2014 9:14 AM, Sebastien Ival wrote: Hi Tim, I have two points to make 1) I think as mentioned in https://jira.duraspace.org/browse/DS-1655, the initial question step is a bit unclear and is now handled as part of the submission process. So having to re-enable it feels like going backward. I don't think the two should be hooked together. 2) To have the question The item has been published or publicly distributed before showing up, I also need to add dc.identifier.citation and dc.publisher. The field only shows up, if you answer yes to the question and you can set all of these values otherwise, it still look like the date is not being set. As when I try to take the task I get an internal server error with : -- Method: POST -- Parameters were: -- submit_claim: Take Task -- workflow_id: 186 -- step: 0 org.apache.jasper.JasperException: java.lang.NullPointerException at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Caused by: java.lang.NullPointerException at org.dspace.content.DCDate.getMonthUTC(DCDate.java:368) at org.dspace.content.DCDate.displayUTCDate(DCDate.java:520) at org.dspace.content.DCDate.displayDate(DCDate.java:487) at org.dspace.app.webui.util.UIUtil.displayDate(UIUtil.java:249) at org.dspace.app.webui.jsptag.ItemTag.render(ItemTag.java:541) at org.dspace.app.webui.jsptag.ItemTag.doStartTag(ItemTag.java:289) at org.apache.jsp.mydspace.preview_002dtask_jsp._jspService(preview_002dtask_jsp.java:352) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432) ... 44 more This makes me think the dc.date.issued is still blank. Any ideas ? Sebastien Original Message From: Tim Donohue tdono...@duraspace.org Sent: Thursday, June 26, 2014 10:03 AM To: Trevor Wilson; dspace-tech@lists.sourceforge.net Subject: Re: [Dspace-tech] Publication Date Metadata Trevor, Sorry for the delay in getting back. I'm still trying to catch up on email since the Open Repositories conference earlier this month. I've cleaned up the documentation a bit: https://wiki.duraspace.org/display/DSDOC4x/Metadata+Recommendations Setting dc.date.issued to today only really works when you are using SWORD or external tools to submit data. If you are mostly submitting from the web UI, your best bet is to likely re-enable the Initial Questions page (see above docs for the link). This lets submitters tell you if the item was published or not. If it was not published before, then the dc.date.issued will be auto-set to today's date. By default, in DSpace 4.0, the Initial Questions page is disabled. This means that the 'dc.date.issued' field is REQUIRED to be entered for every submission (i.e. it'll never be empty, and it will never be automatically set to today's date -- the submitter must manually choose the appropriate date) Hopefully this makes sense, and meets your use cases. If you need to configure DSpace in some other way, you may need to write a custom Submission step to do so. But, feel free to ask more questions if this isn't clear. - Tim -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] Publication Date Metadata
Hi Tim, The default setup is what we are looking at. Users have submit theses = original work. So the users should not have to set this date. It should be automated as per version 3.2. Once we did the upgrade from 3.2 to 4.1, submitting a new thesis would result in a blank dc.date.issued. I was trying to revert for this portion to the 3.2 behavior. It seems to me that adding the initial questions does not fix this. Are you trying to set dc.date.issued to today's date at all times? Yes, this is the behavior we would like to see. What is the reason why you'd rather your submitters not be required to specify the dc.date.issued themselves (which is the default setting in DSpace 4.x)? They are submitting original work. You did not assume wrongly. I am trying (unsuccessfully) to revert to the 3.2 behaviour. Thanks for your help. This is really appreciated. -Original Message- From: Tim Donohue [mailto:tdono...@duraspace.org] Sent: June-27-14 10:37 AM To: Sebastien Ival; dspace-tech@lists.sourceforge.net Cc: Trevor Wilson Subject: Re: [Dspace-tech] Publication Date Metadata Hi Sebastien and Trevor, Maybe I've misunderstood things. It might help to take a step back. What is the setup you are trying to achieve in the DSpace submission steps? In other words, what is your use case here? As you mentioned, it's very possible the Initial Question step doesn't meet your use case. If so, it might be good to clarify how you want the submission forms to act, e.g. Are you trying to set dc.date.issued to today's date at all times? What is the reason why you'd rather your submitters not be required to specify the dc.date.issued themselves (which is the default setting in DSpace 4.x)? It's harder for us to debug this issue without a better understanding of what it is you are trying to achieve. It sounds like I had wrongly assumed you just wanted the same setup as in DSpace 3 (which is why I recommended just re-enabling Initial Questions). - Tim On 6/27/2014 9:14 AM, Sebastien Ival wrote: Hi Tim, I have two points to make 1) I think as mentioned in https://jira.duraspace.org/browse/DS-1655, the initial question step is a bit unclear and is now handled as part of the submission process. So having to re-enable it feels like going backward. I don't think the two should be hooked together. 2) To have the question The item has been published or publicly distributed before showing up, I also need to add dc.identifier.citation and dc.publisher. The field only shows up, if you answer yes to the question and you can set all of these values otherwise, it still look like the date is not being set. As when I try to take the task I get an internal server error with : -- Method: POST -- Parameters were: -- submit_claim: Take Task -- workflow_id: 186 -- step: 0 org.apache.jasper.JasperException: java.lang.NullPointerException at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Caused by: java.lang.NullPointerException at org.dspace.content.DCDate.getMonthUTC(DCDate.java:368) at org.dspace.content.DCDate.displayUTCDate(DCDate.java:520) at org.dspace.content.DCDate.displayDate(DCDate.java:487) at org.dspace.app.webui.util.UIUtil.displayDate(UIUtil.java:249) at org.dspace.app.webui.jsptag.ItemTag.render(ItemTag.java:541) at org.dspace.app.webui.jsptag.ItemTag.doStartTag(ItemTag.java:289) at org.apache.jsp.mydspace.preview_002dtask_jsp._jspService(preview_002dtask_jsp.java:352) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432) ... 44 more This makes me think the dc.date.issued is still blank. Any ideas ? Sebastien Original Message From: Tim Donohue tdono...@duraspace.org Sent: Thursday, June 26, 2014 10:03 AM To: Trevor Wilson; dspace-tech@lists.sourceforge.net Subject: Re: [Dspace-tech] Publication Date Metadata Trevor, Sorry for the delay in getting back. I'm still trying to catch up on email since the Open Repositories conference earlier this month. I've cleaned up the documentation a bit: https://wiki.duraspace.org/display/DSDOC4x/Metadata+Recommendations Setting dc.date.issued to today only really works when you are using SWORD or external tools to submit data. If you are mostly submitting from the web UI, your best bet is to likely re-enable the Initial Questions page (see above docs for the link). This lets submitters tell you if the item was published or not. If it was not published before, then the dc.date.issued will be auto-set to today's date. By default, in DSpace 4.0, the Initial Questions page is disabled. This means that the 'dc.date.issued' field
Re: [Dspace-tech] Publication Date Metadata
Hi Sebastien, OK, now I think I'm finally understanding things...sorry, it was not initially clear what your goal was and how you were getting this error. It sounds like you're hitting an error during the *Workflow Approval Steps* after you've re-enabled the Initial Questions step. I need to dig in deeper here, but it's possible there's a bug here that we've overlooked. - Tim On 6/27/2014 9:46 AM, Sebastien Ival wrote: Hi Tim, The default setup is what we are looking at. Users have submit theses = original work. So the users should not have to set this date. It should be automated as per version 3.2. Once we did the upgrade from 3.2 to 4.1, submitting a new thesis would result in a blank dc.date.issued. I was trying to revert for this portion to the 3.2 behavior. It seems to me that adding the initial questions does not fix this. Are you trying to set dc.date.issued to today's date at all times? Yes, this is the behavior we would like to see. What is the reason why you'd rather your submitters not be required to specify the dc.date.issued themselves (which is the default setting in DSpace 4.x)? They are submitting original work. You did not assume wrongly. I am trying (unsuccessfully) to revert to the 3.2 behaviour. Thanks for your help. This is really appreciated. -Original Message- From: Tim Donohue [mailto:tdono...@duraspace.org] Sent: June-27-14 10:37 AM To: Sebastien Ival; dspace-tech@lists.sourceforge.net Cc: Trevor Wilson Subject: Re: [Dspace-tech] Publication Date Metadata Hi Sebastien and Trevor, Maybe I've misunderstood things. It might help to take a step back. What is the setup you are trying to achieve in the DSpace submission steps? In other words, what is your use case here? As you mentioned, it's very possible the Initial Question step doesn't meet your use case. If so, it might be good to clarify how you want the submission forms to act, e.g. Are you trying to set dc.date.issued to today's date at all times? What is the reason why you'd rather your submitters not be required to specify the dc.date.issued themselves (which is the default setting in DSpace 4.x)? It's harder for us to debug this issue without a better understanding of what it is you are trying to achieve. It sounds like I had wrongly assumed you just wanted the same setup as in DSpace 3 (which is why I recommended just re-enabling Initial Questions). - Tim On 6/27/2014 9:14 AM, Sebastien Ival wrote: Hi Tim, I have two points to make 1) I think as mentioned in https://jira.duraspace.org/browse/DS-1655, the initial question step is a bit unclear and is now handled as part of the submission process. So having to re-enable it feels like going backward. I don't think the two should be hooked together. 2) To have the question The item has been published or publicly distributed before showing up, I also need to add dc.identifier.citation and dc.publisher. The field only shows up, if you answer yes to the question and you can set all of these values otherwise, it still look like the date is not being set. As when I try to take the task I get an internal server error with : -- Method: POST -- Parameters were: -- submit_claim: Take Task -- workflow_id: 186 -- step: 0 org.apache.jasper.JasperException: java.lang.NullPointerException at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Caused by: java.lang.NullPointerException at org.dspace.content.DCDate.getMonthUTC(DCDate.java:368) at org.dspace.content.DCDate.displayUTCDate(DCDate.java:520) at org.dspace.content.DCDate.displayDate(DCDate.java:487) at org.dspace.app.webui.util.UIUtil.displayDate(UIUtil.java:249) at org.dspace.app.webui.jsptag.ItemTag.render(ItemTag.java:541) at org.dspace.app.webui.jsptag.ItemTag.doStartTag(ItemTag.java:289) at org.apache.jsp.mydspace.preview_002dtask_jsp._jspService(preview_002dtask_jsp.java:352) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432) ... 44 more This makes me think the dc.date.issued is still blank. Any ideas ? Sebastien Original Message From: Tim Donohue tdono...@duraspace.org Sent: Thursday, June 26, 2014 10:03 AM To: Trevor Wilson; dspace-tech@lists.sourceforge.net Subject: Re: [Dspace-tech] Publication Date Metadata Trevor, Sorry for the delay in getting back. I'm still trying to catch up on email since the Open Repositories conference earlier this month. I've cleaned up the documentation a bit: https://wiki.duraspace.org/display/DSDOC4x/Metadata+Recommendations Setting dc.date.issued to today only really
[Dspace-tech] index-lucene-update
I just ran index-lucene-init and it completed successfully, but when I
try to run
index-lucene-update, it blows up at where I have ():
*/
public static void cleanIndex(Context context) throws IOException,
SQLException {
IndexReader reader = DSQuery.getIndexReader();
Bits liveDocs = MultiFields.getLiveDocs(reader);
for(int i = 0 ; i reader.numDocs(); i++)
{
() if (!liveDocs.get(i))
The error I'm getting is
Exception: null
java.lang.NullPointerException
at org.dspace.search.DSIndexer.cleanIndex(DSIndexer.java:616)
I know reader is not null, but liveDocs must be, but why?
-Jose
--
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] index-lucene-update
I just checked the API documentation, and it says:
Class MultiFields
public static Bits getLiveDocs(IndexReader reader)
Returns a single Bits instance for this reader, merging live Documents
on the fly. This method will return null if the reader has no
deletions.
Should there be a check for null?
On Fri, Jun 27, 2014 at 11:40 AM, Jose Blanco blan...@umich.edu wrote:
I just ran index-lucene-init and it completed successfully, but when I
try to run
index-lucene-update, it blows up at where I have ():
*/
public static void cleanIndex(Context context) throws IOException,
SQLException {
IndexReader reader = DSQuery.getIndexReader();
Bits liveDocs = MultiFields.getLiveDocs(reader);
for(int i = 0 ; i reader.numDocs(); i++)
{
() if (!liveDocs.get(i))
The error I'm getting is
Exception: null
java.lang.NullPointerException
at org.dspace.search.DSIndexer.cleanIndex(DSIndexer.java:616)
I know reader is not null, but liveDocs must be, but why?
-Jose
--
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] Publication Date Metadata
Perfect. Thank you -Original Message- From: Tim Donohue [mailto:tdono...@duraspace.org] Sent: June-27-14 11:53 AM To: Sebastien Ival; dspace-tech@lists.sourceforge.net Cc: Trevor Wilson Subject: Re: [Dspace-tech] Publication Date Metadata Hi Sebastien, After further investigation, this sounds like a bug in the JSPUI specifically. It does NOT occur in the XMLUI, but seems to only occur with a combination of JSPUI + Initial Questions + Workflow approval steps. I've logged it at: https://jira.duraspace.org/browse/DS-2043 We'll have to find someone to look into it and resolve it. - Tim On 6/27/2014 10:15 AM, Tim Donohue wrote: Hi Sebastien, OK, now I think I'm finally understanding things...sorry, it was not initially clear what your goal was and how you were getting this error. It sounds like you're hitting an error during the *Workflow Approval Steps* after you've re-enabled the Initial Questions step. I need to dig in deeper here, but it's possible there's a bug here that we've overlooked. - Tim On 6/27/2014 9:46 AM, Sebastien Ival wrote: Hi Tim, The default setup is what we are looking at. Users have submit theses = original work. So the users should not have to set this date. It should be automated as per version 3.2. Once we did the upgrade from 3.2 to 4.1, submitting a new thesis would result in a blank dc.date.issued. I was trying to revert for this portion to the 3.2 behavior. It seems to me that adding the initial questions does not fix this. Are you trying to set dc.date.issued to today's date at all times? Yes, this is the behavior we would like to see. What is the reason why you'd rather your submitters not be required to specify the dc.date.issued themselves (which is the default setting in DSpace 4.x)? They are submitting original work. You did not assume wrongly. I am trying (unsuccessfully) to revert to the 3.2 behaviour. Thanks for your help. This is really appreciated. -Original Message- From: Tim Donohue [mailto:tdono...@duraspace.org] Sent: June-27-14 10:37 AM To: Sebastien Ival; dspace-tech@lists.sourceforge.net Cc: Trevor Wilson Subject: Re: [Dspace-tech] Publication Date Metadata Hi Sebastien and Trevor, Maybe I've misunderstood things. It might help to take a step back. What is the setup you are trying to achieve in the DSpace submission steps? In other words, what is your use case here? As you mentioned, it's very possible the Initial Question step doesn't meet your use case. If so, it might be good to clarify how you want the submission forms to act, e.g. Are you trying to set dc.date.issued to today's date at all times? What is the reason why you'd rather your submitters not be required to specify the dc.date.issued themselves (which is the default setting in DSpace 4.x)? It's harder for us to debug this issue without a better understanding of what it is you are trying to achieve. It sounds like I had wrongly assumed you just wanted the same setup as in DSpace 3 (which is why I recommended just re-enabling Initial Questions). - Tim On 6/27/2014 9:14 AM, Sebastien Ival wrote: Hi Tim, I have two points to make 1) I think as mentioned in https://jira.duraspace.org/browse/DS-1655, the initial question step is a bit unclear and is now handled as part of the submission process. So having to re-enable it feels like going backward. I don't think the two should be hooked together. 2) To have the question The item has been published or publicly distributed before showing up, I also need to add dc.identifier.citation and dc.publisher. The field only shows up, if you answer yes to the question and you can set all of these values otherwise, it still look like the date is not being set. As when I try to take the task I get an internal server error with : -- Method: POST -- Parameters were: -- submit_claim: Take Task -- workflow_id: 186 -- step: 0 org.apache.jasper.JasperException: java.lang.NullPointerException at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecuto r.java:615) at java.lang.Thread.run(Thread.java:744) Caused by: java.lang.NullPointerException at org.dspace.content.DCDate.getMonthUTC(DCDate.java:368) at org.dspace.content.DCDate.displayUTCDate(DCDate.java:520) at org.dspace.content.DCDate.displayDate(DCDate.java:487) at org.dspace.app.webui.util.UIUtil.displayDate(UIUtil.java:249) at org.dspace.app.webui.jsptag.ItemTag.render(ItemTag.java:541) at org.dspace.app.webui.jsptag.ItemTag.doStartTag(ItemTag.java:289) at org.apache.jsp.mydspace.preview_002dtask_jsp._jspService(preview_002 dtask_jsp.java:352) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at
Re: [Dspace-tech] Publication Date Metadata
Hi Sebastien, After further investigation, this sounds like a bug in the JSPUI specifically. It does NOT occur in the XMLUI, but seems to only occur with a combination of JSPUI + Initial Questions + Workflow approval steps. I've logged it at: https://jira.duraspace.org/browse/DS-2043 We'll have to find someone to look into it and resolve it. - Tim On 6/27/2014 10:15 AM, Tim Donohue wrote: Hi Sebastien, OK, now I think I'm finally understanding things...sorry, it was not initially clear what your goal was and how you were getting this error. It sounds like you're hitting an error during the *Workflow Approval Steps* after you've re-enabled the Initial Questions step. I need to dig in deeper here, but it's possible there's a bug here that we've overlooked. - Tim On 6/27/2014 9:46 AM, Sebastien Ival wrote: Hi Tim, The default setup is what we are looking at. Users have submit theses = original work. So the users should not have to set this date. It should be automated as per version 3.2. Once we did the upgrade from 3.2 to 4.1, submitting a new thesis would result in a blank dc.date.issued. I was trying to revert for this portion to the 3.2 behavior. It seems to me that adding the initial questions does not fix this. Are you trying to set dc.date.issued to today's date at all times? Yes, this is the behavior we would like to see. What is the reason why you'd rather your submitters not be required to specify the dc.date.issued themselves (which is the default setting in DSpace 4.x)? They are submitting original work. You did not assume wrongly. I am trying (unsuccessfully) to revert to the 3.2 behaviour. Thanks for your help. This is really appreciated. -Original Message- From: Tim Donohue [mailto:tdono...@duraspace.org] Sent: June-27-14 10:37 AM To: Sebastien Ival; dspace-tech@lists.sourceforge.net Cc: Trevor Wilson Subject: Re: [Dspace-tech] Publication Date Metadata Hi Sebastien and Trevor, Maybe I've misunderstood things. It might help to take a step back. What is the setup you are trying to achieve in the DSpace submission steps? In other words, what is your use case here? As you mentioned, it's very possible the Initial Question step doesn't meet your use case. If so, it might be good to clarify how you want the submission forms to act, e.g. Are you trying to set dc.date.issued to today's date at all times? What is the reason why you'd rather your submitters not be required to specify the dc.date.issued themselves (which is the default setting in DSpace 4.x)? It's harder for us to debug this issue without a better understanding of what it is you are trying to achieve. It sounds like I had wrongly assumed you just wanted the same setup as in DSpace 3 (which is why I recommended just re-enabling Initial Questions). - Tim On 6/27/2014 9:14 AM, Sebastien Ival wrote: Hi Tim, I have two points to make 1) I think as mentioned in https://jira.duraspace.org/browse/DS-1655, the initial question step is a bit unclear and is now handled as part of the submission process. So having to re-enable it feels like going backward. I don't think the two should be hooked together. 2) To have the question The item has been published or publicly distributed before showing up, I also need to add dc.identifier.citation and dc.publisher. The field only shows up, if you answer yes to the question and you can set all of these values otherwise, it still look like the date is not being set. As when I try to take the task I get an internal server error with : -- Method: POST -- Parameters were: -- submit_claim: Take Task -- workflow_id: 186 -- step: 0 org.apache.jasper.JasperException: java.lang.NullPointerException at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Caused by: java.lang.NullPointerException at org.dspace.content.DCDate.getMonthUTC(DCDate.java:368) at org.dspace.content.DCDate.displayUTCDate(DCDate.java:520) at org.dspace.content.DCDate.displayDate(DCDate.java:487) at org.dspace.app.webui.util.UIUtil.displayDate(UIUtil.java:249) at org.dspace.app.webui.jsptag.ItemTag.render(ItemTag.java:541) at org.dspace.app.webui.jsptag.ItemTag.doStartTag(ItemTag.java:289) at org.apache.jsp.mydspace.preview_002dtask_jsp._jspService(preview_002dtask_jsp.java:352) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:432) ... 44 more This makes me think the dc.date.issued is still blank. Any ideas ? Sebastien Original Message From: Tim Donohue tdono...@duraspace.org Sent: Thursday, June 26, 2014 10:03 AM To: Trevor Wilson;
Re: [Dspace-tech] Publication Date Metadata
Hello,
We've encountered the error reported in Sebastien's point (2) below. It occurs
when a reviewer tries to preview a workflow task. If the
webui.itemdisplay.default config line includes a date field but no value was
entered in the submission form, ItemTag.java fails when trying to display the
date.
The error won't happen if you set the given date field to required in the
submission form because the submitter must enter a date to get it out of
his/her workspace. I can confirm that dc.date.issued is not required nor set
by default. We use dc.date.created.
Here's the workaround that I used (around line 540 of ItemTag.java in the 4.0
code):
else if (isDate)
{
DCDate dd = new DCDate(values[j].value);
// Parse the date
if
(!dd.toString().equals(null)) {
out.print(UIUtil.displayDate(dd, false, false,
(HttpServletRequest)pageContext.getRequest()));
}
}
Note sure if that's the best solution but it works for us. I hope this helps.
Anthony
-Original Message-
From: Sebastien Ival [mailto:sebastien.i...@rmc.ca]
Sent: Friday, June 27, 2014 10:47 AM
To: Tim Donohue; dspace-tech@lists.sourceforge.net
Cc: Trevor Wilson
Subject: Re: [Dspace-tech] Publication Date Metadata
Hi Tim,
The default setup is what we are looking at. Users have submit theses =
original work. So the users should not have to set this date. It should be
automated as per version 3.2.
Once we did the upgrade from 3.2 to 4.1, submitting a new thesis would result
in a blank dc.date.issued.
I was trying to revert for this portion to the 3.2 behavior. It seems to me
that adding the initial questions does not fix this.
Are you trying to set dc.date.issued to today's date at all times?
Yes, this is the behavior we would like to see.
What is the reason why you'd rather your submitters not be required to
specify the dc.date.issued themselves (which is the default setting in
DSpace 4.x)?
They are submitting original work.
You did not assume wrongly. I am trying (unsuccessfully) to revert to the 3.2
behaviour.
Thanks for your help.
This is really appreciated.
-Original Message-
From: Tim Donohue [mailto:tdono...@duraspace.org]
Sent: June-27-14 10:37 AM
To: Sebastien Ival; dspace-tech@lists.sourceforge.net
Cc: Trevor Wilson
Subject: Re: [Dspace-tech] Publication Date Metadata
Hi Sebastien and Trevor,
Maybe I've misunderstood things. It might help to take a step back. What is the
setup you are trying to achieve in the DSpace submission steps?
In other words, what is your use case here?
As you mentioned, it's very possible the Initial Question step doesn't meet
your use case. If so, it might be good to clarify how you want the submission
forms to act, e.g.
Are you trying to set dc.date.issued to today's date at all times?
What is the reason why you'd rather your submitters not be required to specify
the dc.date.issued themselves (which is the default setting in DSpace 4.x)?
It's harder for us to debug this issue without a better understanding of what
it is you are trying to achieve. It sounds like I had wrongly assumed you just
wanted the same setup as in DSpace 3 (which is why I recommended just
re-enabling Initial Questions).
- Tim
On 6/27/2014 9:14 AM, Sebastien Ival wrote:
Hi Tim,
I have two points to make
1) I think as mentioned in https://jira.duraspace.org/browse/DS-1655, the
initial question step is a bit unclear and is now handled as part of the
submission process. So having to re-enable it feels like going backward. I
don't think the two should be hooked together.
2) To have the question The item has been published or publicly distributed
before showing up, I also need to add dc.identifier.citation and
dc.publisher. The field only shows up, if you answer yes to the question and
you can set all of these values otherwise, it still look like the date is not
being set.
As when I try to take the task I get an internal server error with :
-- Method: POST
-- Parameters were:
-- submit_claim: Take Task
-- workflow_id: 186
-- step: 0
org.apache.jasper.JasperException: java.lang.NullPointerException
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:744)
Caused by: java.lang.NullPointerException
at org.dspace.content.DCDate.getMonthUTC(DCDate.java:368)
at org.dspace.content.DCDate.displayUTCDate(DCDate.java:520)
at org.dspace.content.DCDate.displayDate(DCDate.java:487)
at org.dspace.app.webui.util.UIUtil.displayDate(UIUtil.java:249)
at org.dspace.app.webui.jsptag.ItemTag.render(ItemTag.java:541)
at org.dspace.app.webui.jsptag.ItemTag.doStartTag(ItemTag.java:289)
at
[Dspace-tech] DSpace Distribution License Page Error
Folks, I trust all is well. I tried to send this message earlier but it did not seem to go through. I am resending it without any attachments. I have installed DSpace 4.1 on my local laptop and I am having issues when I click on the I Grant the License the server just hangs. I looked at the debug log and the last entry is: 2014-06-27 09:57:03,580 DEBUG org.dspace.storage.rdbms.DatabaseManager @ Running query SELECT * FROM Handle WHERE resource_type_id = ? AND resource_id = ? with parameters: 2,22 When I looked at the Handle table there is no entry that has a resource_id of 22. Here is my server information: Tomcat Version: Apache Tomcat/7.0.54 JVM Version: 1.7.0_60-b19 OS Name: Windows 8.1 OS Version 6.3 OS Architecture amd64 Database: Postgres 9.3 Here are some additional Java/Catalina settings I altered: CATALINA_OPTS: -XX:+CMSClassUnloadingEnabled -XX:+CMSPermGenSweepingEnabled JAVA_OPTS: -Xms256m -Xmx6096m -Dfile.encoding=UTF-8 -XX:+UseParallelGC -XX:SurvivorRatio=6 -XX:PermSize=164m Can you please let me know what I am doing wrong? Thanks in advance for any help. Andy -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] index-lucene-update
Ok, I'm actually not sure I need to run this. But it is strange that it failed.
This is my situation. I would like to have the lucene index kept
updated because:
(1) I'm still using ArtifactBrowse aspect:
aspect name=Artifact Browser
path=resource://aspects/ArtifactBrowser/ /
(2) I'm using SRW and it has an interface with lucene rather than discovery.
So what I think I need to do to have lucene index kept current ( just
for searching ) is to run
(1) have this in dspace.cfg
event.dispatcher.default.consumers = search, versioning, discovery,
eperson, harvester
(2) When I release the dspace 4.1 code run this:
./dspace index-lucene-init
AND
(3) run this as a cron job nightly:
./dspace filter-media
Does this make sense?
My only problem now is that when filter-media goes to update the
indecies, I get a whole bunch of these errors:
2014-06-27 12:42:36,344 ERROR org.dspace.search.DSIndexer @
java.io.FileNotFoundException:
/dspace/repository/dev/search/_68y0_Lucene41_0.tip (Too many open
files)
Any guidance with this will be greatly appreciated.
-Jose
(1) ./dspace index-lucene-init
On Fri, Jun 27, 2014 at 11:47 AM, Jose Blanco blan...@umich.edu wrote:
I just checked the API documentation, and it says:
Class MultiFields
public static Bits getLiveDocs(IndexReader reader)
Returns a single Bits instance for this reader, merging live Documents
on the fly. This method will return null if the reader has no
deletions.
Should there be a check for null?
On Fri, Jun 27, 2014 at 11:40 AM, Jose Blanco blan...@umich.edu wrote:
I just ran index-lucene-init and it completed successfully, but when I
try to run
index-lucene-update, it blows up at where I have ():
*/
public static void cleanIndex(Context context) throws IOException,
SQLException {
IndexReader reader = DSQuery.getIndexReader();
Bits liveDocs = MultiFields.getLiveDocs(reader);
for(int i = 0 ; i reader.numDocs(); i++)
{
() if (!liveDocs.get(i))
The error I'm getting is
Exception: null
java.lang.NullPointerException
at org.dspace.search.DSIndexer.cleanIndex(DSIndexer.java:616)
I know reader is not null, but liveDocs must be, but why?
-Jose
--
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] Problems with solr/full text
Hi Helix84 Thanks, you were absolutely correct the downgrade was flawless, and once I rebuilt the discovery index (and OAI) everything was working. Ill put up a test machine for the snapshot and see if the error re-occurs, if so I'll be sure to jira it. Robin On 27 Jun 2014, at 9:02 pm, helix84 heli...@centrum.sk wrote: Hi Robin, sorry, I don't know what's wrong with fulltext in Solr but be sure to file a Jira issue. Downgrading to DSpace 4 should be painless so far. There were no DB changes and no Solr schema changes. There aren't many new major features. There was an upgrade to OAI, so after you downgrade, reimport the OAI index (oai import -c) just to be sure. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- Open source business process management suite built on Java and Eclipse Turn processes into business applications with Bonita BPM Community Edition Quickly connect people, data, and systems into organized workflows Winner of BOSSIE, CODIE, OW2 and Gartner awards http://p.sf.net/sfu/Bonitasoft ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
