Re: [dspace-tech] Weird XML/DRI behavior

[Cameron, Jacob]

Thanks Terry. Will give that a go.

--

Please excuse any typing errors or grammatical mistakes. I’m sending this 
message from a mobile device.

Jake Cameron, BCS(UNB)
Systems Support Specialist III
Information Systems and Technical Services University of Lethbridge Library
Phone:(403)329-2756
This e-mail, including any and all attachments, is only for the use of the 
intended recipient(s) and may contain information that is confidential or 
privileged. If you are not the intended recipient, you are advised that any 
dissemination, copying or other use of this e-mail is prohibited. Please notify 
the sender of the error in communication by return e-mail and destroy all 
copies of this e-mail. Thank you.

From: dspace-tech@googlegroups.com  on behalf of 
Terry Brady 
Sent: Wednesday, November 7, 2018 5:57:28 PM
To: Cameron, Jacob
Cc: dspace-tech@googlegroups.com
Subject: Re: [dspace-tech] Weird XML/DRI behavior

It sounds like you have ruled out a browser cache issue.

In the Control Panel -> Java Information section, try clearing the Cocoon cache 
to see if that makes a difference.

On Wed, Nov 7, 2018 at 1:08 PM Cameron, Jacob 
mailto:jacob.came...@uleth.ca>> wrote:
Hi Everyone,

I’ve made some customizations to our front page to add searches for Series and 
Type under the browse, all of DSpace area.

When we just us the url, https://opus.uleth.ca they do not show up.  It shows 
up as the screenshot labelled without XML or DRI.  However, if I use 
https://opus.uleth.ca?xml  or https://opus.uleth.ca?dri they show up properly.  
I’ve tried Chrome, Opera, Firefox and Edge.  It happens in all of those.  
However if I’m on a mobile device, android or apple, they show up fine without 
the ?xml or ?dri.  Any thoughts?

I have tried everything I can think of.

Jake

--
Jake Cameron, BCS(UNB)
Systems Support Specialist III
Information Systems and Technical Services University of Lethbridge Library
Phone:(403)329-2756
This e-mail, including any and all attachments, is only for the use of the 
intended recipient(s) and may contain information that is confidential or 
privileged. If you are not the intended recipient, you are advised that any 
dissemination, copying or other use of this e-mail is prohibited. Please notify 
the sender of the error in communication by return e-mail and destroy all 
copies of this e-mail. Thank you.


--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
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.


--
Terry Brady
Applications Programmer Analyst
Georgetown University Library Information Technology
https://github.com/terrywbrady/info
425-298-5498 (Seattle, WA)

--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
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.

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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] Weird XML/DRI behavior

[Terry Brady]

It sounds like you have ruled out a browser cache issue.

In the Control Panel -> Java Information section, try clearing the Cocoon
cache to see if that makes a difference.

On Wed, Nov 7, 2018 at 1:08 PM Cameron, Jacob 
wrote:

> Hi Everyone,
>
>
>
> I’ve made some customizations to our front page to add searches for Series
> and Type under the browse, all of DSpace area.
>
>
>
> When we just us the url, https://opus.uleth.ca they do not show up.  It
> shows up as the screenshot labelled without XML or DRI.  However, if I use
> https://opus.uleth.ca?xml  or https://opus.uleth.ca?dri they show up
> properly.  I’ve tried Chrome, Opera, Firefox and Edge.  It happens in all
> of those.  However if I’m on a mobile device, android or apple, they show
> up fine without the ?xml or ?dri.  Any thoughts?
>
>
>
> I have tried everything I can think of.
>
>
>
> Jake
>
>
>
> --
>
> Jake Cameron, BCS(UNB)
>
> Systems Support Specialist III
>
> Information Systems and Technical Services University of Lethbridge Library
>
> Phone:(403)329-2756
>
> This e-mail, including any and all attachments, is only for the use of the
> intended recipient(s) and may contain information that is confidential or
> privileged. If you are not the intended recipient, you are advised that any
> dissemination, copying or other use of this e-mail is prohibited. Please
> notify the sender of the error in communication by return e-mail and
> destroy all copies of this e-mail. Thank you.
>
>
>
> --
> All messages to this mailing list should adhere to the DuraSpace Code of
> Conduct: https://duraspace.org/about/policies/code-of-conduct/
> ---
> 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.
>


-- 
Terry Brady
Applications Programmer Analyst
Georgetown University Library Information Technology
https://github.com/terrywbrady/info
425-298-5498 (Seattle, WA)

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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: Harvesting Error when running automatic harvesting scheduler

[Diego Brice]

So, If I add the property "oai.harvester.eperson" to oai cfg file it will 
work?. Or did you change any source code?

Regards

Diego

El viernes, 2 de noviembre de 2018, 0:17:25 (UTC-3), Kev Gunn escribió:
>
> After some more digging, the class HarvestScheduler uses the 
> configuration property oai.harvester.eperson to defined a harvestAdmin.
> Currently this isn't passed to HarvestThread which constructs a new 
> context for the OAIHarvest to run in, updating the constructor to pass the 
> harvestAdmin to see if that resolved this issue.
> oai.harvester.eperson isn't defined in the default oai.cfg properties file 
> so i wasn't aware it was needed without looking at the source code.
>
> Cheers
>
> On Wednesday, 12 September 2018 16:42:34 UTC+10, euler wrote:
>>
>> Dear All,
>>
>> I'm having trouble using the automatic harvest scheduler both in the 
>> XMLUI and in the command line. The version of DSpace the server is running 
>> on is 6.3. When I use the command line (dspace harvest -S), the command 
>> line returned the following error:
>>
>> Starting harvest loop... running.
>> org.dspace.core.exception.DatabaseSchemaValidationException: The schema 
>> validator returned: null
>> at org.dspace.core.Context.init(Context.java:170)
>> at org.dspace.core.Context.(Context.java:126)
>> at 
>> org.dspace.harvest.HarvestScheduler.scheduleLoop(HarvestScheduler.java:149)
>> at 
>> org.dspace.harvest.HarvestScheduler.run(HarvestScheduler.java:140)
>> at java.lang.Thread.run(Unknown Source)
>> Exception in thread "Thread-4" 
>> org.dspace.core.exception.DatabaseSchemaValidationException: The schema 
>> validator returned: null
>> at org.dspace.core.Context.init(Context.java:170)
>> at org.dspace.core.Context.(Context.java:126)
>> at 
>> org.dspace.harvest.HarvestScheduler.scheduleLoop(HarvestScheduler.java:234)
>> at 
>> org.dspace.harvest.HarvestScheduler.run(HarvestScheduler.java:140)
>> at java.lang.Thread.run(Unknown Source)
>>
>>
>> The log showed the message below after running the command dspace harvest 
>> -S:
>>
>> 2018-09-12 13:14:57,708 FATAL org.dspace.core.Context @ Cannot obtain the 
>> bean which provides a database connection. Check previous entries in the 
>> dspace.log to find why the db failed to initialize. The schema validator 
>> returned: null
>> 2018-09-12 13:14:57,709 ERROR org.dspace.harvest.HarvestScheduler @ 
>> Exception on iteration: 0
>> 2018-09-12 13:14:57,713 FATAL org.dspace.core.Context @ Cannot obtain the 
>> bean which provides a database connection. Check previous entries in the 
>> dspace.log to find why the db failed to initialize. The schema validator 
>> returned: null
>>
>> When using the Harvesting tab in the XMLUI control panel, after clicking 
>> Start Harvester, the page returned this message:
>>
>> failed to lazily initialize a collection of role: 
>> org.dspace.content.DSpaceObject.metadata, could not initialize proxy - no 
>> Session
>>
>> Although when I press the back button of the browser, the status says 
>> that the scheduler is waiting for collections to harvest. It seems that the 
>> automatic scheduler from the UI is now running although it didn't harvest 
>> any new items from the collections that I've set up for harvesting because 
>> I have been receiving email messages from the server informing me of a 
>> Harvest error. Below is the content of the harvest error message:
>>
>> Collection 5bee1194-648c-4136-8671-ddc43fc3f85f failed on harvest:
>>
>> Date:   9/11/18 6:25 PM
>> Status Flag:-1
>>
>> We need at least an eperson or a group in order to create a resource 
>> policy.
>>
>> Exception:
>> java.lang.IllegalArgumentException: We need at least an eperson or a 
>> group in order to create a resource policy.
>> at org.dspace.authorize.AuthorizeServiceImpl.
>> createResourcePolicy(AuthorizeServiceImpl.java:777)
>> at org.dspace.authorize.AuthorizeServiceImpl.addPolicy(
>> AuthorizeServiceImpl.java:533)
>> at org.dspace.content.WorkspaceItemServiceImpl.create(
>> WorkspaceItemServiceImpl.java:99)
>> at org.dspace.harvest.OAIHarvester.processRecord(
>> OAIHarvester.java:539)
>> at org.dspace.harvest.OAIHarvester.runHarvest(
>> OAIHarvester.java:367)
>> at org.dspace.harvest.HarvestThread.runHarvest(
>> HarvestThread.java:57)
>> at org.dspace.harvest.HarvestThread.run(HarvestThread.java:41)
>> at java.lang.Thread.run(Unknown Source)
>>
>> So I would like to ask for help if anyone have ever encountered the 
>> errors above and how did you resolve it? I tried to harvest the collection 
>> that is giving me these errors in the dspace demo site using the same 
>> harvest_type and metadata_format and the harvest is successful. I just want 
>> to harvest automatically so that I don't have to run the harvest manually.
>>
>> Thanks in advance,
>> euler
>>
>

-- 
All messages to this mailing list should adhere 

[dspace-tech] Weird XML/DRI behavior

[Cameron, Jacob]

Hi Everyone,

I've made some customizations to our front page to add searches for Series and 
Type under the browse, all of DSpace area.

When we just us the url, https://opus.uleth.ca they do not show up.  It shows 
up as the screenshot labelled without XML or DRI.  However, if I use 
https://opus.uleth.ca?xml  or https://opus.uleth.ca?dri they show up properly.  
I've tried Chrome, Opera, Firefox and Edge.  It happens in all of those.  
However if I'm on a mobile device, android or apple, they show up fine without 
the ?xml or ?dri.  Any thoughts?

I have tried everything I can think of.

Jake

--
Jake Cameron, BCS(UNB)
Systems Support Specialist III
Information Systems and Technical Services University of Lethbridge Library
Phone:(403)329-2756
This e-mail, including any and all attachments, is only for the use of the 
intended recipient(s) and may contain information that is confidential or 
privileged. If you are not the intended recipient, you are advised that any 
dissemination, copying or other use of this e-mail is prohibited. Please notify 
the sender of the error in communication by return e-mail and destroy all 
copies of this e-mail. Thank you.

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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] solr

[Tim Donohue]

Hello Gilbert,

Sorry for the delayed response.  The error you are getting from Solr seems
to be "Invalid content type", which essentially means that Solr is *not*
responding in the format that is expected.  See this question on
StackOverflow for example:
https://stackoverflow.com/questions/39252934/solrj-invalid-content-type

To me, this sounds like DSpace is still not able to "find" Solr properly.
I would highly recommend looking at your configuration to ensure that it is
pointing to Solr on the proper port and path.  Especially, the
"discovery.search.server" configuration in your "discovery.cfg" file:
https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace/config/modules/discovery.cfg#L8

Make sure that the path in that configuration *is responding* and it
actually is Solr.  You could try doing a "wget" query to verify that Solr
is responding properly, for example:

wget -O - http://localhost:8080/solr/search/select?q=test

Again, let us know what you find and if you need more help.

Tim

On Wed, Oct 31, 2018 at 1:37 PM gilbert kunonga  wrote:

> I recently upgrade to dspace 6.3 from 6.2
>
>
> On Wednesday, 31 October 2018 18:42:01 UTC+2, Tim Donohue wrote:
>
>> Hi Gilbert,
>>
>> Are you able to reindex your site?  Try running:
>>
>> [dspace]/bin/dspace index-discovery -b
>>
>> This will run a full reindex (of all browse indexes). See:
>> https://wiki.duraspace.org/display/DSDOC6x/Discovery#Discovery-DiscoverySolrIndexMaintenance
>>
>>
>> If this command doesn't work, it's possible that a past reindex failed
>> and left around a Solr "write.lock" file.  You can safely delete that
>> "write.lock", restart Tomcat and then do a full reindex (see above), if
>> Solr keeps complaining about the "write.lock" file.
>>
>> If none of this helps, it'd be good to better understand what version of
>> DSpace you are running and your installation environment.  Send us an
>> update on this list and maybe we can come up with some other ideas of what
>> may be going on.
>>
>> - Tim
>>
>> On Tue, Oct 30, 2018 at 11:05 AM gilbert kunonga 
>> wrote:
>>
> I am getting the following error when i try to browse by type Author,
>>> Title, Issue Date or Subject. Communities and Collections are displaying.
>>> Solr.log is showing [dspace]/solr/authority/data/index/write.lock is
>>> locked for writing
>>>
>>> Java stacktrace: org.apache.http.ParseException: Invalid content type:
>>> at org.apache.http.entity.ContentType.parse(ContentType.java:273) at
>>> org.apache.solr.client.solrj.impl.HttpSolrServer.executeMethod(HttpSolrServer.java:496)
>>> at
>>> org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:210)
>>> at
>>> org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:206)
>>> at
>>> org.apache.solr.client.solrj.request.QueryRequest.process(QueryRequest.java:91)
>>> at org.apache.solr.client.solrj.SolrServer.query(SolrServer.java:310) at
>>> org.dspace.discovery.SolrServiceImpl.search(SolrServiceImpl.java:1610) at
>>> org.dspace.browse.SolrBrowseDAO.getSolrResponse(SolrBrowseDAO.java:201) at
>>> org.dspace.browse.SolrBrowseDAO.doCountQuery(SolrBrowseDAO.java:257) at
>>> org.dspace.browse.BrowseEngine.getTotalResults(BrowseEngine.java:759) at
>>> org.dspace.browse.BrowseEngine.browseByValue(BrowseEngine.java:453) at
>>> org.dspace.browse.BrowseEngine.browse(BrowseEngine.java:96) at
>>> org.dspace.app.xmlui.aspect.artifactbrowser.ConfigurableBrowse.getBrowseInfo(ConfigurableBrowse.java:859)
>>> at
>>> org.dspace.app.xmlui.aspect.artifactbrowser.ConfigurableBrowse.addBody(ConfigurableBrowse.java:280)
>>> at
>>> org.dspace.app.xmlui.wing.AbstractWingTransformer.startElement(AbstractWingTransformer.java:234)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:498) at
>>> org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71)
>>> at com.sun.proxy.$Proxy400.startElement(Unknown Source) at
>>> org.apache.cocoon.components.sax.XMLTeePipe.startElement(XMLTeePipe.java:87)
>>> at
>>> org.apache.cocoon.xml.AbstractXMLPipe.startElement(AbstractXMLPipe.java:94)
>>> at
>>> org.dspace.app.xmlui.wing.AbstractWingTransformer.startElement(AbstractWingTransformer.java:251)
>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>> at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>> at java.lang.reflect.Method.invoke(Method.java:498) at
>>> org.apache.cocoon.core.container.spring.avalon.PoolableProxyHandler.invoke(PoolableProxyHandler.java:71)
>>> at com.sun.proxy.$Proxy400.startElement(Unknown Source) at
>>> 

Re: [dspace-tech] How to set in OAI identify verb the available compression options?

[Tim Donohue]

Hi Pablo,

Unfortunately, DSpace's OAI-PMH interface does not support
ResponseCompression at this time.

As noted in the OAI-PMH specification (which you linked to), that's an
optional feature.  If an OAI-PMH server does support compression, it should
say so on the "Identify" response.  DSpace does not claim to support
compression on the Identify response, see for example:
https://demo.dspace.org/oai/request?verb=Identify

- Tim

On Wed, Nov 7, 2018 at 10:04 AM Pablo de Albuquerque 
wrote:

> Hi!
>
> I was trying to set the OAI ResponseCompression
> 
>  options
> when handling the Identify verb. How can I do it from DSpace?
> Currently I'm using DSpace 5.8 with XOAI 3.2.10
>
> Thanks,
>
> de Albuquerque Pablo
> SEDICI, Repositorio Insitucional de la UNLP
>
> --
> All messages to this mailing list should adhere to the DuraSpace Code of
> Conduct: https://duraspace.org/about/policies/code-of-conduct/
> ---
> 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

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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] how to make contents view directly on browser rather than downloading them

[Tim Donohue]

Hello Assay,

Unfortunately, DSpace does not yet support this out-of-the-box.  However, I
know several service providers have DSpace plugins (available for purchase)
that support "Document Viewer" functionality (where you can page through a
document in your web browser).  So, if you are interested in such a feature
immediately, you could consider contacting some of our service providers:
https://duraspace.org/dspace/resources/service-providers/

If anyone else on this mailing list has successfully implemented a
customization to provide this functionality, hopefully they will share it
in this thread.

- Tim

On Wed, Nov 7, 2018 at 4:55 AM Ze Victor Harry  wrote:

> hi everybody i don't know if this has been posted yet  but i want contents
> specially pdf files to be opened directly on the browser rather than
> downloading them because i have huge data and i don't want the users to
> download them but only view them.currently if the size of the file is <5 MB
> it can be opened but not to files that exceed 5 MB.any solution for that?
>
> regards
> Assay
>
> --
> All messages to this mailing list should adhere to the DuraSpace Code of
> Conduct: https://duraspace.org/about/policies/code-of-conduct/
> ---
> 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

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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] Current Active Workflow

[Tim Donohue]

Hi Hayden,

Unfortunately, no, this doesn't exist in the XMLUI (to my knowledge).
While you can run both UIs in parallel, I think you'll have to have users
login *separately* to the XMLUI vs JSPUI. For example, authenticating in
the XMLUI does *not* automatically authenticate you in the JSPUI (they do
not share authentication information or tokens).   That's the only drawback
I see to your approach.

- Tim

On Wed, Nov 7, 2018 at 6:37 AM Hayden Young  wrote:

> Hi
>
> There is a feature in JSPUI called "Currently Active Workflows". It is my
> understanding that this feature gives admins the ability to monitor all
> workflow items under review and also abort or cancel them if required.
>
> Is there a similar feature in XMLUI? If not, what is the drawback to
> running the JSPUI webapp for only this feature and using URL rewrites to
> redirect users away from other parts of the JSPUI interface?
>
> Any insight much appreciated.
>
> --
> All messages to this mailing list should adhere to the DuraSpace Code of
> Conduct: https://duraspace.org/about/policies/code-of-conduct/
> ---
> 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

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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] New DSpace 6.x Installation Recommendations

[Tim Donohue]

Hi Rob,

Just as a note, we try and note any "gotchas" directly in the Installation
instructions:
https://wiki.duraspace.org/display/DSDOC6x/Installing+DSpace#InstallingDSpace-PrerequisiteSoftware

You'll notice various notes there on versions of Tomcat or similar to avoid
(and why to avoid them).  Generally, I agree that you should look towards
OpenJDK 1.8 (Java 8), and either Tomcat 7 or 8 (either will work fine).
You must have PostgreSQL 9.4 or above (10.x works fine too), with pgcrypto
installed.

If you need other specific advice, let us know on this list.

- Tim

On Wed, Nov 7, 2018 at 9:25 AM Alan Orth  wrote:

> Dear Rob,
>
> With DSpace 6.x I think you should be targeting Tomcat 8.5 and OpenJDK
> 1.8, which are both default in Ubuntu 18.04. As for PostgreSQL, I have been
> using the official binary repositories from the PostgreSQL project[0]
> itself so I have more flexibility with versions. We've been using version
> 9.5 for a few years and are testing 9.6 in our staging environment, and I
> think I even saw some compatibility updates for PostgreSQL 10 in the DSpace
> 6.x branch or Jira (?).
>
> [0] https://www.postgresql.org/download/linux/ubuntu/
>
> Cheers,
>
> On Tue, Nov 6, 2018 at 9:50 PM Rob Jenson  wrote:
>
>> I am setting up a DSpace 6.x dedicated server for the first time and I am
>> looking for any clues or wisdom from those who have walked this path before.
>>
>> I have been reading through the installation docs and there are several
>> choices to be made. We are going to build on Ubuntu 18.04 in a DigitalOcean
>> Droplet. Everything else is negotiable.
>>
>> This server will be a development-to-production installation, so
>> stability is desirable. It is a brand new installation with no existing
>> legacy data to be migrated or supported, so we can go with the newest
>> stable versions of software that DSpace relies upon.
>>
>> Specifically, what versions of OpenJDK and Tomcat have people been
>> building upon? Are there any other software version "gotchas" to be aware
>> of before configuring the server?
>>
>> Thanks,
>>
>> _rob_
>>
>> --
>> All messages to this mailing list should adhere to the DuraSpace Code of
>> Conduct: https://duraspace.org/about/policies/code-of-conduct/
>> ---
>> 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.
>>
>
>
> --
> Alan Orth
> alan.o...@gmail.com
> https://picturingjordan.com
> https://englishbulgaria.net
> https://mjanja.ch
> "In heaven all the interesting people are missing." ―Friedrich Nietzsche
>
> --
> All messages to this mailing list should adhere to the DuraSpace Code of
> Conduct: https://duraspace.org/about/policies/code-of-conduct/
> ---
> 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

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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] Example EPerson schema? Necessary EPerson schema fields?

[Tim Donohue]

Hello GG,

Those various "1234" fields in your schema are definitely not standard
"eperson" schema fields.  Here's the standard "eperson" schema that comes
with DSpace:

https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace/config/registries/eperson-types.xml

As you can see, DSpace expects there to be 4 fields:

eperson.firstname
eperson.lastname
eperson.phone
eperson.language

These four fields are used/required by DSpace to save information about
users who have registered in your system. While DSpace always allows
Administrators the ability to edit/changes schemas, no other "eperson"
fields are used by DSpace anywhere.

As for finding where a field may be in use, you can query the
"metadatavalue" table in the database with that "metadata_field_id" to see
where it is being used.  It's likely some object in your system has been
"linked" to that field in the "metadatavalue" table.  If you either remove
that metadata value or delete the object, you should be able to delete the
metadata field itself.

If you require more advice, let us know on this mailing list!

Good luck,

Tim

On Wed, Nov 7, 2018 at 9:40 AM  wrote:

> Hey everyone-
>
> Our DSpace instance was initially set up by someone no longer employed at
> our institution.  For whatever reason the EPerson schema reads like this:
>
> 194 eperson.javascript:alert(10379).1234
> 
> 1234
> 370 eperson.language
> 
> 3 eperson.lastname.1234
> 
> 1234
> 2 eperson.lastname
> 
> 149 eperson.ls.1234
> 
> 1234
> 363 eperson.password.1234
> 
> 362 eperson.password
> 
> 372 eperson.phone
> 
> 139 eperson.ProbePhishing.1234
> 
> 1234
> 183 eperson.alert(10339).1234
> 
> 1234
> 202 eperson.alert(4224).1234
> 
> 1234
> And so on...
>
> To do certain tasks we've been having to add fields to this.  For example,
> to add a new user through the UI we had to add 'eperson.phone.null' to keep
> it from throwing the following error:  "bad_dublin_core
> schema=eperson.phone.null. Metadata field does not exist!"  We'd like to
> proactively create these fields. Is there an example out-of-the-box eperson
> schema we could refer to on the web?  We wern't able to locate one.
> Alternately, would someone be willing to send us a list of fields that
> should be present in an un-customized eperson schema, or to copy and paste
> your schema into a document we could look over?  This would be much
> appreciated!
>
> A second question:  Both 'eperson.lastname.1234' and 'eperson.lastname'
> give an 'in use' error when one tries to delete them ("Metadata field
> eperson_lastname_1234 cannot be deleted as it is currently used by one or
> more objects.").  Most of the ...1234 fields can be deleted, meaning the
> system isn't using them.  Does anyone have any insight into why the
> 'eperson.lastname.1234' would be in use?
>
> Thank you so much for your help!
>
> -GG
>
>
>
> --
> All messages to this mailing list should adhere to the DuraSpace Code of
> Conduct: https://duraspace.org/about/policies/code-of-conduct/
> ---
> 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

-- 

[dspace-tech] How to set in OAI identify verb the available compression options?

[Pablo de Albuquerque]

Hi!

I was trying to set the OAI ResponseCompression 

 options 
when handling the Identify verb. How can I do it from DSpace? 
Currently I'm using DSpace 5.8 with XOAI 3.2.10

Thanks,

de Albuquerque Pablo
SEDICI, Repositorio Insitucional de la UNLP

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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] Example EPerson schema? Necessary EPerson schema fields?

[tuf04742]

Hey everyone- 

Our DSpace instance was initially set up by someone no longer employed at 
our institution.  For whatever reason the EPerson schema reads like this:  

194 eperson.javascript:alert(10379).1234 

 
1234
370 eperson.language 

 
3 eperson.lastname.1234 

 
1234
2 eperson.lastname 

 
149 eperson.ls.1234 

 
1234
363 eperson.password.1234 

 
362 eperson.password 

 
372 eperson.phone 

 
139 eperson.ProbePhishing.1234 

 
1234
183 eperson.alert(10339).1234 

 
1234
202 eperson.alert(4224).1234 

 
1234
And so on...  

To do certain tasks we've been having to add fields to this.  For example, 
to add a new user through the UI we had to add 'eperson.phone.null' to keep 
it from throwing the following error:  "bad_dublin_core 
schema=eperson.phone.null. Metadata field does not exist!"  We'd like to 
proactively create these fields. Is there an example out-of-the-box eperson 
schema we could refer to on the web?  We wern't able to locate one.  
Alternately, would someone be willing to send us a list of fields that 
should be present in an un-customized eperson schema, or to copy and paste 
your schema into a document we could look over?  This would be much 
appreciated!  

A second question:  Both 'eperson.lastname.1234' and 'eperson.lastname' 
give an 'in use' error when one tries to delete them ("Metadata field 
eperson_lastname_1234 cannot be deleted as it is currently used by one or 
more objects.").  Most of the ...1234 fields can be deleted, meaning the 
system isn't using them.  Does anyone have any insight into why the 
'eperson.lastname.1234' would be in use?  

Thank you so much for your help! 

-GG



-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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] New DSpace 6.x Installation Recommendations

[Alan Orth]

Dear Rob,

With DSpace 6.x I think you should be targeting Tomcat 8.5 and OpenJDK 1.8,
which are both default in Ubuntu 18.04. As for PostgreSQL, I have been
using the official binary repositories from the PostgreSQL project[0]
itself so I have more flexibility with versions. We've been using version
9.5 for a few years and are testing 9.6 in our staging environment, and I
think I even saw some compatibility updates for PostgreSQL 10 in the DSpace
6.x branch or Jira (?).

[0] https://www.postgresql.org/download/linux/ubuntu/

Cheers,

On Tue, Nov 6, 2018 at 9:50 PM Rob Jenson  wrote:

> I am setting up a DSpace 6.x dedicated server for the first time and I am
> looking for any clues or wisdom from those who have walked this path before.
>
> I have been reading through the installation docs and there are several
> choices to be made. We are going to build on Ubuntu 18.04 in a DigitalOcean
> Droplet. Everything else is negotiable.
>
> This server will be a development-to-production installation, so stability
> is desirable. It is a brand new installation with no existing legacy data
> to be migrated or supported, so we can go with the newest stable versions
> of software that DSpace relies upon.
>
> Specifically, what versions of OpenJDK and Tomcat have people been
> building upon? Are there any other software version "gotchas" to be aware
> of before configuring the server?
>
> Thanks,
>
> _rob_
>
> --
> All messages to this mailing list should adhere to the DuraSpace Code of
> Conduct: https://duraspace.org/about/policies/code-of-conduct/
> ---
> 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.
>


-- 
Alan Orth
alan.o...@gmail.com
https://picturingjordan.com
https://englishbulgaria.net
https://mjanja.ch
"In heaven all the interesting people are missing." ―Friedrich Nietzsche

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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] Re: HTTPS and SOLR

[Alan Orth]

Dear Jacob,

I think it's better if you add another Tomcat connector to handle the
un-encrypted HTTP. We use nginx + TLS in front of our Tomcat and the "main"
connector specifically has to know about the reverse port mapping 443→8443
with HTTPS scheme, so we added a plain HTTP connector for localhost:







Then in our DSpace configuration we point Solr to this localhost:8081.

Hope that helps,

On Tue, Nov 6, 2018 at 11:49 PM Cameron, Jacob 
wrote:

> Hi Mark,
>
>
>
> It’s because the cert is wildcard for our domain it is breaking going to
> the localhost for SOLR.  With SOLR setup for localhost only, it got
> grumpy.  I’ve found an easy way to work around it now.  I hope to get
> apache httpd working on it in the future.
>
>
>
> Jake
>
> --
>
> Jake Cameron, BCS(UNB)
>
> Systems Support Specialist III
>
> Information Systems and Technical Services University of Lethbridge Library
>
> Phone:(403)329-2756
>
> This e-mail, including any and all attachments, is only for the use of the
> intended recipient(s) and may contain information that is confidential or
> privileged. If you are not the intended recipient, you are advised that any
> dissemination, copying or other use of this e-mail is prohibited. Please
> notify the sender of the error in communication by return e-mail and
> destroy all copies of this e-mail. Thank you.
>
>
>
> *From:* dspace-tech@googlegroups.com  *On
> Behalf Of *Mark H. Wood
> *Sent:* Tuesday, November 6, 2018 11:27 AM
> *To:* DSpace Technical Support 
> *Subject:* [dspace-tech] Re: HTTPS and SOLR
>
>
>
> On Monday, November 5, 2018 at 6:11:29 PM UTC-5, jacob.cameron wrote:
>
> Can I have SOLR secured under a wildcard SSL certificate? I’ve installed
> our cert and forced HTTPS I’m tomcat, but SOLR keeps giving a 302 error now
> and when I browse it it tells me that it’s an invalid cert. I haven’t been
> able to figure a way around it. We aren’t using Apache HTTPD to configure
> our ports.
>
>
>
>
>
>
>
> There are any number of ways a cert. can be invalid.  Which specific one
> does your browser show you?  (Browsers are so "helpful" these days that you
> may need to dig...and dig...to get down to the real reason.)  A less
> "friendly", more precise tool such as 'openssl s_client' may provide better
> information.
>
>
>
> HTTP status 302 ("Found") is a redirection.  Tomcat (not Solr) is saying
> that the resource exists but you have to ask for it at a different
> location.  Is DSpace configured to contact Solr via HTTPS?  Does
> 'bin/dspace dsprop -property solr.server' show the https: scheme?
>
> --
> All messages to this mailing list should adhere to the DuraSpace Code of
> Conduct: https://duraspace.org/about/policies/code-of-conduct/
> ---
> 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.
>
> --
> All messages to this mailing list should adhere to the DuraSpace Code of
> Conduct: https://duraspace.org/about/policies/code-of-conduct/
> ---
> 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.
>


-- 
Alan Orth
alan.o...@gmail.com
https://picturingjordan.com
https://englishbulgaria.net
https://mjanja.ch
"In heaven all the interesting people are missing." ―Friedrich Nietzsche

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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: Problemas para ver archivos de un item

[Jose Miguel Ravasi]

Hola Santi
Gracias por tu respuesta.
Me falto aclarar que la carpeta assetstore ya la tenia copiada desde el 
entorno de producción. Perdón, no lo aclare en su momento.
Veo algunos items y otros no.
Aun no encontre como solucionarlo
Saludos


José M Ravasi
Biblioteca FI UNMDP
rinfi.fi.mdp.edu.ar



El miércoles, 7 de noviembre de 2018, 10:35:57 (UTC-3), 
san...@sedici.unlp.edu.ar escribió:
>
> Hola José,
>
> El problema es que en la base de datos no están guardados los archivos, 
> sino que solo los metadatos relacionados con ellos. Los Bitstreams se 
> guardan efectivamente en la carpeta assetstore. 
> Es por ello que el pg_dump/pgrestore no funciona para importar/exportar 
> archivos, para ello se debe copiar el contenido de la carptea assetstore 
> desde entorno de produccion al de desarrollo.
>
> Espero que haya servido la ayuda
> Santi
>
> El viernes, 26 de octubre de 2018, 13:47:03 (UTC-3), Jose Miguel Ravasi 
> escribió:
>>
>> Estimados
>> Tengo una instalación de Dspace 6.2 en Debian.
>> Como se trata de una instalación para desarrollo, importe los registros 
>> mediante un pg_dump/pgrestore desde una instalación de producción que 
>> funciona ok.
>> El problema que tengo es que me muestra los archivos de algunos items si 
>> y de otros no.
>> No se que pasa o porque ocurre este problema
>> Lo que me devuelve es 
>> java.io.FileNotFoundException: 
>> /home/dspace/assetstore/95/20/25/95202521001550446181969613383993908672 (No 
>> existe el fichero o el directorio)
>>
>> Si alguno tiene una respuesta a este problema, se lo voy a agradecer.
>> Saludos
>>
>> José M Ravasi
>> Biblioteca FI UNMDP
>> rinfi.fi.mdp.edu.ar
>>
>>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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] 5.10 Discover/Search showing final thumbnail, not first

[Alex Fletcher]

We have a collection of art objects/photos on our local implementation, and 
for many objects, the thumbnail that appears on the search results page is 
taken from the last image of the entry, rather than the first one (for 
example a detail of the feet rather than of the whole work). This is a 
problem, because art historians find information by looking at images, and 
so we have carefully selected which is the first image, in order to 
generate the most helpful thumbnail. Now, on the search results page, you 
are more likely to see a secondary image (the building in which a sculpture 
is located or feet, or another odd detail of a sculpture), which makes it 
difficult to use the database for visual research. The odd thing is that 
when you click on the entry, the thumbnail on the individual object page is 
taken from the first image of the entry. So for example on this search page:

https://qspace.library.queensu.ca/discover?scope=1974/14832=10=6=Image_by=none=0

 
And then the individual entries:
   
   - https://qspace.library.queensu.ca/handle/1974/24713
   - https://qspace.library.queensu.ca/handle/1974/24700
   - https://qspace.library.queensu.ca/handle/1974/24701
   
Has anyone come across this previously and have any advice as to how to 
correct this?


Thanks,


Alex Fletcher

Queen's University Library

Kingston, Ontario, Canada

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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: Problemas para ver archivos de un item

[santit]

Hola José,

El problema es que en la base de datos no están guardados los archivos, 
sino que solo los metadatos relacionados con ellos. Los Bitstreams se 
guardan efectivamente en la carpeta assetstore. 
Es por ello que el pg_dump/pgrestore no funciona para importar/exportar 
archivos, para ello se debe copiar el contenido de la carptea assetstore 
desde entorno de produccion al de desarrollo.

Espero que haya servido la ayuda
Santi

El viernes, 26 de octubre de 2018, 13:47:03 (UTC-3), Jose Miguel Ravasi 
escribió:
>
> Estimados
> Tengo una instalación de Dspace 6.2 en Debian.
> Como se trata de una instalación para desarrollo, importe los registros 
> mediante un pg_dump/pgrestore desde una instalación de producción que 
> funciona ok.
> El problema que tengo es que me muestra los archivos de algunos items si y 
> de otros no.
> No se que pasa o porque ocurre este problema
> Lo que me devuelve es 
> java.io.FileNotFoundException: 
> /home/dspace/assetstore/95/20/25/95202521001550446181969613383993908672 (No 
> existe el fichero o el directorio)
>
> Si alguno tiene una respuesta a este problema, se lo voy a agradecer.
> Saludos
>
> José M Ravasi
> Biblioteca FI UNMDP
> rinfi.fi.mdp.edu.ar
>
>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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] Current Active Workflow

[Hayden Young]

Hi

There is a feature in JSPUI called "Currently Active Workflows". It is my 
understanding that this feature gives admins the ability to monitor all 
workflow items under review and also abort or cancel them if required.

Is there a similar feature in XMLUI? If not, what is the drawback to 
running the JSPUI webapp for only this feature and using URL rewrites to 
redirect users away from other parts of the JSPUI interface?

Any insight much appreciated.

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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: CAPTCHA/reCAPTCHA for the Feedback form?

[santit]

Hi!

At http://digital.cic.gba.gob.ar/, we have implemented a simple math 
captcha on the users feedback form. If you are interested here is the commit 

.
We first used Google's reCAPTCHA but we really didn't need such big tool 
for this, so we implemented our own.
It's a simple javascript function which shows two numbers on the screen and 
ask the user to introduce the sum result.

I hope it helps
Santi


El viernes, 2 de noviembre de 2018, 14:33:07 (UTC-3), Darryl Friesen 
escribió:
>
>
> Has anyone implemented some form of CAPTCHA for use on the Feedback form?  
> We seem to be getting more and more spam this way.
>
> We've used Google's reCAPTCHA on a few other projects and if memory 
> serves, it requires some validation after submission.  So for use with 
> DSpace I assume that would mean changes to some Java classes somewhere, 
> correct?  Has anyone already implemented this, or have any other 
> suggestions on cutting down spam through the feedback mechanism?
>
> Thanks!
>
> - Darryl
>
>  
>
> --
>
> Darryl Friesen, B.Sc., Programmer/Analystdarryl@usask.ca 
> 
>
> Library Systems & Information Technology,http://library.usask.ca/
>
> University of Saskatchewan Library
>
> --
>
> "Go not to the Elves for counsel, for they will say both no and yes"
>
>  
>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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] for a specific community I want to publish without approval, what im doing wrong ?

[Damian]

I found the problem, I had created a user the stage accept / reject item in 
the community configuration thanks for answering best regards


El martes, 6 de noviembre de 2018, 7:53:02 (UTC-3), Damian escribió:
>
> Hi Paul, thanks for answering
> but if i don´t setup this collection, after submission process, dspace 
> take the DEFAULT Workflow.
> The Default workflow is assigned the carousel type workflow 
> Kind regards
>
>
>
> the default workfloww is assigned the carousel type
> El martes, 6 de noviembre de 2018, 4:37:21 (UTC-3), Paul Münch escribió:
>>
>> Hello,
>>
>> if you want accept items without any workflow steps, then do not setup a 
>> workflow group in the target collection. You do not have to configure 
>> anything for it in the 'workflow.xml'. 
>>
>> Kind regards,
>>
>> Paul Münch
>>
>> Am 06.11.18 um 01:21 schrieb Damian:
>>
>> im working with dspace 6.0 xmlui  mirage2 theme 
>>
>>  modifiy workflow.xml 
>>
>> for a specific community (Reposit/4) , i want to publish without 
>> approval, all others community get default workflow
>>
>> but im doing something wrong because is not working 
>>
>> 
>> 
>> 
>> 
>> 
>> 
>>  
>> 
>> 
>> 
>>  
>> 
>> ColeccQGral
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> -- 
>> All messages to this mailing list should adhere to the DuraSpace Code of 
>> Conduct: https://duraspace.org/about/policies/code-of-conduct/
>> --- 
>> 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.
>>
>>
>> -- 
>> Philipps-Universität Marburg | UB 
>> Digitale Dienste | Deutschhausstraße 9 | D018
>> Tel. +49 06421 28-24624  
>> --
>>
>>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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] how to make contents view directly on browser rather than downloading them

[Ze Victor Harry]

hi everybody i don't know if this has been posted yet  but i want contents
specially pdf files to be opened directly on the browser rather than
downloading them because i have huge data and i don't want the users to
download them but only view them.currently if the size of the file is <5 MB
it can be opened but not to files that exceed 5 MB.any solution for that?

regards
Assay

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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.