Hi,
Did you try to put your admin user as reviewer as well?
Regards
Luiz
Em 25/02/2016 17:15, escreveu:
> Hi,
>
> [Context: Dspace XMLUI 5.4 (Mirage2)]
>
> Admin can not delete submissions in workflow. This problem has been there
> since ages (we had the same limitation with version 1.8.2).
On the front page where it says "Communities in DSpace"
Select a community to browse its collections.
X
X
X
X
I'd like to display the image associated with the collection rather than
the text...
Thanks for suggestions!
--
You received this message because you are subscribed to the Google Gro
Hi,
[Context: Dspace XMLUI 5.4 (Mirage2)]
Admin can not delete submissions in workflow. This problem has been there
since ages (we had the same limitation with version 1.8.2). I just made
sure I got the same behavior in the demo site (http://demo.dspace.org/xmlui)
before posting here.
It's e
Thanks Andrea
четверг, 25 февраля 2016 г., 22:38:08 UTC+2 пользователь 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 t
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 --
created this as JIRA for this as well
https://jira.duraspace.org/browse/DS-3082
if somebody has a suggestion how to remedy this - please let me know
when running fresh install in dspace 5 with oracle I get errors
I looked into the details of creating bitstreamformatregistry entries:
Database
Tim, Just wanted to let you know I just tested filter-media (without the
need of my extra code in MediaFiltermanager.java) and the lucene and solr
indecies were both updated. I was able to find the item I was looking
for. Thanks again.
-Jose
On Thu, Feb 25, 2016 at 12:02 PM, Jose Blanco wrote:
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 U
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 al
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
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, discov
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
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://deepb
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
d
torstai 25. helmikuuta 2016 13.46.28 UTC+2 Claudia Jürgen kirjoitti:
>
> 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 cha
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
Ok, digging into the source code I found (thanks to jkesanie):
dspace-xmlui...UploadStep.java: boolean disableFileEditing = (submissionInfo
.isInWorkflow()) && !ConfigurationManager.getBooleanProperty("workflow",
"reviewer.file-edit");
So it seems to be configurable, intended behaviour, although
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
n
18 matches
Mail list logo
