Re: [dspace-tech] Re: Submit Feature requests to DSpace

[George Kozak]

Thanks, Mark!  Will do!
George Kozak
Cornell University

On Fri, May 26, 2017 at 9:11 AM, Mark H. Wood  wrote:

> On Thursday, May 25, 2017 at 2:32:09 PM UTC-4, George Kozak wrote:
>>
>> Hi,
>> My management asked me if we could submit a request for an enhancement to
>> be made to  DSpace.  How do we go about submitting feature requests for
>> consideration for a new release?
>>
>>
>  Please file an issue at https://jira.duraspace.org/ (using the Create
> button) for project DSpace, selecting "issue type" New Feature (for new
> features) or Improvement (for improvements to existing features).  Bug
> reports are also welcome.  Issues are reviewed regularly.
>
> --
> 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.
>



-- 
***
George Kozak
Digital Library Specialist
Cornell University Library - IT
218 Olin Library
Cornell University
Ithaca, NY 14853
607-255-8924
g...@cornell.edu

-- 
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] google scholar

[Monika Mevenkamp]

Tim 

thanks for your answer - yes sitemaps are up and I just fixed my robots.txt 
file to allow crawlers in. 

But when I try to log into the Google webmaster tool's 
  search console,  I get 
the message 
admin.google.com is for G Suite accounts only. Regular Gmail accounts cannot be 
used to sign in to admin.google.com. Learn more 

when I learn more I get to a page that offers a 14 day trial. Is there another 
way to invite Google to crawl my instance ? 

It looks to me that Google now wants to make money on both ends, webmaster 
support and advertising.

Monika

 
Monika Mevenkamp
mo.me...@gmail.com

http://mo-meven.tumblr.com/
http://mcmprogramming.com/mo.meven/



> On May 25, 2017, at 4:37 PM, Tim Donohue  wrote:
> 
> Hi Monika,
> 
> We are in touch with Google Scholar staff on a regular basis (at least 
> yearly), and they forward along any issues they are seeing with DSpace sites 
> so that we can resolve them. Essentially, out of the box, DSpace is Google 
> Scholar compliant. So, you need not modify any of the default settings, 
> unless you have custom metadata fields you wish to make available to Google 
> Scholar, etc.
> 
> Google Scholar used to have a published way of requesting an index of the 
> site. But, I'm no longer finding it among their resources. However, I know, 
> like Google crawlers, the Google Scholar crawlers are pretty smart about 
> finding *any* public repository out there that is linked to from elsewhere.  
> Also, you could use Google Webmaster tools to notify the Google crawlers (and 
> I believe Google Scholar is notified as well).
> 
> Also, we have a reference in the DSpace documentation regarding optimizing 
> SEO for DSpace.  Google Scholar highly recommends enabling Sitemaps in DSpace 
> (as it makes it much easier to locate all the content): 
> https://wiki.duraspace.org/display/DSDOC5x/Search+Engine+Optimization 
> 
> 
> - Tim
> 
> 
> On Thu, May 25, 2017 at 3:17 PM Monika Mevenkamp  > wrote:
> I want Google Scholar to come and index my DSpace instance (v5) 
> The instance generates the meta tags shown below 
> 
> The Google Scholar requirements documentation at scholar/inclusion 
>  talks 
> about citation_* and DC.* meta tags. It does not mention DCTERMS.* tags. On 
> the other hand the documentation says: DSpace is fine.   
> 
> So, do I have to adjust the out of the box settings ?   
> 
> I could not find anything about nominating my instance to be indexed with 
> Google Scholar. 
> Can I do that so Google Scholar knows to come crawling ?
> 
> Monika
> 
> 
> http://purl.org/dc/terms/ 
> ">
> http://purl.org/dc/elements/1.1/ 
> ">
> 
> 
> 
>  scheme="DCTERMS.W3CDTF">
>  scheme="DCTERMS.W3CDTF">
>  scheme="DCTERMS.W3CDTF">
> 
> 
>  content="http://arks.princeton.edu/ark:/88435/pr19w4b 
> " scheme="DCTERMS.URI">
> 
> 
>  scheme="DCTERMS.RFC1766">
> 
> 
> 
> 
> 
>  scheme="DCTERMS.W3CDTF">
> 
> 
> 
> 
> 
>  content="http://oar.princeton.edu/jspui/handle/88435/pr19w4b 
> ">
> 
>  content="http://oar.princeton.edu/jspui/bitstream/88435/pr19w4b/1/1112.5026v1.pdf
>  ">
> 
>  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.

Re: [dspace-tech] AWS S3 Connection Pool Error

['Peter Dietz' via DSpace Technical Support]

The TransferManager code just made the implementation simpler. Otherwise
you have to write code that determines how large the bitstream is, and if
its small, transfer the file to somewhere in memory, and then stream that,
or if its larger, you could store it to temp file, and then stream that.
You also have to ensure that you delete the temp file when complete. If its
very large, larger than 5GB, you can't transfer that in a single GET. The
TransferManager code handles the multipart uploads and download. Also, it
can give a performance benefit, where GET and PUT can be done multi-thread
multi-part, instead of a single long running GET or PUT to S3. The
transfermanager also seemed to do a good job of closing resources when the
transfer was complete.

http://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/s3/transfer/TransferManager.html
High level utility for managing transfers to Amazon S3.

TransferManager provides a simple API for uploading content to Amazon S3,
and makes extensive use of Amazon S3 multipart uploads to achieve enhanced
throughput, performance and reliability.

When possible, TransferManager attempts to use multiple threads to upload
multiple parts of a single upload at once. When dealing with large content
sizes and high bandwidth, this can have a significant increase on
throughput.

TransferManager is responsible for managing resources such as connections
and threads; share a single instance of TransferManager whenever possible.
TransferManager, like all the client classes in the AWS SDK for Java, is
thread safe. Call TransferManager.shutdownNow() to release the resources
once the transfer is complete.


Peter Dietz
Longsight
www.longsight.com
pe...@longsight.com
p: 740-599-5005 x809

On Fri, May 26, 2017 at 9:18 AM,  wrote:

> Thanks Peter,
>
> I have implemented most of your changes on the DSpace 6 code and now I'm
> not running out of connections.  I haven't updated to use the Transfer
> Manager yet and I was wondering what advantage you found using the Transfer
> Manager over the original implementation.
>
> Thanks,
> Justin
>
> On Thursday, May 18, 2017 at 11:02:22 AM UTC-4, Peter Dietz wrote:
>>
>> Hi Justin,
>>
>> With production use, and encountering similar issues to you, I have made
>> fixes to our code to protect against http connection leaking with AWS S3
>> assetstore, and also to handle larger uploads/downloads. Here is some
>> commit history to the (5.x) S3BitStore: https://github.com
>> /LongsightGroup/DSpace/commits/longsight-5.6/dspace-api/src/
>> main/java/org/dspace/storage/bitstore/impl/S3BitStore.java
>>
>>
>> 
>> Peter Dietz
>> Longsight
>> www.longsight.com
>> pe...@longsight.com
>> p: 740-599-5005 x809 <(740)%20599-5005>
>>
>> On Thu, May 18, 2017 at 10:57 AM, Claudia Jürgen <
>> claudia...@tu-dortmund.de> wrote:
>>
>>> Hello jcdalton,
>>>
>>> which UI are you using and are you using google analytics?
>>>
>>> For the time being you may set the config parameter db.maxidle to
>>> something else than -1
>>> see
>>> https://jira.duraspace.org/browse/DS-3564?jql=text%20~%20%22maxidle%22
>>>
>>> Hope this helps
>>>
>>> Claudia Jürgen
>>>
>>>
>>> Am 18.05.2017 um 16:25 schrieb jcda...@email.wm.edu:
>>>
 I'm using S3 as a bitstore on DSpace 6 and I'm coming up with a lot of
 errors like the following:

 com.amazonaws.http.AmazonHttpClient @ Unable to execute HTTP request:
 Timeout waiting for connection from pool
 org.apache.http.conn.ConnectionPoolTimeoutException: Timeout waiting
 for
 connection from pool

 It looks to me like either DSpace isn't closing the connections as it
 should.  Anyone else had this issue?

 Thanks


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

[dspace-tech] Re: Change limit import metadata via jspui?

[Mark H. Wood]

On Wednesday, May 24, 2017 at 2:36:01 PM UTC-4, Brendow Adriel wrote:
>
> I need import a file csv with 1000 rows. How i can change the limit 
> importation of metadatas via interface?
>

I haven't done batch metadata editing, but I think you can raise the limit 
by editing [DSpace]/config/modules/bulkedit.cfg and changing the value of 
'bulkedit.gui-item-limit'.  You'll need to restart DSpace before the change 
will be effective.

See:

https://wiki.duraspace.org/display/DSDOC6x/Batch+Metadata+Editing
https://wiki.duraspace.org/display/DSDOC6x/Batch+Metadata+Editing+Configuration

Do take note of the warning about problems that may arise when importing 
large CSV files.

-- 
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] AWS S3 Connection Pool Error

[jcdalton]

Thanks Peter,

I have implemented most of your changes on the DSpace 6 code and now I'm 
not running out of connections.  I haven't updated to use the Transfer 
Manager yet and I was wondering what advantage you found using the Transfer 
Manager over the original implementation.

Thanks,
Justin

On Thursday, May 18, 2017 at 11:02:22 AM UTC-4, Peter Dietz wrote:
>
> Hi Justin,
>
> With production use, and encountering similar issues to you, I have made 
> fixes to our code to protect against http connection leaking with AWS S3 
> assetstore, and also to handle larger uploads/downloads. Here is some 
> commit history to the (5.x) S3BitStore: 
> https://github.com/LongsightGroup/DSpace/commits/longsight-5.6/dspace-api/src/main/java/org/dspace/storage/bitstore/impl/S3BitStore.java
>
>
> 
> Peter Dietz
> Longsight
> www.longsight.com
> pe...@longsight.com 
> p: 740-599-5005 x809
>
> On Thu, May 18, 2017 at 10:57 AM, Claudia Jürgen <
> claudia...@tu-dortmund.de > wrote:
>
>> Hello jcdalton,
>>
>> which UI are you using and are you using google analytics?
>>
>> For the time being you may set the config parameter db.maxidle to
>> something else than -1
>> see
>> https://jira.duraspace.org/browse/DS-3564?jql=text%20~%20%22maxidle%22
>>
>> Hope this helps
>>
>> Claudia Jürgen
>>
>>
>> Am 18.05.2017 um 16:25 schrieb jcda...@email.wm.edu :
>>
>>> I'm using S3 as a bitstore on DSpace 6 and I'm coming up with a lot of
>>> errors like the following:
>>>
>>> com.amazonaws.http.AmazonHttpClient @ Unable to execute HTTP request:
>>> Timeout waiting for connection from pool
>>> org.apache.http.conn.ConnectionPoolTimeoutException: Timeout waiting for
>>> connection from pool
>>>
>>> It looks to me like either DSpace isn't closing the connections as it
>>> should.  Anyone else had this issue?
>>>
>>> Thanks
>>>
>>>
>> --
>> 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...@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] Re: Statistics: Invalid content type

[Jeffrey Sheldon]

Regarding the problem I emailed about two days ago (below), I had hoped to 
reach Pablo Crespo who experienced a similar situation:

https://groups.google.com/forum/#!topic/dspace-tech/zP_w2WyIHYw

No response so far.  Anyone have any thoughts?  I'm going to take a more 
aggressive approach today at debugging this, but any thoughts which can help me 
narrow the scope are appreciated.  


-Jeff


From: dspace-tech@googlegroups.com  on behalf of 
Jeffrey Sheldon 
Sent: Wednesday, May 24, 2017 1:49 PM
To: dspace-tech@googlegroups.com
Subject: [dspace-tech] Statistics: Invalid content type

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 
org.apache.cocoon.components.pipeline.impl.AbstractCachingProcessingPipeline.processXMLPipeline(AbstractCachingProcessing

[dspace-tech] Re: Submit Feature requests to DSpace

[Mark H. Wood]

On Thursday, May 25, 2017 at 2:32:09 PM UTC-4, George Kozak wrote:
>
> Hi,
> My management asked me if we could submit a request for an enhancement to 
> be made to  DSpace.  How do we go about submitting feature requests for 
> consideration for a new release? 
>
>
 Please file an issue at https://jira.duraspace.org/ (using the Create 
button) for project DSpace, selecting "issue type" New Feature (for new 
features) or Improvement (for improvements to existing features).  Bug 
reports are also welcome.  Issues are reviewed regularly.

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