Title: Message Title
|
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Unassigned
|
|
Components:
|
DSpace API
|
|
Created:
|
25/Nov/13 3:47 PM
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
Pascal-Nicolas Becker
|
|
I need to write another DOIConnector to support some security constraints of our computing center. While doing so I noticed that the DOIIdentifierProvider does things only the DOIConnector should do. This change helps to keep the separation between both parts clean.
In detail: when the DOIIdentifierProvider has to register a DOI at the registration agency, it checks whether the DOI is reserved and perform a reservation if it is not. The behavior is founded in a rule of DataCite that wants us to reserve a DOI before it is registered. As other registration agency may have other rules this should be checked by the DataCiteConnector and not by the DOIIdentifierProvider. The DataCiteConnector encapsulates all DataCite specific part while the DOIIdentifierProvider should handle everything on the side of DSpace.
The second Bugfix is just a typo. A static final field in the DOIIdentifierException should be renamed.
Both bugfixes should goes into DSpace 4.0 so that they get public before anyone else begins to implement another DOIConnector.
|
|
|
|
|
|
|
|
------------------------------------------------------------------------------
Shape the Mobile Experience: Free Subscription
Software experts and developers: Be at the forefront of tech innovation.
Intel(R) Software Adrenaline delivers strategic insight and game-changing
conversations that shape the rapidly evolving mobile landscape. Sign up now.
http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
