On 14 January 2015 at 01:23, Monika C. Mevenkamp moni...@princeton.edu
wrote:
Is it true that the database browse indexes become obsolete when using
discovery/solr ?
Hi Monica
Yes. See: http://wiki.lib.sun.ac.za/index.php/SUNScholar/Browse_Indexes
Cheers
hg
*Hilton Gibson*
Ubuntu
I think it is bad idea to migrate using SAF. We have do it with our archive
and we found, that this way does not save bitstream order! For example, you
have an item http://yourreponame.org/bitstream/123456789/5/file.pdf when you
export and import again, you will get
Hey Bruno,
Sorry for the delay, very busy.
Also, sorry that the documentation for DSpace 5 REST API isn't complete
yet. Feel free to contribute as you discover how things work.
It looks like you need to first create the item, as you are currently doing
it:
POST
Thanks both of you. I am going to improve it with my next pull request.
I did the recreation of the master branch and will use pull instead of
fetch.
Regards Christian
Am 13.01.2015 um 08:59 schrieb Àlex Magaz Graça:
El 12/01/15 a les 15:55, Christian Scheible ha escrit:
Hi Helix,
I think
Change the port number in the following properties and restart your
servlet container:
search.server in [dspace]/config/modules/discovery.cfg
solr.url in [dspace]/config/modules/oai.cfg
server in [dspace]/config/modules/solr-statistics.cfg
solr.authority.server in [dspace]/config/dspace.cfg
Hi All
Just to add - our upgrade to 4.2 from 3.2 involved fixing a lot of
data-issued metadata.
The SOLR discovery date-issued index was a mess after the upgrade.
Updating the existing curation task to check metadata, with a date-issued
format would help a lot.
Cheers
hg
*Hilton Gibson*
Ubuntu
Dear Pablo,
Thanks again.
It would be simply /jspui/cris/rp/rp5?open=journal
At the time being, I have force generating the anchor
/jspui/cris/rp/rp0005?open=journal#dspaceitems to make the jump succeed.
Best Regards,
Alexander Wong
On Tue, Jan 13, 2015 at 8:21 PM, Pablo Buenaposada
On Tue, Jan 13, 2015 at 9:30 AM, Hilton Gibson hilton.gib...@gmail.com wrote:
Updating the existing curation task to check metadata, with a date-issued
format would help a lot.
Hi Hilton, see DS-1775.
Regards,
~~helix84
Compulsory reading: DSpace Mailing List Etiquette
Oliver
look for the IP Authentication chapter in the DSPACE documentation for your
version for details
We use IP authentication so that the system will try it first - before it moves
on to the next method:
This is done in dspace/config/modules/authentication.cfg
About issue 1, yes, seems that's not working well, will look into it.
Issue 2 it's strange, mine is working well, I don't know if I forget to tell
you about more code fixes in other files, can't remember now...
Tell me what url gives you in the red section of the image attached.
I looked only briefly, the immediate problem seems to be that either the
eperson or (more likely) the workflow item is null:
https://github.com/DSpace/DSpace/blob/dspace-5.0-rc3/dspace-api/src/main/java/org/dspace/xmlworkflow/WorkflowRequirementsManager.java#L126
I don't know what it means in
Hi Ryan (and all),
Had a moment this morning to dig a little deeper here...
From what I can tell, it looks like this *may* be the result of a
flaw/bug in the logic of the Discovery Access Rights Awareness feature
(which is supposed to respect access restrictions on Items).
I believe what may
After some more investigation I found that all docs in my solr index with
search.resourcetype:2
are also
discoverable:false
I take it that those are the docs corresponding to dspace items.
What determines an item’s “discoverable” setting ?
We have a mix of openly accessible and restricted
13 matches
Mail list logo
