[dspace-tech] Reminder - DSpace Dev Show and Tell - Oct 30, 2018 - DSpace Docker Updates

[Terry Brady]

The Oct 30 DSpace Developer Show and Tell will be an update on DSpace
Docker Initiatives.

See the agenda below for a list of new developments with the DSpace docker
images.  If you are using Docker for DSpace development, I would love to
add your story to the agenda.

   -
   
https://wiki.duraspace.org/display/DSPACE/Dev+Show+and+Tell+-+Oct+30%2C+2018+-+1500UTC+-+DSpace+Docker+Updates


-- 
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] Run handle server in a separate machine (DSpace 4.7)?

[Vinicius Assef]

Hi there.

Our DSpace 4.7 server runs inside a private cloud, thus handle.net
cannot ping the server.

Is there a way to run only DSpace's handle server in a different
machine from that one running the rest of DSpace itself?

--
Thanks in advance.
Vinicius Assef

-- 
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] log4j:ERROR Unable to delete log file

[admin]

Hi,

I cannot figure out how to fix the following issue. I get the error:
log4j:ERROR Unable to delete log file
in email report related to cron entry:
Cron  $DSPACE/bin/dspace index-discovery > /dev/null


Peter

-- 
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: DOI via Proxy

[Paul Münch]

Hello Claudia,

thank you very much for your detailed description. I didn't realise that
only new items will be listed.

Kind regards,

Paul Münch

Am 22.10.18 um 13:35 schrieb Claudia Jürgen:
> Hello Paul,
>
> once you have configured and your DOI ( these notes are for4.x, 5.x) in
> [dspace]/dspace/config/dspace.cfg
>
>   * identifier.doi.prefix
>   * identifier.doi.namespaceseparator
>   * event.consumer.doi.class
>   * event.consumer.doi.filters
>   * event.dispatcher.default.consumers
>
> [dspace]/config/spring/api/identifier-service.xml
>
>   * bean org.dspace.identifier.DOIIdentifierProvider
>   * bean org.dspace.identifier.doi.DOIConnector
>
> and adjusted the crosswalk
> [dspace]/config/crosswalks/DIM2DataCite.xsl
> You can test the crosswalk with
> [dspace]/bin/dspace dsrun 
> org.dspace.content.crosswalk.XSLTDisseminationCrosswalk DataCite  
> [output-file]
>
> newly added items will get an entry in the doi table.
> You can check what is in your doi table with
> SELECT * from doi;
>
> If you have already existing items you got to retrospectively create
> the entries in the table.
> We did this by manipulating the database (usual warning about backup):
> INSERT into doi (doi_id, doi, resource_type_id, resource_id, status) 
> SELECT nextval('doi_seq'), 
> concat('YOURPREFIX/YOURNAMESPACESEPARATOR-',currval('doi_seq')), 2, item_id, 7
> FROM item WHERE in_archive=true and item_id not in (select resource_id from 
> doi where resource_type_id=2);
>
> and then running the doi-organiser.
>
> Hope this helps
>
> Claudia Jürgen
>
>
>
> Am 22.10.2018 um 12:55 schrieb Paul Münch:
>> Hello,
>>
>> I figured out that the Proxy configuration is not the problem. Somehow
>> it is not possible to do anything with the 'doi-organiser'. Everytime I
>> tried to reserve, register or update all for test purposes, I got these
>> error message: There are no objects in database that could be ...
>> I configured our DSpace-Instance how descriebed in the documentation.
>> The database connection is fine. Can anybody help me?
>>
>> Thanks in advance and kind regards,
>>
>> Paul Münch
>>
>> Am 19.10.18 um 14:20 schrieb Paul Münch:
>>> Hello,
>>>
>>> we have a problem with the 'doi-organiser'-tool via our proxy server.
>>> All proxy configuration works fine, e.g. OAI, REST or command line
>>> programms like 'wget'. But if we use the 'doi-organiser', we get a
>>> 'Connection timed out'. All DSpace-DOI configuration are successfully
>>> tested on VMs without proxy. So there is no problem.
>>> In our Java environment the proxy parameters are all set and are in use
>>> during the 'doi-organiser' ( I check it with 'jps -lvm' ). Additionally
>>> I added 'System.setProperty(...)' to 'DataCiteConnector.java' - without
>>> success.
>>> I have no idea how to solve this issue and hope someone of you could help.
>>>
>>> Thanks in advance and kind regards,
>>>
>>> Paul Münch
>>>
>
> -- 
> 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. / --
> 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.

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

Re: [dspace-tech] Re: DOI via Proxy

[Claudia Jürgen]

Hello Paul,

once you have configured and your DOI ( these notes are for4.x, 5.x) in
[dspace]/dspace/config/dspace.cfg

 *   identifier.doi.prefix
 *   identifier.doi.namespaceseparator
 *   event.consumer.doi.class
 *   event.consumer.doi.filters
 *   event.dispatcher.default.consumers

[dspace]/config/spring/api/identifier-service.xml

 *   bean org.dspace.identifier.DOIIdentifierProvider
 *   bean org.dspace.identifier.doi.DOIConnector

and adjusted the crosswalk
[dspace]/config/crosswalks/DIM2DataCite.xsl
You can test the crosswalk with

[dspace]/bin/dspace dsrun org.dspace.content.crosswalk.XSLTDisseminationCrosswalk 
DataCite  [output-file]

newly added items will get an entry in the doi table.
You can check what is in your doi table with
SELECT * from doi;

If you have already existing items you got to retrospectively create the 
entries in the table.
We did this by manipulating the database (usual warning about backup):

INSERT into doi (doi_id, doi, resource_type_id, resource_id, status)
SELECT nextval('doi_seq'), 
concat('YOURPREFIX/YOURNAMESPACESEPARATOR-',currval('doi_seq')), 2, item_id, 7
FROM item WHERE in_archive=true and item_id not in (select resource_id from doi 
where resource_type_id=2);

and then running the doi-organiser.

Hope this helps

Claudia Jürgen




Am 22.10.2018 um 12:55 schrieb Paul Münch:

Hello,

I figured out that the Proxy configuration is not the problem. Somehow
it is not possible to do anything with the 'doi-organiser'. Everytime I
tried to reserve, register or update all for test purposes, I got these
error message: There are no objects in database that could be ...
I configured our DSpace-Instance how descriebed in the documentation.
The database connection is fine. Can anybody help me?

Thanks in advance and kind regards,

Paul Münch

Am 19.10.18 um 14:20 schrieb Paul Münch:


Hello,

we have a problem with the 'doi-organiser'-tool via our proxy server.
All proxy configuration works fine, e.g. OAI, REST or command line
programms like 'wget'. But if we use the 'doi-organiser', we get a
'Connection timed out'. All DSpace-DOI configuration are successfully
tested on VMs without proxy. So there is no problem.
In our Java environment the proxy parameters are all set and are in use
during the 'doi-organiser' ( I check it with 'jps -lvm' ). Additionally
I added 'System.setProperty(...)' to 'DataCiteConnector.java' - without
success.
I have no idea how to solve this issue and hope someone of you could help.

Thanks in advance and kind regards,

Paul Münch







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

--
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: DOI via Proxy

[Paul Münch]

Hello Michael,

unfortunately not. Is there something additional I had to do beside the
configuration?

Kind regards,

Paul Münch

Am 22.10.18 um 13:10 schrieb Michael Plate:
> Hi Paul,
>
> Am 22.10.18 um 12:55 schrieb Paul Münch:
>> Hello,
>>
>> I figured out that the Proxy configuration is not the problem. Somehow
>> it is not possible to do anything with the 'doi-organiser'. Everytime I
>> tried to reserve, register or update all for test purposes, I got these
>> error message: There are no objects in database that could be ...
>> I configured our DSpace-Instance how descriebed in the documentation.
>> The database connection is fine. Can anybody help me?
> […]
>
> do you have entries in the "doi" table ?
>
> CU
>
> Michael
>
>

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


signature.asc
Description: OpenPGP digital signature

Re: [dspace-tech] Re: Is it possible to submit a license.txt into bundle "License"?

[Stefan Kombrink]

Thanks Tim,

 I've checked it using curl and this actually does the job!

greets Stefan

On 10/19/18 3:48 PM, Tim Donohue wrote:
> One last note, I meant to mention, I also found a "clue" to this in the
> documentation of the AIP METS format (which is the same METS format that
> is also used by SWORD):
> 
> https://wiki.duraspace.org/display/DSDOC6x/DSpace+AIP+Format#DSpaceAIPFormat-AIPDetails:METSStructure
> 
> In that detailed documentation, there's a section on "mets/fileSec"
> element which says:
> 
> "For ITEM objects:
> 
>   * Each distinct Bundle in an Item goes into a |fileGrp|.
> The |fileGrp| has a |@USE| attribute which corresponds to the Bundle
> name."
> 
> 
> - Tim
> 
> On Fri, Oct 19, 2018 at 8:43 AM Tim Donohue  > wrote:
> 
> Hi Stefan,
> 
> I believe the Bundle name for bitstreams ingested via SWORD (or
> other packaging tools) can be specified in the "USE" attribute of a
> METS .  You can see this in the Example METS file for SWORD at:
> 
> https://github.com/DSpace/DSpace/blob/master/dspace-sword/example/mets.xml#L133
> 
> Notice, in this case USE="CONTENT". which means these bitstreams
> will be added to the CONTENT bundle.  If you change it to a
> different value, it should instead add those bitstreams to a
> different Bundle.
> 
> This is achieved because SWORD (both versions) actually just uses
> our DSpaceMETSIngester (which is also used by commandline tools that
> ingest METS).  In the DSpaceMETSIngester, after a bitstream is found
> in the METS file, this "finishBitstream" method is called:
> 
> https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace-api/src/main/java/org/dspace/content/packager/DSpaceMETSIngester.java#L238
> 
> You'll notice in that method, it checks the "getBundleName()"
> provided by the METS file itself.  That method looks at the "USE"
> attribute:
> 
> https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace-api/src/main/java/org/dspace/content/packager/METSManifest.java#L491
> 
> Hopefully that helps,
> 
> - Tim
> 
> On Fri, Oct 19, 2018 at 7:10 AM Stefan Kombrink
> mailto:stefan.kombr...@uni-ulm.de>> wrote:
> 
> Hi euler,
> 
>  thanks for your reply. I can't use xmlui though, I need to make
> it work
> via sword (or any other automated way) somehow.
> 
> greets Stefan
> 
> On 10/19/18 11:59 AM, euler wrote:
> > Hi,
> >
> > If you are using XMLUI, there is a setting there in dspace.cfg:
> >
> > # Determine which bundles administrators and collection
> administrators
> > may upload
> > # into an existing item through the administrative interface.
> If the
> > user does not
> > # have the appropriate privileges (add & write) on the bundle
> then that
> > bundle will
> > # not be shown to the user as an option.
> > #xmlui.bundle.upload = ORIGINAL, METADATA, THUMBNAIL, LICENSE,
> CC-LICENSE
> >
> > The bundles above (in uppercase letters) are the default
> bundles which
> > you can upload as bitstream. You just have to select the
> appropriate
> > bundle when submitting, ie select Licenses instead of Content
> Files
> > (default) when uploading the file. See attached screenshot.
> >
> > Hope this helps.
> >
> > upload-license.PNG
> >
> -- 
> Stefan Kombrink
> Universität Ulm
> Kommunikations- und Informationszentrum (kiz)
> Abteilung Informationsmedien
> +49-731-50-31482 
> 
> -- 
> 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
> 
> -- 
> Tim Donohue
> Technical Lead for DSpace & DSpaceDirect
> DuraSpace.org | DSpace.org | DSpaceDirect.org

-- 
Stefan Kombrink
Universität Ulm
Kommunikations- und Informationszentrum (kiz)
Abteilung Informationsmedien
+49-731-50-31482

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: 

[dspace-tech] Re: DOI via Proxy

[Michael Plate]

Hi Paul,

Am 22.10.18 um 12:55 schrieb Paul Münch:
> Hello,
> 
> I figured out that the Proxy configuration is not the problem. Somehow
> it is not possible to do anything with the 'doi-organiser'. Everytime I
> tried to reserve, register or update all for test purposes, I got these
> error message: There are no objects in database that could be ...
> I configured our DSpace-Instance how descriebed in the documentation.
> The database connection is fine. Can anybody help me?
[…]

do you have entries in the "doi" table ?

CU

Michael


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


smime.p7s
Description: S/MIME Cryptographic Signature

Re: [dspace-tech] Reset password user for dspace in command line

[Claudia Jürgen]

Hello,

you can not set a new password via command line, see:
https://wiki.duraspace.org/display/DSDOC6x/Managing+User+Accounts

But the user can simple use the password forgotten function link on the
login screen
[YourURL]/forgot

Hope this helps

Claudia Jürgen


Am 21.10.2018 um 19:10 schrieb hoska...@gmail.com:

Hello every one
We have dspace 6.2 installed in debian 9 with postgres 9.6 .
some users created in dspace lose theirs passwords login. Is it possible to 
define an other password for these users witn dspace command ligne. Or how we 
can change the password in database. The pasword in database is crypted with 
sha512.
thanks for help



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

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