[Dspace-tech] Social Media integration with DSpace JSPUI
Hello Experts, We are using DSpace 5.2 JSPUI. We want to integrate Social media toolbar and functionality of adding comments / recommendations. Can somebody please guide on how to do this? Requesting help on above. Thanks, Raj -- ___ 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] help with dspace on windows
Did you deploy the jspui in the Tomcat? Em 05/08/2015 00:54, manindra manindra.gun...@gmail.com escreveu: Hi, I need a help from you...i think u can do this. Im installing dspace on centOS ...everything went fine. Java jdk, maven, ant, tomcat, postgresql...everthing installed successfully. But when i open web browser and type the localhost address with port number along with jspui. i.e., http://192.168.108.31:8080/jspui Iam getting the following error. *HTTP Status 404 - /jspui type Status report message /jspui description The requested resource is not available. Apache Tomcat/8.0.24* i have tried so many ways to rectify it though i dont have any idea on dspace. Im totally new to this environment. i couldnt get the error solved. could you please help me. i can provide the supporting files neccessary if any changes u can do to those. Thank you in advance, Manindra. -- View this message in context: http://dspace.2283337.n4.nabble.com/Dspace-tech-help-with-dspace-on-windows-tp3286924p4679106.html Sent from the DSpace - Tech mailing list archive at Nabble.com. -- ___ 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 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] costumizar jspui
Hello Tony, copy your message catalogue to [dspace-source]/dspace/modules/jspui/src/main/resources/ then build and deploy see: https://wiki.duraspace.org/display/DSDOC5x/Localization+L10n#LocalizationL10n-Wheretoedit.1 If you want to customize the pages themselves see https://wiki.duraspace.org/display/DSDOC5x/JSPUI+Configuration+and+Customization Hope this helps Claudia Jürgen Am 05.08.2015 um 00:59 schrieb Tony Junior: fiz umas alterações no arquivo Messages.properties, (mudei o texto que aparace na jspui) como faço para atualizar no Dspace estou usando a versão 5.2 -- ___ 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 -- 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...@ub.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. -- ___ 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] retrospectively assigning DOIs to live items
Hi Andrea and Pascal,
it's on my todo-list too to add it to the doi-organiser, but low. Done
the fixes for the provider though and going to make a patch for these,
as soon as I got the doi stuff locally running.
At the moment the crosswalk itself needs a bit more work.
Run it with ~16.000 documents on the test.datacite.org site and it
produced a lot of errors, especially with regards to maxOccurences
(never checked in our existing crosswalk), required attributes etc.
Nearly fixed these too and going to test it again.
I only wonder whether we should make corrections to the 2.2 kernel or
rather 3.1 which is the preferred version from DataCite:
https://schema.datacite.org/meta/kernel-3.1/doc/DataCite-MetadataKernel_v3.1.pdf
or both 2.2 for existing DSpace versions and 3.1 for future release?
Btw DataCite flags (for oai harvesters) data with the flag reference
quality. Does anyone know the quality creteria for this flag, could not
find it in their documentation?
Sunny Greetings
Claudia
Am 04.08.2015 um 01:47 schrieb Andrea Schweer:
Hi Pascal,
On 03/08/15 21:04, Becker, Pascal-Nicolas wrote:
On 03/08/15 1:48 AM, Andrea Schweer wrote:
On 03/08/15 11:16, Claudia Jürgen wrote:
yes this is right. If you enable the identifier service this will only
cover new items.
Assuming you are using the DataCite Connector, the easiest way would
be to manipulate the database (usual warnings about that) to give the
old items the status of newly items in archive:
INSERT into doi (doi_id, doi, resource_type_id, resource_id, status)
SELECT nextval('doi_seq'),
concat('YOURPREFIX/YOURNAMESPACESEPARATOR-',currval('doi_seq')), 2,
item_id, 7 FROM item WHERE in_archive=true and item_id not in (select
resource_id from doi where resource_type_id=2);
Then the cron job for the usual doi-organiser commands will pick up
the job.
Perfect, thanks a lot for that!
It should be easy to add a command in the doi-organiser that adds
those entries into the database. I just didn't had the use case and
the time. ;-)
All good :) It just wasn't obvious to me from the documentation. Perhaps
I'll have the time to change the docs / add this functionality to
doi-organiser, but no promises -- I have the use case but not
necessarily the time...
cheers,
Andrea
--
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...@ub.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.
--
___
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] REST API get object by handle
Hi Ondřej,
I see that there was a code refactoring during the development, which
successfully hit the DSpaceObject endpoints ( /items, /collections,
/communities), but missed the /handle endpoint). Unintentional caching, a
bug.
The old way we were obtaining a context in REST is this (visible in handle
code). We cache a context, hold on to it, try to use it as a
singleton-ish-thing. It was supposed to be a way to help performance at one
point, your not going back to the DB to get a new context for each request,
so you could scale higher.
try {
if(context == null || !context.isValid() ) {
context = new Context();
//Failed SQL is ignored as a failed SQL statement, prevent:
current transaction is aborted, commands ignored until end of transaction
block
context.getDBConnection().setAutoCommit(true);
}
The problem is that you hold the same DB connection for a very long time,
and similar to a transaction, that DB connection will use the state of the
database at the time it got the connection / context. So, other edits to
objects will be missed, its caches / hold stale connection, and just sucks.
After several days of tomcat running, it could also just run into some
weird issue.
The new DB connection that we figured out (Hat tip to Richard Rodgers at
OR2013 in PEI), is to properly get a new context for each request, and
properly close your context after each request. Wrapping everything in a
try, and finally helps ensure success.
try
{
context = createContext(getUser(headers));
...
finally
{
processFinally(context); ### essentially just context.abort()
}
Peter Dietz
Longsight
www.longsight.com
pe...@longsight.com
p: 740-599-5005 x809
On Tue, Jul 28, 2015 at 10:04 AM, Luiz dos Santos luiz...@gmail.com wrote:
Hi Peter,
When I hit the url:
https://demo.dspace.org/rest/handle/10673/14?expand=all it give back a
xml instead a json? I mean, should it be a json?
Thanks
Luiz
On Mon, Jul 27, 2015 at 12:37 PM, Peter Dietz pe...@longsight.com wrote:
Hi OK,
The endpoint to look up an object by its handle is
base-rest-url/handle/handle-number. So, for example:
https://demo.dspace.org/rest/handle/10673/14?expand=all
The /handle/handle-number endpoint doesn't appear to be properly
documented. Here is the HandleResource in the code.
https://github.com/DSpace/DSpace/blob/master/dspace-rest/src/main/java/org/dspace/rest/HandleResource.java#L37
It produces a rest DSpaceObject (so if the handle yields an Item, the
response is a rest Item in json/xml).
{
id: 10
name: Test submit
handle: 10673/14
type: item
link: /rest/items/10
expand:
[
0]
lastModified: 2015-07-27 11:00:18.027
...
Peter Dietz
Longsight
www.longsight.com
pe...@longsight.com
p: 740-599-5005 x809
On Fri, Jul 24, 2015 at 6:54 AM, Ondřej Košarko kosa...@ufal.mff.cuni.cz
wrote:
Hi all,
Is it currently possible, using the dspace5 rest api, to access the
items/collections/communities using handles rather than internal-ids?
I can see a workaround for items - first find-by-metadata-field. But
that seems bit cumbersome. Handles or some other PIDs are already used to
reference items*, collections, etc. and they are guaranteed not to
change.
*imagine you want to have on your personal homepage, together with PID,
some other metadata for the submission.
imagine you are using dc.relation.* (with PIDs as value) to link some of
the submissions together and are creating a visualization of the relations.
It's doable for items but there always will be at least two requests for
each, or am I missing some other way?
Regards,
OK
PS: Is it possible to have wildcards in metadataEntries? Both - keys and
values?
--
___
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 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 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] REST API get object by handle
Hi Luiz,
Getting back XML vs JSON depends on your client's Accept header. If you are
using your web browser, it has a preference to accept HTTP, XHTML, XML
before it wants to accept JSON. So, viewing endpoints in your browser,
you'll usually get back XML.
A while back I made a video where I'm using Chrome extension Advanced Rest
Client. (I also hammer the API with jmeter).
Set it as:
Accept: application/json
https://youtu.be/FYVMGLLDAUE?t=688
Peter Dietz
Longsight
www.longsight.com
pe...@longsight.com
p: 740-599-5005 x809
On Wed, Aug 5, 2015 at 1:05 PM, Peter Dietz pe...@longsight.com wrote:
Hi Ondřej,
I see that there was a code refactoring during the development, which
successfully hit the DSpaceObject endpoints ( /items, /collections,
/communities), but missed the /handle endpoint). Unintentional caching, a
bug.
The old way we were obtaining a context in REST is this (visible in handle
code). We cache a context, hold on to it, try to use it as a
singleton-ish-thing. It was supposed to be a way to help performance at one
point, your not going back to the DB to get a new context for each request,
so you could scale higher.
try {
if(context == null || !context.isValid() ) {
context = new Context();
//Failed SQL is ignored as a failed SQL statement,
prevent: current transaction is aborted, commands ignored until end of
transaction block
context.getDBConnection().setAutoCommit(true);
}
The problem is that you hold the same DB connection for a very long time,
and similar to a transaction, that DB connection will use the state of the
database at the time it got the connection / context. So, other edits to
objects will be missed, its caches / hold stale connection, and just sucks.
After several days of tomcat running, it could also just run into some
weird issue.
The new DB connection that we figured out (Hat tip to Richard Rodgers at
OR2013 in PEI), is to properly get a new context for each request, and
properly close your context after each request. Wrapping everything in a
try, and finally helps ensure success.
try
{
context = createContext(getUser(headers));
...
finally
{
processFinally(context); ### essentially just
context.abort()
}
Peter Dietz
Longsight
www.longsight.com
pe...@longsight.com
p: 740-599-5005 x809
On Tue, Jul 28, 2015 at 10:04 AM, Luiz dos Santos luiz...@gmail.com
wrote:
Hi Peter,
When I hit the url:
https://demo.dspace.org/rest/handle/10673/14?expand=all it give back a
xml instead a json? I mean, should it be a json?
Thanks
Luiz
On Mon, Jul 27, 2015 at 12:37 PM, Peter Dietz pe...@longsight.com
wrote:
Hi OK,
The endpoint to look up an object by its handle is
base-rest-url/handle/handle-number. So, for example:
https://demo.dspace.org/rest/handle/10673/14?expand=all
The /handle/handle-number endpoint doesn't appear to be properly
documented. Here is the HandleResource in the code.
https://github.com/DSpace/DSpace/blob/master/dspace-rest/src/main/java/org/dspace/rest/HandleResource.java#L37
It produces a rest DSpaceObject (so if the handle yields an Item, the
response is a rest Item in json/xml).
{
id: 10
name: Test submit
handle: 10673/14
type: item
link: /rest/items/10
expand:
[
0]
lastModified: 2015-07-27 11:00:18.027
...
Peter Dietz
Longsight
www.longsight.com
pe...@longsight.com
p: 740-599-5005 x809
On Fri, Jul 24, 2015 at 6:54 AM, Ondřej Košarko
kosa...@ufal.mff.cuni.cz wrote:
Hi all,
Is it currently possible, using the dspace5 rest api, to access the
items/collections/communities using handles rather than internal-ids?
I can see a workaround for items - first find-by-metadata-field. But
that seems bit cumbersome. Handles or some other PIDs are already used to
reference items*, collections, etc. and they are guaranteed not to
change.
*imagine you want to have on your personal homepage, together with PID,
some other metadata for the submission.
imagine you are using dc.relation.* (with PIDs as value) to link some
of the submissions together and are creating a visualization of the
relations.
It's doable for items but there always will be at least two requests
for each, or am I missing some other way?
Regards,
OK
PS: Is it possible to have wildcards in metadataEntries? Both - keys
and values?
--
___
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] How to search items by metadata using REST API?
Hi Kim,
For versioning REST API, I'm not sure of a definitive best route to get
there. A while back, for a Ruby on Rails project, one way we made a
/rest/v1 and a /rest/v2 versions of that REST API, was just make a
subfolder v1 and v2, copy and paste our entire v1 code into v2, and
then never touch v1 code again, and update the v2 code to become different.
I'd imagine jaxrs has some other graceful routes to accomplish this, but
the subfolder route is easy-ish to support and understand.
But yes. Its growing through evolution. Rather than intelligent design. ;)
Peter Dietz
Longsight
www.longsight.com
pe...@longsight.com
p: 740-599-5005 x809
On Wed, Jun 17, 2015 at 4:32 AM, Alan Orth alan.o...@gmail.com wrote:
That's interesting, Terry. I think I'll just wait until DSpace 5.0 to get
the search-by-metadata feature, as there 5.0 is already a high priority for
us for a number of other reasons as well!
Alan
On Tue, Jun 16, 2015 at 2:52 AM Terry Brady terry.br...@georgetown.edu
wrote:
Alan,
The following PR has some code that will search metadata via the API:
https://github.com/DSpace/DSpace/pull/954
I am also on 4.3, so this code is compatible with DSpace4.3.
Terry
On Thu, Jun 11, 2015 at 5:58 AM, Alan Orth alan.o...@gmail.com wrote:
Ah, it seems the `/rest/items/find-by-metadata-field` endpoint doesn't
exist in DSpace 4.x. Neither does the `/rest/login` endpoint. The docs need
to make more of a point to say which versions these are supposed to work
in... ;)
Alan
On Thu, Jun 11, 2015 at 12:24 PM Alan Orth alan.o...@gmail.com wrote:
Thanks. It seems my query is well formed but it returns an HTTP 405
Method Not Allowed response. Perhaps DSpace 4.x's REST API isn't
sufficient for the find-by-metadata-field query. Or perhaps I need to log
in as you illustrated here:
https://github.com/BrunoNZ/dspace-rest-requests
I guess I'll fork that repo and give this a more structured test. I
already found some syntax and usability bugs there (mixing sh and bash, not
reading the sourced variables, etc).
Alan
On Wed, Jun 10, 2015 at 8:30 PM, Bruno Zanette brunonzane...@gmail.com
wrote:
Hey Alan,
Take a look at the commentaries on the REST-API's documentation's
page. I've answered a similar question there.
https://wiki.duraspace.org/display/DSDOC5x/REST+API?focusedCommentId=68068154#comment-68068154
But basically, the request that you have to send is something like
this:
curl -k -4 -H accept: application/json -H Content-Type:
application/json -X POST
https://demo.dspace.org/rest/items/find-by-metadata-field; -d
'{key: dc.title,value: Test Webpage,language: en_US}'
Em qua, 10 de jun de 2015 às 14:08, Alan Orth alan.o...@gmail.com
escreveu:
Hey,
I'm using DSpace 4.3 and trying to search for items matching certain
metadata. The REST API docs on GitHub[0] mention that you can POST to
`rest/items/find-by-metadata-field`, but it doesn't give any more
information than that (like how to specify query parameters).
I've tried several variations of the following:
$ http --print Hhb POST '
http://localhost:8080/rest/items/find-by-metadata-field'
dc.subject=LACTATION
It always returns with an HTTP 405. What is the proper way to use
this? Does the POST require I login first or something?
Thanks,
[0] https://github.com/DSpace/DSpace/tree/master/dspace-rest
--
Alan Orth
alan.o...@gmail.com
https://alaninkenya.org
https://mjanja.ch
In heaven all the interesting people are missing. -Friedrich
Nietzsche
GPG public key ID: 0x8cb0d0acb5cd81ec209c6cdfbd1a0e09c2f836c0
--
___
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
--
Alan Orth
alan.o...@gmail.com
https://alaninkenya.org
https://mjanja.ch
In heaven all the interesting people are missing. -Friedrich Nietzsche
GPG public key ID: 0x8cb0d0acb5cd81ec209c6cdfbd1a0e09c2f836c0
--
___
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
--
Terry Brady
Applications Programmer Analyst
Georgetown University Library Information Technology
https://www.library.georgetown.edu/lit/code
425-298-5498 (Seattle, WA)
--
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette:
