This Confluence wiki site, maintained by DuraSpace prior to the recent merger with LYRASIS, will transition from the duraspace.org domain to the lyrasis.org domain on Saturday, Nov 16 beginning at approximately 7pm ET. A period of downtime of 2-3 hours is expected. After the transition, this wiki will be available at https://wiki.lyrasis.org/. All links to duraspace.org wiki pages will be redirected to the correct lyrasis.org URL. If you have questions prior to or following the transition please contact: wikihelp@lyrasis.org.
Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The feature allows a researcher or more in general an authorized user or the administrator to add objects to a relation starting from the detail page of the target CRIS object. The "object" could be both a dspace items (publication, dataset, patent, etc.) than a CRIS Object (events, awards, projects, etc.). It is also possible to make available, for some or all the relations, the opposite action "remove". Below some  examples:

  • Add publications to a project
  • Add publications to a journal
  • Add projects to a researcher
  • Add events to a project

...

Which relations should offer this feature are configured  in the spring file cris-relationpreference.xml where one can also decide who (administrator, owner of the target or a policy managed groups) will have access to the feature and which discovery configuration apply to the search form.

The cris-relationpreference.xml file contains a bean RelationServiceConfiguration containing the list of all the relations that support such feature

Code Block
languagexml
<bean
		class="org.dspace.app.cris.configuration.RelationServiceConfiguration">
		<property name="list">
			<list>
				<bean
					class="org.dspace.app.cris.configuration.RelationService">
					<property name="relationConfiguration" ref="relationPJVSItemConfiguration"/>
					<property name="discoveryConfigurationKey" value="publications"/>
					<property name="addAction">
						<bean class="org.dspace.app.cris.configuration.AddRelationMetadataAction">
							<property name="metadataAction" value="dc.relation" />
						</bean>
					</property>
					<property name="removeAction">
						<bean class="org.dspace.app.cris.configuration.RemoveRelationMetadataAction">
							<property name="metadataAction" value="dc.relation" />
						</bean>
					</property>
					<property name="security">
						<list>
							<ref bean="ownerSecurityConfiguration" />
							<ref bean="adminSecurityConfiguration" />
						</list>
					</property>
				</bean>
...

if the specified removeAction is specified a "remove" button will be presented aside objects already included in the relation otherwise the message Already included in the relation shown in the screenshot is displayed