[dspace-tech] xmlui StartSubmissionLookupStep not working

2017-07-11 Thread Geoffrey Brimhall 
dspace pubmed/docid lookup is working fine with dspace5 and jspui

I built dspace 6 xmlui + mirage2 to test out pubmed/docid lookup with 
xmlui, but so far have no success in getting it to work. It simply returns 
nothing when I hit the "search" button whether I enter a 
pubmed/docid/author, such as "10.1002/ldr.2317" or "27252203". I've tried 
this with both the dspace release and src build, same results either way.

Following directions at 

https://wiki.duraspace.org/display/DSDOC6x/2016+Framework+for+live+import+from+external+sources

https://wiki.duraspace.org/display/DSPACE/Troubleshoot+an+error

Log errors:

*dspace.log:*

Caused by: org.apache.axiom.om.OMException: 
com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '"' 
(code 34) in DOCTYPE declaration; expected a space between public and 
system identifiers
 at [row,col {unknown-source}]: [1,50]
at 
org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:276)
at 
org.apache.axiom.om.impl.llom.OMContainerHelper.buildNext(OMContainerHelper.java:164)
at 
org.apache.axiom.om.impl.llom.OMContainerHelper.getFirstOMChild(OMContainerHelper.java:182)
at 
org.apache.axiom.om.impl.llom.OMDocumentImpl.getFirstOMChild(OMDocumentImpl.java:201)
at 
org.apache.axiom.om.impl.llom.OMDocumentImpl.getOMDocumentElement(OMDocumentImpl.java:98)
at 
org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOMBuilder.java:544)
at 
org.apache.axiom.om.impl.builder.StAXOMBuilder.getDocumentElement(StAXOMBuilder.java:540)
at 
org.dspace.importer.external.pubmed.service.PubmedImportMetadataSourceServiceImpl.getSingleElementValue(PubmedImportMetadataSourceServiceImpl.java:202)
at 
org.dspace.importer.external.pubmed.service.PubmedImportMetadataSourc

...

2017-07-11 23:48:14,152 ERROR 
org.dspace.app.xmlui.aspect.submission.submit.JSONLookupSearcher @ 
org.dspace.importer.external.exception.MetadataSourceException: At retry of 
operation 8d67cebd-5545-4feb-9a1f-e0c3e4b5aac2 0
org.dspace.importer.external.exception.MetadataSourceException: 
org.dspace.importer.external.exception.MetadataSourceException: At retry of 
operation 8d67cebd-5545-4feb-9a1f-e0c3e4b5aac2 0
at 
org.dspace.importer.external.service.ImportService.getNbRecords(ImportService.java:136)
at 
org.dspace.app.xmlui.aspect.submission.submit.JSONLookupSearcher.generate(JSONLookupSearcher.java:85)
at sun.reflect.GeneratedMethodAccessor141.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71)


*cocoon.log:*

at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:615)
at 
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskTh
read.java:61)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.RuntimeException: 
org.dspace.importer.external.exception.Me
tadataSourceException: 
org.dspace.importer.external.exception.MetadataSourceExce
ption: At retry of operation 8d67cebd-5545-4feb-9a1f-e0c3e4b5aac2 0
at 
org.dspace.app.xmlui.aspect.submission.submit.JSONLookupSearcher.gene
rate(JSONLookupSearcher.java:156)
at sun.reflect.GeneratedMethodAccessor141.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.i
nvoke(PoolableProxyHandler.java:71)
at com.sun.proxy.$Proxy211.generate(Unknown Source)
at 
org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.proc
essXMLPipeline(AbstractProcessingPipeline.java:544)
... 79 more
Caused by: org.dspace.importer.external.exception.MetadataSourceException: 
org.d
space.importer.external.exception.MetadataSourceException: At retry of 
operation
 8d67cebd-5545-4feb-9a1f-e0c3e4b5aac2 0
at 
org.dspace.importer.external.service.ImportService.getNbRecords(Impor
tService.java:136)
at 
org.dspace.app.xmlui.aspect.submission.submit.JSONLookupSearcher.gene
rate(JSONLookupSearcher.java:85)
... 85 more
Caused by: org.dspace.importer.external.exception.MetadataSourceException: 
At re
try of operation 8d67cebd-5545-4feb-9a1f-e0c3e4b5aac2 0
at 
org.dspace.importer.external.service.components.AbstractRemoteMetadat
aSource.throwSourceException(AbstractRemoteMetadataSource.java:229)
at 
org.dspace.importer.external.service.components.AbstractRemoteMetadat
aSource.handleException(AbstractRemoteMetadataSource.java:203)
at 
org.dspace.importer.external.service.components.AbstractRemoteMetadat
aSource.retry(AbstractRemoteMetadataSource.java:168)
at

Re: [dspace-tech] check pdf files

2017-07-11 Thread mariafernanda . ruiz . cepal 
Thanks Emilio for your answer.

I will check the dspace-tech for more information.

Cheers!!!




On Wednesday, July 5, 2017 at 5:42:39 AM UTC-4, Emilio Lorenzo wrote:
>
> Hi Fernanda, 
>
> I suppose you are referring to PDF-A1,2 and 3 vs PDF. The checking is 
> difficult due to the ISO-standard complexity as explained in  
> https://en.wikipedia.org/wiki/PDF/A
>
> Nevertheless, probably the best option to access files  in the assetstore 
> (an object contains multiple files as you have discovered)  is using the 
> java methods in Dspace (a good starting point would be the curation task  
> called Bitstream Format Profiler)  or using specific database queries 
> (there are similar questions in Dspace-teh regarding this identification 
> and access.
>
> After that access,  you will need a validator to test the compliance (see 
> https://softwarerecs.stackexchange.com/questions/18161/is-there-free-or-open-source-software-for-checking-pdf-a-compliance
> )
>
> best luck
> Emilio 
>
> El 04/07/2017 a las 17:39, mariafernand...@gmail.com  
> escribió:
>
> Hi everybody
>
> I need to check wich files (bitstreams) are ftp or ftp-a. It is possible 
> to check with Adobe Professional what kind of pdf is, however I need to put 
> all the files to check under one directory.
>
> I know all the files (ftp and others) are storaged inside other 
> directories under /assetstore folder, and they are indicated in the name of 
> the file, for example:
>
> A bitstream with the internal ID 12345678901234567890123456789012345678 is 
> stored in the directory
>
> [dspace]/assetstore/12/34/56/12345678901234567890123456789012345678
>
> My question is:  how can I access directly to the bitstreams with 
> extension pdf?, because if I open this bitstream 
> 12345678901234567890123456789012345678, it will only have plain text.
>
> Thanks for your help!!
>
> Fernanda
> -- 
> 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...@googlegroups.com .
> To post to this group, send email to dspac...@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.

[dspace-tech] Metadata filed doesn't change after modifying local.cfg

2017-07-11 Thread danielKim 
Thanks for reading this question.
Our library repository uses custom metadata filed so I have added following 
lines in the local.cfg configuration file.

webui.itemdisplay.default = dc.title, dc.title.alternative, 
dc.contributor.*, \
dc.subject(nobreakline), dc.date.issued(date), 
dc.publisher, \
dc.identifier.citation, 
dc.relation.ispartofseries, \
dc.description.abstract, dc.description, \
dc.identifier.govdoc, dc.identifier.uri(link),\
dc.identifier.isbn, dc.identifier.issn, \
dc.identifier.ismn, dc.identifier, \
dc.subject.keywords, dc.rights.uri

So far I know without this, the default metadata will be displayed in the 
web interface.
The problem is 'webui.itemdisplay.default' will only accept one parameter 
and ignore parameters after on.
For example, if I change first line of this configuration,

webui.itemdisplay.default = dc.subject.keywords, dc.title.alternative, 
dc.contributor.*, \

The web interface will be look like this:




So if I change config like this:

webui.itemdisplay.default = dc.title, dc.title.alternative, 
dc.contributor.*, \
*..*
*Below are the same as above*


web interface will show the title correctly.




So it seems webui.itemdisplay.default accepts only one parameter from the 
config file but it should read whole configuration and change metadata 
display to users.


This is my dspace version information. 




I have another dspace server which is running original 6.0 release. (So 
this server is made for using CRIS version of dspace)

That old server correctly shows all metadata information as we change 
related configurations at local.cfg file.

Do you think this is the bug of CRIS version ? or should I made some 
mistake which prevents to dspace can't recognize configurations correctly?


Thanks in advance! 

-- 
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] XMLUI embargo date (edit file) is not saved DSpace 6

2017-07-11 Thread maria . caceres . csuc 
Hello,

I have enabled simple embargo just following the steps in the wiki: 
https://wiki.duraspace.org/display/DSDOC6x/Embargo but when I try to save 
the page, the embargo date is not stored but I don't recieve any kind of 
error.

Does someone know what is happening?

Regards,
María  

-- 
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] Metadata changes after migrate to dspace 6

2017-07-11 Thread helix84 
On Tue, Jul 11, 2017 at 9:50 AM,   wrote:
> In the version 3.2 I had only one schema "dc" and after the migration I have
> one another "eperson". Why the user values like firstname, lastname, phone
> and language are stored in metadata too??

Here's why:

https://wiki.duraspace.org/display/DSPACE/Metadata+for+all+DSpace+objects

It's metadata for other objects in addition to items.


Regards,
~~helix84

Compulsory reading: DSpace Mailing List Etiquette
https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

-- 
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] Metadata changes after migrate to dspace 6

2017-07-11 Thread maria . caceres . csuc 
Hello, 

I have migrate my database to the last version of Dspace and I found some 
changes in the metadata.

In the version 3.2 I had only one schema "dc" and after the migration I 
have one another "eperson". Why the user values like firstname, lastname, 
phone and language are stored in metadata too??

And why after the migration I have else another metadata dc.rights.license 
if i had dc.rights and dc.rights.uri??

Regards,
María

-- 
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.