R: [dspace-tech] DSpace-CRIS: Internal error

2016-02-25 Thread a.bollini 


Hi Vladimir,you need to add the following parameter to the tomcat startup
-Dorg.apache.el.parser.SKIP_IDENTIFIER_CHECK=true  

Please note that dspace-cris 5.4.0 is out, you can easily upgrade to the new 
version.Andrea

Inviato dal mio dispositivo Samsung

 Messaggio originale 
Da: Vladimir Svyatoshenko  
Data: 25/02/2016  19:49  (GMT+01:00) 
A: DSpace Technical Support  
Oggetto: [dspace-tech] DSpace-CRIS: Internal error 

Hi,

I install dspace-cris 5.2.1:

1. Edit build.properties
2. createdb
3. mvn package
4. ant flesh-install
5. chown -R tomcat8.tomcat8 /dspace
6. chmod -R a+r,a+w,a+X /dspace
7. dspace create-administrator 
8. start tomcat
9. dspace database install-example-cris-base
10. Login
11. Administrative UI --> My DSpace --> Create Researcher profile -- Ok
12. View researcher profile --> Edit researcher page -- Internal error 

dspace.log:
javax.servlet.ServletException: org.apache.jasper.JasperException: 
/dspace-cris/jdyna/rpDataEditForm.jsp (line: 663, column: 4) 
"${researcher:isThereMetadataNoEditable(holder.shortName, holder.class)}" 
contains invalid expression(s): javax.el.ELException: Failed to parse the 
expression [${researcher:isThereMetadataNoEditable(holder.shortName, 
holder.class)}]
    at 
org.dspace.utils.servlet.DSpaceWebappServletFilter.doFilter(DSpaceWebappServletFilter.java:85)
    at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239)
    at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at 
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:721)
    at 
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:466)
    at 
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:391)
    at 
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:318)
    at 
org.springframework.web.servlet.view.InternalResourceView.renderMergedOutputModel(InternalResourceView.java:238)
    at 
org.springframework.web.servlet.view.AbstractView.render(AbstractView.java:262)
    at 
org.springframework.web.servlet.DispatcherServlet.render(DispatcherServlet.java:1180)
    at 
org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:950)
    at 
org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:852)
    at 
org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:882)
    at 
org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:778)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:618)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:725)
    at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:291)
    at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
    at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239)
    at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at 
org.dspace.app.webui.cris.filter.DSpaceContextCleanupFilter.doFilter(DSpaceContextCleanupFilter.java:54)
    at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239)
    at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at 
org.dspace.app.webui.filter.RegisteredOnlyFilter.doFilter(RegisteredOnlyFilter.java:66)
    at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239)
    at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at 
org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:88)
    at 
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
    at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239)
    at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at 
org.dspace.utils.servlet.DSpaceWebappServletFilter.doFilter(DSpaceWebappServletFilter.java:78)
    at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239)
    at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:219)
    at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:106)
    at 
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:506)
    at

[dspace-tech] DSpace-CRIS: Internal error

2016-02-25 Thread Vladimir Svyatoshenko 
Hi,

I install dspace-cris 5.2.1:

1. Edit build.properties
2. createdb
3. mvn package
4. ant flesh-install
5. chown -R tomcat8.tomcat8 /dspace
6. chmod -R a+r,a+w,a+X /dspace
7. dspace create-administrator 
8. start tomcat
9. dspace database install-example-cris-base
10. Login
11. Administrative UI --> My DSpace --> Create Researcher profile -- Ok
12. View researcher profile --> Edit researcher page -- Internal error 

dspace.log:
javax.servlet.ServletException: org.apache.jasper.JasperException: 
/dspace-cris/jdyna/rpDataEditForm.jsp (line: 663, column: 4) 
"${researcher:isThereMetadataNoEditable(holder.shortName, holder.class)}" 
contains invalid expression(s): javax.el.ELException: Failed to parse the 
expression [${researcher:isThereMetadataNoEditable(holder.shortName, 
holder.class)}]
at 
org.dspace.utils.servlet.DSpaceWebappServletFilter.doFilter(DSpaceWebappServletFilter.java:85)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at 
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:721)
at 
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:466)
at 
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:391)
at 
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:318)
at 
org.springframework.web.servlet.view.InternalResourceView.renderMergedOutputModel(InternalResourceView.java:238)
at 
org.springframework.web.servlet.view.AbstractView.render(AbstractView.java:262)
at 
org.springframework.web.servlet.DispatcherServlet.render(DispatcherServlet.java:1180)
at 
org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:950)
at 
org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:852)
at 
org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:882)
at 
org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:778)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:618)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:725)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:291)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at 
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at 
org.dspace.app.webui.cris.filter.DSpaceContextCleanupFilter.doFilter(DSpaceContextCleanupFilter.java:54)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at 
org.dspace.app.webui.filter.RegisteredOnlyFilter.doFilter(RegisteredOnlyFilter.java:66)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at 
org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:88)
at 
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at 
org.dspace.utils.servlet.DSpaceWebappServletFilter.doFilter(DSpaceWebappServletFilter.java:78)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239)
at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:219)
at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:106)
at 
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:506)
at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:142)
at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)
at 
org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:610)
at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88)
at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:537)
at 
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1081)
at

Re: [dspace-tech] Harvesting EPrints repository from DSpace

2016-02-25 Thread Franziska Ackermann 

Hi,

What worked for me was the solution described under the link you sent below.
After the file "OAI_Bibliography.pm" had been removed from the E-Prints 
Repository, DSpace could harvest the records via oai_dc.


Best regards,
Franziska


Am 25.02.2016 um 17:12 schrieb amgcia...@gmail.com:

Hi all,

We are running a DSpace repository and would like to harvest metadata 
from an EPrints repository.


We have successfully configured a collection that harvests its content 
from an external source, in this case an EPrints repository OAI feed 
(selecting an specific OAI set). DSpace connects successfully to the 
EPrints OAI server, however it’s only retrieving empty metadata 
records. We are experiencing the same issue as described here 
.


We have looked at the DSpace code and located the issue: DSpace’s 
harvester module requests first a list of supported metadata formats 
to find the metadata prefix that the target repository uses for the 
selected metadata schema (http://www.openarchives.org/OAI/2.0/oai_dc). 
Internally this is done by iterating through the results of the 
ListMetadataFormats query and returns the metadataPrefix for the first 
metadataFormat that matches the selected metadata schema.


What happens in this case is that EPrints has more than one entry for 
the supported metadata formats using OAI_DC (oai_bibl and oai_dc 
prefixes):


…

  oai_bibl
http://www.openarchives.org/OAI/2.0/oai_dc.xsd
http://www.openarchives.org/OAI/2.0/oai_dc/


  oai_dc
http://www.openarchives.org/OAI/2.0/oai_dc.xsd
http://www.openarchives.org/OAI/2.0/oai_dc/

…

DSpace’s harvester is then selecting the first metadataPrefix, i.e. 
oai_bibl, for which EPrints is returning records with no metadata.


Just wondering if anyone has experienced the same issue, and if so, 
how did they solve it. Any help/suggestions are very much appreciated. 
Ideally we would like to avoid customising DSpace just to fix this, so 
I’m wondering whether there’s an easy way to fix this through EPrints 
configuration: e.g. disabling oai_bibl or something similar.


Many thanks and kind regards,
Agustina
--
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 dspace-tech+unsubscr...@googlegroups.com 
.
To post to this group, send email to dspace-tech@googlegroups.com 
.

Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.


--
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 dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] updating lucene search.

2016-02-25 Thread Jose Blanco 
Great.  I already have this setup and I remember testing it using the UI
and it did work. But I thought it did not affect filter-media processing.
So I'm probably fine as is.  I will do some checking to confirm that.
Thank you

-Jose

On Thu, Feb 25, 2016 at 11:52 AM, Tim Donohue 
wrote:

> Hi Jose,
>
> Your code likely would still work, but it may be easier to simply enable
> the "search" index event consumer (this is the one that refreshes a Lucene
> index).
>
> By default, 5.x has this list of event consumers enabled in dspace.cfg:
>
> event.dispatcher.default.consumers = versioning, discovery, eperson,
> harvester
>
> The "discovery" consumer ensures Discovery (Solr) reindexes when changes
> occur. You could just append the "search" consumer to similarly notify
> Lucene, e.g.
>
> event.dispatcher.default.consumers = versioning, discovery, eperson,
> harvester, search
>
> Adding "search" to that list triggers this SearchConsumer whenever changes
> to Community, Collection & Items occur (including when filter-media runs)
>
> https://github.com/DSpace/DSpace/blob/dspace-5_x/dspace-api/src/main/java/org/dspace/search/SearchConsumer.java
>
> - Tim
>
>
> On 2/25/2016 8:55 AM, Jose Blanco wrote:
>
> Thanks Tim for your response. What I have done is I have left the advance
> page from previous Dspace instances with Lucene, but everything else is
> Discovery. This page uses lucene:
>
> https://deepblue.lib.umich.edu/advanced-search
>
> and so does the box on the menu bar from the main page:
>
> https://deepblue.lib.umich.edu/
>
> So I'm using some old code to get this functionality.
>
> Now, in the past I had the code from my previous email in the filter-media
> so that the full text search for the lucene index would be updated.  When I
> did the last code merge I chopped that code out, and am now realizing that
> I need to put it back in if I the lucene full text search to work. What do
> you think?
>
> Thanks again!
> Jose
>
>
>
>
>
> On Thu, Feb 25, 2016 at 9:32 AM, Tim Donohue 
> wrote:
>
>> Hi Jose,
>>
>> Could you describe your setup more?  It's not actually possible (well not
>> recommended) to run Discovery (which uses Apache Solr) AND Lucene (which is
>> a separate search interface) simultaneously.  Are you running Discovery, or
>> are you running the traditional Lucene-based search?  By default, DSpace
>> 5.x uses Discovery.
>>
>> https://wiki.duraspace.org/display/DSDOC5x/Discovery
>>
>> If you are running Discovery, then it is notified of any updates to
>> items, etc. and will reindex individual items when notified.  There's no
>> need to add any special code for that.
>>
>> If you are still using Lucene, you might want to think about whether it's
>> worth moving to just using Discovery.  In 5.x, we deprecated Lucene
>> searching, and it is being removed entirely in 6.x (coming soon).  So,
>> while you can still use Lucene in 5.x, you'll eventually need to move to
>> using Discovery (with Solr) once 6.x is released.
>>
>> - Tim
>>
>>
>> On 2/24/2016 3:46 PM, Jose Blanco wrote:
>>
>> I am currently using lucene and discovery in 5.1.  In 4.2 I had this bit
>> of code in MediaFilterManager.java so that when ./dsapce filter-media ran
>> the lucene index would be updated.  I wonder if it will work in 5.1 and if
>> perhaps there is a better way to do it.  This is the code I had:
>>
>> if (updateIndex)
>> {
>> if (!isQuiet)
>> {
>> System.out.println("Updating search index:");
>> }
>> DSIndexer.setBatchProcessingMode(true);
>> try
>> {
>> DSIndexer.updateIndex(c);
>> }
>> finally
>> {
>> DSIndexer.setBatchProcessingMode(false);
>> }
>> }
>>
>> Thank you!
>> Jose
>> --
>> 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 dspace-tech+unsubscr...@googlegroups.com.
>> To post to this group, send email to 
>> dspace-tech@googlegroups.com.
>> Visit this group at https://groups.google.com/group/dspace-tech.
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>> --
>> Tim Donohue
>> Technical Lead for DSpace & DSpaceDirect
>> DuraSpace.org | DSpace.org | DSpaceDirect.org
>>
>> --
>> 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 dspace-tech+unsubscr...@googlegroups.com.
>> To post to this group, send email to 
>> dspace-tech@googlegroups.com.
>> Visit this group at https://groups.google.com/group/dspace-tech.
>> For more options, visit

Re: [dspace-tech] updating lucene search.

2016-02-25 Thread Tim Donohue 

Hi Jose,

Your code likely would still work, but it may be easier to simply enable 
the "search" index event consumer (this is the one that refreshes a 
Lucene index).


By default, 5.x has this list of event consumers enabled in dspace.cfg:

event.dispatcher.default.consumers = versioning, discovery, eperson, 
harvester


The "discovery" consumer ensures Discovery (Solr) reindexes when changes 
occur. You could just append the "search" consumer to similarly notify 
Lucene, e.g.


event.dispatcher.default.consumers = versioning, discovery, eperson, 
harvester, search


Adding "search" to that list triggers this SearchConsumer whenever 
changes to Community, Collection & Items occur (including when 
filter-media runs)

https://github.com/DSpace/DSpace/blob/dspace-5_x/dspace-api/src/main/java/org/dspace/search/SearchConsumer.java

- Tim

On 2/25/2016 8:55 AM, Jose Blanco wrote:
Thanks Tim for your response. What I have done is I have left the 
advance page from previous Dspace instances with Lucene, but 
everything else is Discovery. This page uses lucene:


https://deepblue.lib.umich.edu/advanced-search

and so does the box on the menu bar from the main page:

https://deepblue.lib.umich.edu/

So I'm using some old code to get this functionality.

Now, in the past I had the code from my previous email in the 
filter-media so that the full text search for the lucene index would 
be updated.  When I did the last code merge I chopped that code out, 
and am now realizing that I need to put it back in if I the lucene 
full text search to work. What do you think?


Thanks again!
Jose





On Thu, Feb 25, 2016 at 9:32 AM, Tim Donohue > wrote:


Hi Jose,

Could you describe your setup more?  It's not actually possible
(well not recommended) to run Discovery (which uses Apache Solr)
AND Lucene (which is a separate search interface) simultaneously. 
Are you running Discovery, or are you running the traditional

Lucene-based search?  By default, DSpace 5.x uses Discovery.

https://wiki.duraspace.org/display/DSDOC5x/Discovery

If you are running Discovery, then it is notified of any updates
to items, etc. and will reindex individual items when notified. 
There's no need to add any special code for that.


If you are still using Lucene, you might want to think about
whether it's worth moving to just using Discovery. In 5.x, we
deprecated Lucene searching, and it is being removed entirely in
6.x (coming soon).  So, while you can still use Lucene in 5.x,
you'll eventually need to move to using Discovery (with Solr) once
6.x is released.

- Tim


On 2/24/2016 3:46 PM, Jose Blanco wrote:

I am currently using lucene and discovery in 5.1.  In 4.2 I had
this bit of code in MediaFilterManager.java so that when ./dsapce
filter-media ran the lucene index would be updated.  I wonder if
it will work in 5.1 and if perhaps there is a better way to do
it.  This is the code I had:

if (updateIndex)
{
if (!isQuiet)
{
System.out.println("Updating search index:");
}
DSIndexer.setBatchProcessingMode(true);
try
{
DSIndexer.updateIndex(c);
}
finally
{
DSIndexer.setBatchProcessingMode(false);
}
}

Thank you!
Jose
-- 
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 dspace-tech+unsubscr...@googlegroups.com
.
To post to this group, send email to dspace-tech@googlegroups.com
.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.


-- 
Tim Donohue

Technical Lead for DSpace & DSpaceDirect
DuraSpace.org | DSpace.org | DSpaceDirect.org

-- 
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 dspace-tech+unsubscr...@googlegroups.com
.
To post to this group, send email to dspace-tech@googlegroups.com
.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.




--
Tim Donohue
Technical Lead for DSpace & DSpaceDirect
DuraSpace.org | DSpace.org | DSpaceDirect.org

--
You received this message because you are subscribed to the Google Groups "DSpace 
Technical Support" group.
To

Re: [dspace-tech] updating lucene search.

2016-02-25 Thread Jose Blanco 
Thanks Tim for your response. What I have done is I have left the advance
page from previous Dspace instances with Lucene, but everything else is
Discovery. This page uses lucene:

https://deepblue.lib.umich.edu/advanced-search

and so does the box on the menu bar from the main page:

https://deepblue.lib.umich.edu/

So I'm using some old code to get this functionality.

Now, in the past I had the code from my previous email in the filter-media
so that the full text search for the lucene index would be updated.  When I
did the last code merge I chopped that code out, and am now realizing that
I need to put it back in if I the lucene full text search to work. What do
you think?

Thanks again!
Jose





On Thu, Feb 25, 2016 at 9:32 AM, Tim Donohue  wrote:

> Hi Jose,
>
> Could you describe your setup more?  It's not actually possible (well not
> recommended) to run Discovery (which uses Apache Solr) AND Lucene (which is
> a separate search interface) simultaneously.  Are you running Discovery, or
> are you running the traditional Lucene-based search?  By default, DSpace
> 5.x uses Discovery.
>
> https://wiki.duraspace.org/display/DSDOC5x/Discovery
>
> If you are running Discovery, then it is notified of any updates to items,
> etc. and will reindex individual items when notified.  There's no need to
> add any special code for that.
>
> If you are still using Lucene, you might want to think about whether it's
> worth moving to just using Discovery.  In 5.x, we deprecated Lucene
> searching, and it is being removed entirely in 6.x (coming soon).  So,
> while you can still use Lucene in 5.x, you'll eventually need to move to
> using Discovery (with Solr) once 6.x is released.
>
> - Tim
>
>
> On 2/24/2016 3:46 PM, Jose Blanco wrote:
>
> I am currently using lucene and discovery in 5.1.  In 4.2 I had this bit
> of code in MediaFilterManager.java so that when ./dsapce filter-media ran
> the lucene index would be updated.  I wonder if it will work in 5.1 and if
> perhaps there is a better way to do it.  This is the code I had:
>
> if (updateIndex)
> {
> if (!isQuiet)
> {
> System.out.println("Updating search index:");
> }
> DSIndexer.setBatchProcessingMode(true);
> try
> {
> DSIndexer.updateIndex(c);
> }
> finally
> {
> DSIndexer.setBatchProcessingMode(false);
> }
> }
>
> Thank you!
> Jose
> --
> 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 dspace-tech+unsubscr...@googlegroups.com.
> To post to this group, send email to dspace-tech@googlegroups.com.
> Visit this group at https://groups.google.com/group/dspace-tech.
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> Tim Donohue
> Technical Lead for DSpace & DSpaceDirect
> DuraSpace.org | DSpace.org | DSpaceDirect.org
>
> --
> 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 dspace-tech+unsubscr...@googlegroups.com.
> To post to this group, send email to dspace-tech@googlegroups.com.
> Visit this group at https://groups.google.com/group/dspace-tech.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Re: Possible bug in DSpace 5.4 with batch metadata import, workflow edit metadata and file upload

2016-02-25 Thread Claudia Jürgen 

Hello Ilja,

I think this is correct behaviour especially with regards to the legal
aspects.
The submitter grants the license agreement for the file(s) in the item
he submitted.
So no one should be able to change these.

Claudia Jürgen


Am 25.02.2016 um 11:26 schrieb Ilja Sidoroff:

It seems that Sherpa/Romeo isn't the thing to blame (expect for perhaps
showing up in the wrong page). There doesn't seem to be a possibility to
upload new files when reviewing and editing items in the workflow phase. It
seems that the code for initial submission and reviewing are almost, but
not quite the same. Has anyone got any pointers, where I this happens in
the source code, so I could take a look?

I will probably be filing a bug on this, after I pinpoint the cause, as I
don't think this is the intended behaviour.



--
Claudia Juergen
Eldorado

Technische Universität Dortmund
Universitätsbibliothek
Vogelpothsweg 76
44227 Dortmund

Tel.: +49 231-755 40 43
Fax: +49 231-755 40 32
claudia.juer...@tu-dortmund.de
www.ub.tu-dortmund.de

Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie ist 
ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für diese 
E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender und 
vernichten Sie diese Mail. Vielen Dank.
Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen 
ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher Schriftform 
(mit eigenhändiger Unterschrift) oder durch Übermittlung eines solchen 
Schriftstücks per Telefax erfolgen.

Important note: The information included in this e-mail is confidential. It is 
solely intended for the recipient. If you are not the intended recipient of 
this e-mail please contact the sender and delete this message. Thank you. 
Without prejudice of e-mail correspondence, our statements are only legally 
binding when they are made in the conventional written form (with personal 
signature) or when such documents are sent by fax.

--
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 dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Re: Possible bug in DSpace 5.4 with batch metadata import, workflow edit metadata and file upload

2016-02-25 Thread Ilja Sidoroff 
It seems that Sherpa/Romeo isn't the thing to blame (expect for perhaps 
showing up in the wrong page). There doesn't seem to be a possibility to 
upload new files when reviewing and editing items in the workflow phase. It 
seems that the code for initial submission and reviewing are almost, but 
not quite the same. Has anyone got any pointers, where I this happens in 
the source code, so I could take a look?

I will probably be filing a bug on this, after I pinpoint the cause, as I 
don't think this is the intended behaviour.

-- 
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 dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.