-
Notifications
You must be signed in to change notification settings - Fork 22
Pr1370 review #1390
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: issue_#1181_doi_configuration_per_community
Are you sure you want to change the base?
Pr1370 review #1390
Changes from all commits
e048b7a
4d0e302
c652159
bffc5fa
92c5d4e
4e42b92
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -123,12 +123,21 @@ | |
| that allows you to configure multiple community specific DOI providers. | ||
| Each provider will only mint DOIs for items in the configured communities. | ||
|
|
||
| An item belongs to a community when that community is a direct parent of the item's owning | ||
| collection - the same semantics as the per-community handle prefixes | ||
| (lr.pid.community.configurations). A provider configured with a top-level community does not | ||
| cover its sub-communities; list each sub-community explicitly in the "communities" property. | ||
|
|
||
| Credentials, for DOI connectors need to be configured, per each DOI prefix, in local.cfg, e.g.: | ||
|
|
||
| identifier.doi.10.83111.user = <username> | ||
| identifier.doi.10.83111.password = <password> | ||
| identifier.doi.10.83222.user = <username> | ||
| identifier.doi.10.83222.password = <password> | ||
|
|
||
| The ${...} placeholders on the connector beans below resolve against the DSpace configuration, | ||
| so the credentials stay in local.cfg. Each connector's doiPrefix must match the doiPrefix of the | ||
| provider it is wired into. | ||
| --> | ||
| <!-- Uncomment to enable community specific DOI providers | ||
| <bean id="org.dspace.identifier.DOIIdentifierProvider" class="org.dspace.identifier.ClarinDOIIdentifierProvider"> | ||
|
|
@@ -146,7 +155,11 @@ | |
| abstract="true"> | ||
| <property name="configurationService" ref="org.dspace.services.ConfigurationService" /> | ||
| <property name="DOIConnector"> | ||
| <bean parent = "org.dspace.identifier.doi.DOIConnector" /> | ||
| <bean parent = "org.dspace.identifier.doi.DOIConnector"> | ||
| <property name="username" value="${identifier.doi.10.83111.user}" /> | ||
| <property name="password" value="${identifier.doi.10.83111.password}" /> | ||
| <property name="doiPrefix" value="10.83111" /> | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Can we avoid the same doiPrefix to be declared twice ? I'd leave the doiPrefix to be the property of Provider, and username, password properties of DataCiteConnector, BTW, after this change, it doesn't matter what format of username/password properties will be used for connector. It could be whatever format. What's mentioned here is just a convention. |
||
| </bean> | ||
| </property> | ||
| <property name="doiPrefix" value="10.83111" /> | ||
| <property name="namespaceSeparator" value="clarin.1." /> | ||
|
|
@@ -164,7 +177,11 @@ | |
| abstract="true"> | ||
| <property name="configurationService" ref="org.dspace.services.ConfigurationService" /> | ||
| <property name="DOIConnector"> | ||
| <bean parent = "org.dspace.identifier.doi.DOIConnector" /> | ||
| <bean parent = "org.dspace.identifier.doi.DOIConnector"> | ||
| <property name="username" value="${identifier.doi.10.83222.user}" /> | ||
| <property name="password" value="${identifier.doi.10.83222.password}" /> | ||
| <property name="doiPrefix" value="10.83222" /> | ||
| </bean> | ||
| </property> | ||
| <property name="doiPrefix" value="10.83222" /> | ||
| <property name="namespaceSeparator" value="clarin.2." /> | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The SimpleCache was limited to 5 items, and is replaced by unlimited ConcurrentHashMap.
My concern is that It may occupy lot of memory.