Re: [dspace-tech] Language Support in dspace

[Aman Garu]

Dear Claudia,
Thank you for your response. 

Let me explain my problem. For eg. When I search "Nep" it matches the word 
like Nepal, Nepali, anepalya, etc. But while searching via Nepali Language 
we are are not getting required output. For eg. When I search "नेप" it 
doesn't match the world like नेपाल, नेपाली, अनेपालय, etc. It matches whole 
word only. So it only returns items containing "नेप".   

On Wednesday, December 13, 2017 at 4:02:48 PM UTC+5:45, Claudia Jürgen 
wrote:
>
> Hello Aman, 
>
> with which version and UI of DSpace are you working and which servlet 
> container do you use. 
> For international character support in Tomcat you got to set the 
> URIEncoding="UTF-8" 
> see 
>
> https://wiki.duraspace.org/display/DSDOC5x/Installing+DSpace#InstallingDSpace-ServletEngine(ApacheTomcat7orlater,Jetty,CauchoResinorequivalent)
>  
>
> Just tried it on a 5.x instance with stuff from 
> https://en.wikibooks.org/wiki/Nepali/Vocabulary and it was searchable, 
> so most likely it is the above mentioned encoding setting. 
>
> Hope this helps 
>
> Claudia Jürgen 
>
>
>
> Am 12.12.2017 um 06:20 schrieb Aman Garu: 
> > Hello! 
> > 
> > I am from Nepal and we have to store the items in Nepali language in 
> > dspace. Storing is not an issue but I am not able to search the items in 
> > Nepali language. What should I do for it. Can someone help me! 
> > 
> > Thank in advance. 
> > 
> > 
>
> -- 
> 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...@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: Flyway migration "Hibernate Workflow Migration" fails

[kardeiz]

I've reported this here: https://jira.duraspace.org/browse/DS-3788.

On Wednesday, December 13, 2017 at 2:56:34 PM UTC-6, kar...@gmail.com wrote:
>
> With a new installation of DSpace 6.2, pretty generic configuration (e.g., 
> no edits to anything around Flyway/Hibernate/etc.), and a fresh database 
> with Oracle XE 11.2, `./dspace database migrate` fails at "6.0.2015.08.31  
>   | DS 2701 Hibernate Workflow Migration" with the following error
>
> Script failed
> -
> SQL State  : 72000
> Error Code : 12991
> Message: ORA-12991: column is referenced in a multi-column constraint
> Line   : 36
> Statement  : ALTER TABLE cwf_collectionrole DROP COLUMN 
> collection_legacy_id
>
> at 
> org.flywaydb.core.internal.dbsupport.SqlScript.execute(SqlScript.java:117)
> at 
> org.dspace.storage.rdbms.DatabaseUtils.executeSql(DatabaseUtils.java:1089)
> ... 25 more
> Caused by: java.sql.SQLException: ORA-12991: column is referenced in a 
> multi-column constraint
>
> Any thoughts on why this is happening?
>
> Thanks,
>
> Jacob
>

-- 
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: Flyway migration "Hibernate Workflow Migration" fails

[kardeiz]

Unless I am missing something, this looks like a bug in the Oracle SQL. It 
looks like the PostgreSQL commands were just copied into another file 
without the appropriate modifications (apparently Oracle doesn't handle 
column renaming in the same way as Postgres).

I ran the relevant SQL data definitions in Oracle directly and got the 
error reported by Flyway.

The faulty 
file: 
https://github.com/DSpace/DSpace/blob/master/dspace-api/src/main/resources/org/dspace/storage/rdbms/sqlmigration/workflow/oracle/xmlworkflow/V6.0_2015.08.11__DS-2701_Xml_Workflow_Migration.sql.



On Wednesday, December 13, 2017 at 2:56:34 PM UTC-6, kar...@gmail.com wrote:
>
> With a new installation of DSpace 6.2, pretty generic configuration (e.g., 
> no edits to anything around Flyway/Hibernate/etc.), and a fresh database 
> with Oracle XE 11.2, `./dspace database migrate` fails at "6.0.2015.08.31  
>   | DS 2701 Hibernate Workflow Migration" with the following error
>
> Script failed
> -
> SQL State  : 72000
> Error Code : 12991
> Message: ORA-12991: column is referenced in a multi-column constraint
> Line   : 36
> Statement  : ALTER TABLE cwf_collectionrole DROP COLUMN 
> collection_legacy_id
>
> at 
> org.flywaydb.core.internal.dbsupport.SqlScript.execute(SqlScript.java:117)
> at 
> org.dspace.storage.rdbms.DatabaseUtils.executeSql(DatabaseUtils.java:1089)
> ... 25 more
> Caused by: java.sql.SQLException: ORA-12991: column is referenced in a 
> multi-column constraint
>
> Any thoughts on why this is happening?
>
> Thanks,
>
> Jacob
>

-- 
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: Statistics: Invalid content type

[wlrutherford]

Hello Jeffrey,

Did you ever find a solution? I'm seeing the same errors. The difference is 
I'm not sure if the Usage Statistics
ever worked. I recently built a new server and moved the database to 
replace an older system managed by
somebody else. Users are reporting that the stats worked on the old server 
but not now.



On Wednesday, May 24, 2017 at 10:49:45 AM UTC-8, Jeffrey Sheldon wrote:
>
> Folks, 
>
> Our usage statistics abruptly stopped working yesterday despite no major 
> changes having taken place in our DSpace 5.3/XMLUI installation.  If I 
> choose to view statistics, nothing is displayed.  Rather, I receive the 
> following errors in catalina.out after clicking on the associated action: 
>
> View Usage Statistics 
> Error using query type: 2 
>
> View Search Statistics 
> Error using query *:* 
>
> View Workflow Statistics 
> Error using query statistics_type:workflow AND NOT(previousWorkflowStep: 
> SUBMIT) 
>
> In the dspace.log file, this is the response for "View Usage Statistics": 
>
> 2017-05-24 18:31:47,344 ERROR 
> org.dspace.app.xmlui.aspect.statistics.StatisticsTransformer @ Error 
> occurred while creating statistics for home page 
> org.apache.solr.client.solrj.SolrServerException: Error executing query 
> at 
> org.apache.solr.client.solrj.request.QueryRequest.process(QueryRequest.java:100)
>  
>
> at 
> org.apache.solr.client.solrj.SolrServer.query(SolrServer.java:301) 
> at org.dspace.statistics.SolrLogger.query(SolrLogger.java:1203) 
> at 
> org.dspace.statistics.SolrLogger.queryFacetField(SolrLogger.java:920) 
> at 
> org.dspace.statistics.content.StatisticsDataVisits.queryFacetField(StatisticsDataVisits.java:647)
>  
>
> at 
> org.dspace.statistics.content.StatisticsDataVisits.createDataset(StatisticsDataVisits.java:252)
>  
>
> at 
> org.dspace.statistics.content.StatisticsDisplay.getDataset(StatisticsDisplay.java:88)
>  
>
> at 
> org.dspace.app.xmlui.aspect.statistics.StatisticsTransformer.addDisplayListing(StatisticsTransformer.java:373)
>  
>
> at 
> org.dspace.app.xmlui.aspect.statistics.StatisticsTransformer.renderHome(StatisticsTransformer.java:156)
>  
>
> at 
> org.dspace.app.xmlui.aspect.statistics.StatisticsTransformer.addBody(StatisticsTransformer.java:106)
>  
>
> at 
> org.dspace.app.xmlui.wing.AbstractWingTransformer.startElement(AbstractWingTransformer.java:223)
>  
>
> at sun.reflect.GeneratedMethodAccessor155.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)
>  
>
> at com.sun.proxy.$Proxy99.startElement(Unknown Source) 
> at 
> org.apache.cocoon.components.sax.XMLTeePipe.startElement(XMLTeePipe.java:87) 
>
> at 
> org.apache.cocoon.components.sax.AbstractXMLByteStreamInterpreter.parse(AbstractXMLByteStreamInterpreter.java:117)
>  
>
> at 
> org.apache.cocoon.components.sax.XMLByteStreamInterpreter.deserialize(XMLByteStreamInterpreter.java:44)
>  
>
> at 
> org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline.processXMLPipeline(AbstractCachingProcessingPipeline.java:324)
>  
>
> at 
> org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.process(AbstractProcessingPipeline.java:750)
>  
>
> at sun.reflect.GeneratedMethodAccessor197.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)
>  
>
> at com.sun.proxy.$Proxy87.process(Unknown Source) 
> at 
> org.apache.cocoon.components.source.impl.SitemapSource.toSAX(SitemapSource.java:362)
>  
>
> at 
> org.apache.cocoon.components.source.util.SourceUtil.toSAX(SourceUtil.java:111)
>  
>
> at 
> org.apache.cocoon.components.source.util.SourceUtil.parse(SourceUtil.java:294)
>  
>
> at 
> org.apache.cocoon.generation.FileGenerator.generate(FileGenerator.java:136) 
> at sun.reflect.GeneratedMethodAccessor188.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)
>  
>
> at com.sun.proxy.$Proxy92.generate(Unknown Source) 
> at 
> org.apache.cocoon.components.pipeline.AbstractProcessingPipeline.processXMLPipeline(AbstractProcessingPipeline.java:544)
>  
>
> at 
> 

[dspace-tech] Statistics in dspace 5.5

[Lucas angelo]

I am not able to activate the statistics in dspace, when I click on 
statistics, it appears "there are no reports to show" can anyone help me?



Att, Lucas.

-- 
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] DSpace JSPUI Virus Scanning During Upload

[Tim Donohue]

Hi Gary,

Looking at the error stacktrace in your Gist (
https://gist.github.com/gzhou1/b0b4996bf5c617b25af0291c1aa0edaa), it looks
like a Hibernate issue similar to this one (and the tickets that are linked
off of it):
https://jira.duraspace.org/browse/DS-3775

I'm not entirely sure of the cause here (as I'm less familiar with this
area of the code), but maybe it'll give you or someone else on this list a
hint in the right direction.

- Tim

On Tue, Dec 12, 2017 at 12:24 PM Gary Zhou  wrote:

> Hi,
>
> I am trying to implement virus scanning in Submission step and would like
> clarification on how virus scanning should work. My DSpace setup is using
> v6.2 JSPUI. I'm noticing that when a file fails the virus scanning, the
> InternalErrorServlet handler is called and I get the following traceback
> when an email attempts to send (
> https://gist.github.com/gzhou1/b0b4996bf5c617b25af0291c1aa0edaa). Should
> this be happening? Additionally, when Next is clicked on an unsuccessful
> (virus found) upload, the status is not being properly stored and passed
> into doPostProcessing() in JSPUploadStep. From what I understand, status is
> retrieved from processUploadFile() in UploadStep. Status is returned
> properly on the initial upload (on the condition of attr.endsWith("-path"))
> but upon "Next" click, STATUS_COMPLETE (0) is returned because the
> condition is never met.
>
> It is worth noting that the application behaves as expected when using
> XMLUI.
>
> Thanks!
>
> --
> 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.

[dspace-tech] Re: DSpace 7 and Accessibilty

[Mark H. Wood]

We also need to work out what we mean by "accessibility".  For example, I'm 
told that here at a US public university which receives Federal grant 
money, we come under section 504 of the Rehabilitation Act of 1973 and thus are 
expected to comply with WCAG 2.0 level AA.  Other jurisdictions may have 
different requirements.  We need to collate all of those requirements so 
that we know what to test.

-- 
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] DSpace 7 and Accessibilty

[Tim Donohue]

Hi All,

Per this DSpace 7 Accessibility discussion, I've just created a ticket in
our DSpace 7 UI codebase around finding tools to help us automate basic
accessibility testing (and build a better UI in the process).  I'd
appreciate feedback from anyone interested/experienced in accessibility
tools, guidelines and/or automated testing.

https://github.com/DSpace/dspace-angular/issues/209

If there are accessibility experts out there interested in providing
feedback on DSpace 7, we'd love to hear from you!  Just drop me an email
and/or add your thoughts to the above GitHub ticket.

Thanks,

Tim


On Wed, Nov 29, 2017 at 2:47 PM Tim Donohue  wrote:

> Hi Claudia,
>
> One of the core features of recent versions of Angular (2 and above) is
> ARIA-enabled components: https://angular.io/features  So, a base level of
> accessibility is "built-in" to some extent, but I'm certain it can be
> improved upon in our UI code.
>
> During the decision making process on Angular,  we had help from the U of
> Kansas on performing some basic accessibility tests against the Angular
> platform to ensure it would meet our needs. The tests came back positive,
> with only minor issues (from our own code) at the time.  See this old
> ticket, which describes the testing process that was performed against the
> prototype last year:
> https://github.com/DSpace-Labs/angular2-ui-prototype/issues/113
>
> Currently, as you've seen, development has moved over to the
> dspace-angular project: https://github.com/DSpace/dspace-angular/   The
> base platform is the same, but we haven't (yet) done a repeat of the
> accessibility tests from last year.  I fully agree that this is a great
> opportunity to ensure DSpace has a highly accessible, modern UI.
>
> As we are still quite early in the DSpace 7 UI development process, we
> have not done any additional formalized testing of the UI for
> accessibility.  However, prior to the DSpace 7 final release, I'd like to
> see more formal accessibility testing occur (and if there is anyone
> interested in helping us in this way, please do get in touch).
>
> In the meantime, there is the opportunity for interested folks (or a team
> of folks) to begin doing some basic accessibility testing against our demo
> site: https://dspace7-demo.atmire.com/ .  This demo site is always
> running the latest version of the DSpace 7 UI (as it auto-updates on any
> code changes).  Any accessibility issues found should be logged as bugs in
> our GitHub issue tracker for the project:
> https://github.com/DSpace/dspace-angular/issues  (that way we can assign
> them to DSpace 7 developers to be fixed ASAP)
>
> I like your idea of establishing more formal guidelines for DSpace
> accessibility (and the Angular UI specifically perhaps).  I'd welcome
> someone (or multiple someones) to consider drafting some accessibility
> notes on our Wiki.  This could start with some simple guidelines/goals, and
> perhaps even include tools for testing, basic best practices, etc.
>
> If there is such interest, we could even consider forming an Accessibility
> Working Group (or similar) to discuss how to generate these guidelines or
> provide feedback from their own experiences.
>
> In any case, this is definitely a place we could use help!  I cannot claim
> anyone on the DSpace 7 UI team is an accessibility expert, but we'd all
> like to ensure the new UI is meeting the accessibility goals of our user
> community.  So, help in defining/formalizing those goals and providing bug
> reports on existing issues would be appreciated.
>
> - Tim
>
>
> On Wed, Nov 29, 2017 at 5:55 AM Claudia Jürgen <
> claudia.juer...@tu-dortmund.de> wrote:
>
>> Hi all,
>>
>> as I have been once again asked off list about accessibilty and DSpace I
>> thought to raise the issue.
>> This has been an ongoing feature request with DSpace since the beginning.
>> There are a couple of tickets with regards to it.
>> Two UI's and a lot of changes made it difficult and costly to address the
>> issue for DSpace in general.
>>
>> I wonder whether the fresh start with Angular will provide the
>> opportunity to do it now.
>> It was one argument during the prototyping challenge but I did not find
>> anything  at
>>
>> https://wiki.duraspace.org/display/DSPACE/DSpace+7+-+Angular+UI+Development
>> Being completly new to Angular, just installed dspace angular once to
>> have a peek and looked a a tutorial.
>> There are a couple of tutorials and the old angular js did have an aria
>> module, but I did not find anything similar in the newer versions.
>>
>> But actually it would first require to define which level and standards
>> or even best practices of accessibility we want to support/adpopt in the
>> long run in DSpace and create guidelines.
>> What are your thoughts?
>>
>> cu
>>
>> Claudia
>>
>>
>> --
>> Claudia Juergen
>> Eldorado
>>
>> Technische Universität Dortmund
>> UniversitätsbibliothekVogelpothsweg 76
>> 44227 Dortmund 
>> 

[dspace-tech] Re: Problem to harvest a collection from a external repository.

[Mark H. Wood]

I will quickly note that the code which returns "invalidAddress: OAI server 
could not be reached" catches any Exception, discards it without looking at 
it, and assumes that the URL was invalid.  We should fix that.

-- 
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: PDF CoverPage generation in JSPUI

[caosborne . az]

Hi Swapnil,
I just heard back from Dspace technical support and they said out-of-box in 
the JSPUI only the cover page can be generated only using the curation 
task, you cannot get it on the fly. They said they have code that's not 
currently in JSPUI that provides this functionality that they can share. 
Once I get that, I'll post it here as well (sounds like thy are going to 
post it somewhere on github).

On Sunday, April 2, 2017 at 9:51:35 AM UTC-7, Swapnil Patel wrote:
>
> Dear DSpace users,
>
> As mentioned at http://demo.dspace.org/jspui I found that PDF CoverPage 
> generation feature is added in JSPUI in DSpace 6.
>
> I have implemented the same in both JSPUI and XMLUI as per the 
> instructions given in 
> https://wiki.duraspace.org/display/DSDOC6x/PDF+Citation+Cover+Page
>
> It is working perfectly in XMLUI but *not working in JSPUI*.
>
> My question is, *Has anyone tried to implement PDF CoverPage generation 
> in JSPUI?*
>
> Please guide me as it is my requirement to implement the feature in JSPUI.
>
> 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] Problem to harvest a collection from a external repository.

[Brendow Adriel]

Hello guys,

i'm trying harvest a collection from a external repository by OAI service, 
but when i try ping the url by terminal  or test the configurations harvest 
in module xmlui:

*By xmlui:*

* OAI server could not be reached.

*By terminal:*

C:\dspace5\bin>dspace harvest -g -a 
https://repositorioaberto.uab.pt/oai/request -i all

Using DSpace installation in: C:\dspace5

Testing basic PMH access:  8967 [main] DEBUG 
ORG.oclc.oai.harvester2.verb.HarvesterVerb  - 
requestURL=https://repositorioaberto.uab.pt/oai/request?verb=Identify
23544 [net.sf.ehcache.CacheManager@6d167f58] DEBUG 
net.sf.ehcache.util.UpdateChecker  - Update check failed: 
java.net.ConnectException: Connection timed out: connect
invalidAddress: OAI server could not be reached.

Testing ORE support:  31598 [main] DEBUG 
ORG.oclc.oai.harvester2.verb.HarvesterVerb  - 
requestURL=https://repositorioaberto.uab.pt/oai/request?verb=Identify
invalidAddress: OAI server could not be reached.
52641 [main] DEBUG net.sf.ehcache.CacheManager  - CacheManager already 
shutdown

*By terminal returning status: 200 OK!:*

Other test with other url oai service:

Using DSpace installation in: C:\dspace5
Testing basic PMH access:  38726 [main] DEBUG 
ORG.oclc.oai.harvester2.verb.HarvesterVerb  - 
requestURL=https://demo.dspace.org/oai/request?verb=Identify
40198 [main] DEBUG ORG.oclc.oai.harvester2.verb.HarvesterVerb  - 
responseCode=200
40205 [main] DEBUG ORG.oclc.oai.harvester2.verb.HarvesterVerb  - 
contentEncoding=null
41265 [main] DEBUG ORG.oclc.oai.harvester2.verb.HarvesterVerb  - 
requestURL=https://demo.dspace.org/oai/request?verb=ListMetadataFormats
41278 [main] DEBUG ORG.oclc.oai.harvester2.verb.HarvesterVerb  - 
responseCode=200
41284 [main] DEBUG ORG.oclc.oai.harvester2.verb.HarvesterVerb  - 
contentEncoding=null
41292 [main] DEBUG ORG.oclc.oai.harvester2.verb.HarvesterVerb  - 
requestURL=https://demo.dspace.org/oai/request?verb=ListMetadataFormats
41350 [main] DEBUG ORG.oclc.oai.harvester2.verb.HarvesterVerb  - 
responseCode=200
41398 [main] DEBUG ORG.oclc.oai.harvester2.verb.HarvesterVerb  - 
contentEncoding=null
OK

Testing ORE support:  41541 [main] DEBUG 
ORG.oclc.oai.harvester2.verb.HarvesterVerb  - 
requestURL=https://demo.dspace.org/oai/request?verb=Identify
41555 [main] DEBUG ORG.oclc.oai.harvester2.verb.HarvesterVerb  - 
responseCode=200
41555 [main] DEBUG ORG.oclc.oai.harvester2.verb.HarvesterVerb  - 
contentEncoding=null
41557 [main] DEBUG ORG.oclc.oai.harvester2.verb.HarvesterVerb  - 
requestURL=https://demo.dspace.org/oai/request?verb=ListMetadataFormats
41566 [main] DEBUG ORG.oclc.oai.harvester2.verb.HarvesterVerb  - 
responseCode=200
41570 [main] DEBUG ORG.oclc.oai.harvester2.verb.HarvesterVerb  - 
contentEncoding=null
41573 [main] DEBUG ORG.oclc.oai.harvester2.verb.HarvesterVerb  - 
requestURL=https://demo.dspace.org/oai/request?verb=ListMetadataFormats
41591 [main] DEBUG ORG.oclc.oai.harvester2.verb.HarvesterVerb  - 
responseCode=200
41591 [main] DEBUG ORG.oclc.oai.harvester2.verb.HarvesterVerb  - 
contentEncoding=null
OK

41604 [main] DEBUG net.sf.ehcache.CacheManager  - CacheManager already 
shutdown


 This is related with proxy of my dspace application or the application oai 
service collected?

I tested too, in others environments dspace without proxy and including in 
the demo.dspace.org/xmlui. it returns the same error:

* OAI server could not be reached.

I honestly am not able to see the problem or how to solve this

-- 
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] Language Support in dspace

[Claudia Jürgen]

Hello Aman,

with which version and UI of DSpace are you working and which servlet
container do you use.
For international character support in Tomcat you got to set the
URIEncoding="UTF-8"
see
https://wiki.duraspace.org/display/DSDOC5x/Installing+DSpace#InstallingDSpace-ServletEngine(ApacheTomcat7orlater,Jetty,CauchoResinorequivalent)

Just tried it on a 5.x instance with stuff from
https://en.wikibooks.org/wiki/Nepali/Vocabulary and it was searchable,
so most likely it is the above mentioned encoding setting.

Hope this helps

Claudia Jürgen



Am 12.12.2017 um 06:20 schrieb Aman Garu:

Hello!

I am from Nepal and we have to store the items in Nepali language in
dspace. Storing is not an issue but I am not able to search the items in
Nepali language. What should I do for it. Can someone help me!

Thank in advance.




--
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] DSpace-CRIS, default filters for Organizations and Projects do not work

[euler]

Dear DSpace-CRIS experts,

I am currently testing a DSpace-CRIS installation and I noticed that the 
filters for Organizations and Projects do not work. When I tried the demo 
of DSpace-CRIS at https://dspace-cris.4science.it, I confirmed that the 
filters indeed do not work. For example, if I use the filter Investigators 
with a value of blue, it returned no results:






Although if you browse the project by title, 2 projects have Blue, Earth as 
its principal investigator. Other filters like start date and keywords 
don't work also, even if I use Contains as the filter_type.


Please help on how to make these filters work and how to add additional 
filters aside from the default filters if ever.


Thanks in advance!


Best regards,

euler

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