[Dspace-tech] R: DOI DATACITE
Hi Pascal, We have a contract with DataCite, and they have given to us username and password. I have followed the instructions in the documentation and inserted my credentials in dspace.cfg then I have done some change in the DIM2DataCite.xsl( My university name ) and finally I have removed the comment signs in the file identifier-service.xml. After that I have inserted an new submission, I have seen that there was in the Doi table of the dspace database a new row for that item. But when I use the command line to reserve or register the DOI the system answer that there 0 object for reservation/registration. If I try to execute the command dspace doi-organiser -l, the system say : command not found. The only way to insert the item in Datacite for now is to insert it manually, from the datacite site. Thanks for your help Best regards Massimiliano Da: Becker, Pascal-Nicolas [mailto:p.bec...@tu-berlin.de] Inviato: venerdì 17 gennaio 2014 16:56 A: dspace-tech@lists.sourceforge.net Cc: Massimiliano Cilurzo Oggetto: RE: [Dspace-tech] DOI DATACITE Hi Massimiliano, did you entered into a contract with a DOI registration agency? Did they provide you a username, a password and a (test-)prefix? Are you sure, they want you to use the DataCite API directly? If you followed the instructions in the documentation, DSpace should mint DOIs whenever new items gets published into the repository. With publish I mean that the item is part of your repository, can be found using the normal search, and is not waiting for the user to finish the submission or for an administrator to accept it. The DOI is stored as metadata value of the item in the field dc.identifier.uri. So If you take a look on the published item you should find it there. As the documentation describes DSpace uses an asynchronous mechanism to register DOIs. Using the command line interface (https://wiki.duraspace.org/display/DSDOC4x/DOI+Digital+Object+Identifier#DO IDigitalObjectIdentifier-CommandLineInterface) you can list all DOIs waiting for reservation and/or registration. So, do you already have published an item after you configured DSpace to use DOIs? What happens if you executes [dspace-install]/bin/dspace doi-organiser -l? Regards, Pascal From: Massimiliano Cilurzo [mailto:mcilu...@unisa.it] Sent: Friday, January 17, 2014 12:25 PM To: dspace-tech@lists.sourceforge.net Subject: [Dspace-tech] DOI DATACITE Hi All, We have installed in a test server DSPACE 4.0, we have configured it for the use of DOI from DATACITE. We followed the guide line at https://wiki.duraspace.org/display/DSDOC4x/DOI+Digital+Object+Identifier But now I wonder how we can test if. Could someone give an help? Thanks Best regards Massimiliano Cilurzo -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
[Dspace-tech] R: DOI DATACITE
Hi Pascal, I have executed dspace doi-organiser in the wrong directory. When I execute bin/dspace doi-organiser -l? The system answer is: There are no DOIs queued for reservation. There are no DOIs queued for registration. DOIs queued for update: doi:10.,10.5072/unisa-1 (belongs to item with handle 123456789/479) doi:10.x,10.5072/un-2 (belongs to item with handle 123456789/480) doi:10.x,10.5072/unisa-3 (belongs to item with handle 123456789/481) doi:10.,10.5072/unisa-4 (belongs to item with handle 123456789/482) doi: 10.5072/unisa-5 (belongs to item with handle 123456789/485) doi: 10.5072/unisa-6 (belongs to item with handle 123456789/486) There are no DOIs queued for deletion. When I go in the Datacite site, I cant see any of this item. Thanks Kind regards Massimiliano Da: Becker, Pascal-Nicolas [mailto:p.bec...@tu-berlin.de] Inviato: venerdì 17 gennaio 2014 16:56 A: dspace-tech@lists.sourceforge.net Cc: Massimiliano Cilurzo Oggetto: RE: [Dspace-tech] DOI DATACITE Hi Massimiliano, did you entered into a contract with a DOI registration agency? Did they provide you a username, a password and a (test-)prefix? Are you sure, they want you to use the DataCite API directly? If you followed the instructions in the documentation, DSpace should mint DOIs whenever new items gets published into the repository. With publish I mean that the item is part of your repository, can be found using the normal search, and is not waiting for the user to finish the submission or for an administrator to accept it. The DOI is stored as metadata value of the item in the field dc.identifier.uri. So If you take a look on the published item you should find it there. As the documentation describes DSpace uses an asynchronous mechanism to register DOIs. Using the command line interface (https://wiki.duraspace.org/display/DSDOC4x/DOI+Digital+Object+Identifier#DO IDigitalObjectIdentifier-CommandLineInterface) you can list all DOIs waiting for reservation and/or registration. So, do you already have published an item after you configured DSpace to use DOIs? What happens if you executes [dspace-install]/bin/dspace doi-organiser -l? Regards, Pascal From: Massimiliano Cilurzo [mailto:mcilu...@unisa.it] Sent: Friday, January 17, 2014 12:25 PM To: dspace-tech@lists.sourceforge.net Subject: [Dspace-tech] DOI DATACITE Hi All, We have installed in a test server DSPACE 4.0, we have configured it for the use of DOI from DATACITE. We followed the guide line at https://wiki.duraspace.org/display/DSDOC4x/DOI+Digital+Object+Identifier But now I wonder how we can test if. Could someone give an help? Thanks Best regards Massimiliano Cilurzo -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
[Dspace-tech] R: DOI DATACITE
Hi Pascal, Thanks for your help now Im understanding how it works. When I execute [dspace]/bin/dspace doi-organiser u the answer is this: Unable to send email alert. It wasn't possible to update this identifier: doi:10.142xx,10.5072/unisa-1 Unable to send email alert. It wasn't possible to update this identifier: doi:10.142xx,10.5072/unisa-2 Unable to send email alert. It wasn't possible to update this identifier: doi:10.142xx,10.5072/unisa-3 Unable to send email alert. It wasn't possible to update this identifier: doi:10.142xx,10.5072/unisa-4 Unable to send email alert. It wasn't possible to update this identifier: doi:10.142xx/unisa-5 Unable to send email alert. It wasn't possible to update this identifier: doi:10.142xx/unisa-6 Da: Becker, Pascal-Nicolas [mailto:p.bec...@tu-berlin.de] Inviato: giovedì 23 gennaio 2014 13:00 A: dspace-tech@lists.sourceforge.net Cc: Massimiliano Cilurzo Oggetto: RE: [Dspace-tech] DOI DATACITE Hi Massimiliano, as written in the DSpace Documentation DSpace uses an asynchronous approach to register DOIs. Whenever DSpace wants to reserver/register a DOI, it just writes in the DOI table what should be done. The doi-organiser does the real work (by sending one or multiple requests to datacite, containing the metadata and the information if a doi should be reserved, registered, ). So to send your registration request to DataCite, you have to run the doi-organiser as described here: https://wiki.duraspace.org/display/DSDOC4x/DOI+Digital+Object+Identifier#DOI DigitalObjectIdentifier-%27cron%27jobforasynchronousreservation/registration To test it, you can start these commands manually on the command line. For regular use I would suggest a cronjob. Its up to you to decide how often the doi-organiser should be triggered by the cronjob. The decision you have to make is how much time is acceptable for you between the moment DSpace adds a DOI to the metadata of an item and the moment the DOI is functional (registered). I would make this decision depending on the number of submissions you have per day. On smaller repositories it should be acceptable to run the doi-organsier perhaps twice a doi. But if you want to, you can run it more often, f.e. every 15 minutes The reason we did it this way, is to ensure that DSpace is still working even if DataCite should have some down time Did this helps you? What happens if you run [dspace]/bin/dspace doi-organiser u? Regards, Pascal From: Massimiliano Cilurzo [mailto:mcilu...@unisa.it] Sent: Thursday, January 23, 2014 8:46 AM To: dspace-tech@lists.sourceforge.net; Becker, Pascal-Nicolas Subject: R: [Dspace-tech] DOI DATACITE Hi Pascal, I have executed dspace doi-organiser in the wrong directory. When I execute bin/dspace doi-organiser -l? The system answer is: There are no DOIs queued for reservation. There are no DOIs queued for registration. DOIs queued for update: doi:10.,10.5072/unisa-1 (belongs to item with handle 123456789/479) doi:10.x,10.5072/un-2 (belongs to item with handle 123456789/480) doi:10.x,10.5072/unisa-3 (belongs to item with handle 123456789/481) doi:10.,10.5072/unisa-4 (belongs to item with handle 123456789/482) doi: 10.5072/unisa-5 (belongs to item with handle 123456789/485) doi: 10.5072/unisa-6 (belongs to item with handle 123456789/486) There are no DOIs queued for deletion. When I go in the Datacite site, I cant see any of this item. Thanks Kind regards Massimiliano Da: Becker, Pascal-Nicolas [mailto:p.bec...@tu-berlin.de] Inviato: venerdì 17 gennaio 2014 16:56 A: dspace-tech@lists.sourceforge.net Cc: Massimiliano Cilurzo Oggetto: RE: [Dspace-tech] DOI DATACITE Hi Massimiliano, did you entered into a contract with a DOI registration agency? Did they provide you a username, a password and a (test-)prefix? Are you sure, they want you to use the DataCite API directly? If you followed the instructions in the documentation, DSpace should mint DOIs whenever new items gets published into the repository. With publish I mean that the item is part of your repository, can be found using the normal search, and is not waiting for the user to finish the submission or for an administrator to accept it. The DOI is stored as metadata value of the item in the field dc.identifier.uri. So If you take a look on the published item you should find it there. As the documentation describes DSpace uses an asynchronous mechanism to register DOIs. Using the command line interface (https://wiki.duraspace.org/display/DSDOC4x/DOI+Digital+Object+Identifier#DO IDigitalObjectIdentifier-CommandLineInterface) you can list all DOIs waiting for reservation and/or registration. So, do you already have published an item after you configured DSpace to use DOIs? What happens if you executes [dspace-install]/bin/dspace doi-organiser -l? Regards, Pascal From: Massimiliano Cilurzo [mailto:m
[Dspace-tech] R: DOI DATACITE
Hi Pascal,
in this is the dspace.log after the command dspace/bin/dspace doi-organiser
u
.
org.dspace.content.MetadataSchema @ Loading schema cache for fast finds
2014-01-24 09:53:40,896 WARN org.dspace.identifier.doi.DataCiteConnector @
While reserving the DOI doi:10.,10.5072/unisa-1, we got a http status
code 404 and the message "
var
djConfig="en_US"; dojo.require("dojo.parser");Welcome to
DataCite Metadata Store
Metadata Store
You are not logged in | Logindojo.require('dijit.TitlePane');Spring.addDecoration(new
Spring.ElementDecoration({elementId : '_title_title_id', widgetType :
'dijit.TitlePane', widgetAttrs : {title: 'Requested Resource Not Found',
open: true}})); Requested Resource Not FoundSorry, we
did not find the resource you were looking for.Home | Language: | Login".
2014-01-24 09:53:40,920 WARN org.dspace.identifier.doi.DOIOrganiser @
Unable to send email alert
javax.mail.internet.AddressException: Illegal address in string ``''
at
javax.mail.internet.InternetAddress.(InternetAddress.java:94)
at org.dspace.core.Email.send(Email.java:261)
at
org.dspace.identifier.doi.DOIOrganiser.sendAlertMail(DOIOrganiser.java:914)
at
org.dspace.identifier.doi.DOIOrganiser.update(DOIOrganiser.java:689)
at
org.dspace.identifier.doi.DOIOrganiser.runCLI(DOIOrganiser.java:265)
at org.dspace.identifier.doi.DOIOrganiser.main(DOIOrganiser.java:82)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:225
)
at
org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:77)
2014-01-24 09:53:40,921 ERROR org.dspace.identifier.doi.DOIOrganiser @ It
wasn't possible to update this identifier: doi:10.,10.5072/unisa-1
Exceptions code: BAD_ANSWER
org.dspace.identifier.doi.DOIIdentifierException: Unable to parse an answer
from DataCite API. Please have a look into DSpace logs.
at
org.dspace.identifier.doi.DataCiteConnector.reserveDOI(DataCiteConnector.jav
a:564)
at
org.dspace.identifier.doi.DataCiteConnector.updateMetadata(DataCiteConnector
.java:681)
at
org.dspace.identifier.DOIIdentifierProvider.updateMetadataOnline(DOIIdentifi
erProvider.java:412)
at
org.dspace.identifier.doi.DOIOrganiser.update(DOIOrganiser.java:669)
at
org.dspace.identifier.doi.DOIOrganiser.runCLI(DOIOrganiser.java:265)
at org.dspace.identifier.doi.DOIOrganiser.main(DOIOrganiser.java:82)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:225
)
at
org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:77)
2014-01-24 09:53:42,294 WARN org.dspace.identifier.doi.DataCiteConnector @
While reserving the DOI doi:10.14273,10.5072/unisa-2, we got a http status
code 404 and the message "
Thanks
Best regards,
Massimiliano
Da: Becker, Pascal-Nicolas [mailto:p.bec...@tu-berlin.de]
Inviato: giovedì 23 gennaio 2014 18:10
A: Massimiliano Cilurzo; dspace-tech@lists.sourceforge.net
Oggetto: RE: [Dspace-tech] DOI DATACITE
Hi Massimiliano,
youre on the right way, but there is still some error. What does the
doi-organiser writes into [dpsace]/logs/dspace.logs?
Regards,
Pascal
From: Massimiliano Cilurzo [mailto:mcilu...@unisa.it]
Sent: Thursday, January 23, 2014 1:09 PM
To: Becker, Pascal-Nicolas; dspace-tech@lists.sourceforge.net
Subject: R: [Dspace-tech] DOI DATACITE
Hi Pascal,
Thanks for your help now Im understanding how it works.
When I execute [dspace]/bin/dspace doi-organiser u the answer is this:
Unable to send email alert.
It wasn't possible to update this identifier: doi:10.142xx,10.5072/unisa-1
Unable to send email alert.
It wasn't possible to update this identifier: doi:10.142xx,10.5072/unisa-2
Unable to send email alert.
It wasn't possible to update this identifier: doi:10.142xx,10.5072/unisa-3
Unable to send email alert.
It wasn't possible to update this identifier: doi:10.142xx,10.5072/unisa-4
Unable to send email alert.
It wasn't possible to update this identifier: doi:10.142xx/unisa-5
Unable to send email alert.
It wasn't possible to update this identifier: doi:10.142xx/unisa-6
Da: Becker, Pascal-Nicolas [mailto:p.bec...@tu-berlin.de]
Inviato: giovedì 23 gennaio 2014 13:00
A: dspace-tech@lists.sourceforge.net
Cc: Mass
[Dspace-tech] R: DOI DATACITE
th the DataCite crosswork does not have anything to do with the URL of the DataCite server, it's the same crosswalk for testing and production server. I would advise to use the command line argument -q when the doi-organiser gets started by a cronjob only. If you use the doi-organiser manually you get more information if you don't use -q. Regards, Pascal > -Original Message- > From: Massimiliano Cilurzo [mailto:mcilu...@unisa.it] > Sent: Monday, February 10, 2014 3:34 PM > To: heli...@centrum.sk > Cc: Becker, Pascal-Nicolas; 'dspace-tech' > Subject: R: [Dspace-tech] R: DOI DATACITE > > Dear Ivan, > >The DIM2DataCite.xsl is present in the dspace/config/crosswalks directory. > I have just noticed that if I put in the identifier-service.xml, > 'DATACITE_HOST' > value ='test.datacite.org', I haven't this problem. > " >class="org.dspace.identifier.doi.DataCiteConnector" > scope="singleton"> > > > > this > message: > Update DOI doi:10.14273/unisa-2 for ITEM with ID 1.210 failed: > AUTHENTICATION_ERROR > > Thanks > Best regards > Massimiliano > > -Messaggio originale- > Da: ivan.ma...@gmail.com [mailto:ivan.ma...@gmail.com] Per conto di > helix84 > Inviato: lunedì 10 febbraio 2014 15:23 > A: Massimiliano Cilurzo > Cc: Becker, Pascal-Nicolas; dspace-tech > Oggetto: Re: [Dspace-tech] R: DOI DATACITE > > Before Pascal gives you an authoritative reply, I'd check whether you > have the [dspace]/config/crosswalks/DIM2DataCite.xsl file present. > Perhaps you reused your old configuration directory from DSpace 3.x > that didn't have this file? > > > Regards, > ~~helix84 > > Compulsory reading: DSpace Mailing List Etiquette > https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- Android apps run on BlackBerry 10 Introducing the new BlackBerry 10.2.1 Runtime for Android apps. Now with support for Jelly Bean, Bluetooth, Mapview and more. Get your Android app in front of a whole new audience. Start now. http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
[Dspace-tech] R: DOI DATACITE
ged in | href="/login;jsessionid=6F8AA3B9DFDF8CA4082A98A39D1312AA">Login
> version="2.0"> type="text/javascript">dojo.require('dijit.TitlePane'); id="_title_title_id"> type="text/javascript">Spring.addDecoration(new
> Spring.ElementDecoration({elementId : '_title_title_id', widgetType :
> 'dijit.TitlePane', widgetAttrs : {title: 'Requested Resource Not Found', open:
> true}})); Requested Resource Not FoundSorry, we
> did not find the resource you were looking for. version="2.0" id="footer"> href="/;jsessionid=6F8AA3B9DFDF8CA4082A98A39D1312AA">Home pan> | Language: href="?lang=en"> src="/resources/images/flags/en.png;jsessionid=6F8AA3B9DFDF8CA4082A98
> A39D1312AA" class="flag"/> href="?lang=de"> src="/resources/images/flags/de.png;jsessionid=6F8AA3B9DFDF8CA4082A98
> A39D1312AA" class="flag"/> href="?lang=fr"> src="/resources/images/flags/fr.png;jsessionid=6F8AA3B9DFDF8CA4082A98
> A39D1312AA" class="flag"/> | href="/login;jsessionid=6F8AA3B9DFDF8CA4082A98A39D1312AA">Login
> ".
> 2014-02-11 10:44:46,381 ERROR org.dspace.identifier.doi.DOIOrganiser @
> It wasn't possible to update this identifier: doi:10.14273/unisa-4
> Exceptions
> code: BAD_ANSWER
> org.dspace.identifier.doi.DOIIdentifierException: Unable to parse an
> answer from DataCite API. Please have a look into DSpace logs.
> at
> org.dspace.identifier.doi.DataCiteConnector.reserveDOI(DataCiteConnector.
> java:564)
> at
> org.dspace.identifier.doi.DataCiteConnector.updateMetadata(DataCiteCon
> n
> ector.java:681)
> at
> org.dspace.identifier.DOIIdentifierProvider.updateMetadataOnline(DOIId
> en
> tifierProvider.java:412)
> at
> org.dspace.identifier.doi.DOIOrganiser.update(DOIOrganiser.java:669)
> at
> org.dspace.identifier.doi.DOIOrganiser.runCLI(DOIOrganiser.java:265)
> at org.dspace.identifier.doi.DOIOrganiser.main(DOIOrganiser.java:82)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.j
> ava:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.ja
> va:225)
> at
> org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:77)
>
>
> Thanks
> Best regards
> Massimiliano
>
>
>
> -Messaggio originale-
> Da: Becker, Pascal-Nicolas [mailto:p.bec...@tu-berlin.de]
> Inviato: lunedì 10 febbraio 2014 17:10
> A: Massimiliano Cilurzo
> Cc: 'dspace-tech'; heli...@centrum.sk
> Oggetto: RE: [Dspace-tech] DOI DATACITE
>
> Sorry, I lost track. What's the current problem right now? Did you
> "repair" the old DOIs in your database?
>
> The URL test.datacite.org addresses the test server of DataCite, the
> URL mds.datacite.org addresses the production server. You can get a
> login to the test server from your DOI/DataCite registration agency.
> We got two different prefixes for the test and for the production
> server, so you should check for which server you have valid
> credentials (prefix, username, password). You can test your credential
> by calling https://test.datacite.org/mds/ or https://mds.datacite.org in your
> browser and try to login.
> "AUTHENTICATION_ERROR" means that your credentials are invalid or does
> not match the doi prefix you configured. There should be a more
> detailed message in the dspace.log, can you please have a look?
>
> Relating the crosswalk problem it is absolutely correct, what helix
> wrote. Is the file named in your dspace.cfg? You can see how it is done here:
> https://github.com/DSpace/DSpace/blob/dspace-
> 4.0/dspace/config/dspace.cfg#L508-L515. The problem with the DataCite
> crosswork does not have anything to do with the URL of the DataCite
> server, it's the same crosswalk for testing and production server.
>
> I would advise to use the command line argument -q when the
> doi-organiser gets started by a cronjob only. If you use the
> doi-organiser manually you get more information if you don't use -q.
>
> Regards,
> Pascal
>
> > -Original Message-
> > From: Massimiliano Cilurzo [mailto:mcilu...@unisa.it]
> > Sent: Monday, February 10, 2014 3:34 PM
> > To: heli...@centrum.sk
> > Cc: Becker, Pascal-Nicolas;
Re: [Dspace-tech] R: DOI DATACITE
Before Pascal gives you an authoritative reply, I'd check whether you have the [dspace]/config/crosswalks/DIM2DataCite.xsl file present. Perhaps you reused your old configuration directory from DSpace 3.x that didn't have this file? Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
