COAR Notify - Revision history

Will.fyson: /* Introduction */

2025-07-31T15:13:43Z

‎Introduction

2025-07-31T13:40:02Z

‎Bazaar Plugin (for EPrints v3)

2025-07-31T13:21:04Z

2025-07-31T13:19:57Z

‎Overview

2025-07-31T13:07:32Z

‎Repository Linking

2025-07-31T12:53:42Z

2025-07-31T12:53:31Z

‎Summary Page Updates

2025-07-31T12:51:17Z

‎Repository Linking

2025-07-31T12:37:56Z

2025-07-31T12:32:03Z

‎LDN Inbox

@@ Line 1: / Line 1: @@
 ==Introduction==
 This page includes details on the COAR Notify implementation for EPrints. For an overview of COAR Notify in EPrints please see [[COAR Notify Overview]].
 For more details on the PCI integration which uses COAR Notify, please see [[COAR Notify: PCI]]

@@ Line 59: / Line 59: @@
 ===Bazaar Plugin (for EPrints v3)===
-Available at: https://github.com/eprintsug/coar_notify/tree/epm
+Available at: https://bazaar.eprints.org/1257/ and https://github.com/eprintsug/coar_notify/tree/epm
 The EPM can be installed either via the Bazaar or by inclusion as a submodule in your repository's lib/epm directory.

@@ Line 5: / Line 5: @@
 For more details on the PCI integration which uses COAR Notify, please see [[COAR Notify: PCI]]
 ==Repository Linking==
@@ Line 58: / Line 49: @@
 ==Download and Install==
-'''Prerequisites: [[Signposting]]; [[COAR Notify]] ingredient/plugin.'''
+'''Prerequisites: [[Signposting]]'''
 ===Ingredient (for EPrints v3.4+)===

← Older revision		Revision as of 13:19, 31 July 2025
Line 19:		Line 19:

	===Overview===		===Overview===
		+	Links between repositories can be specified via a new field in the deposit workflow. Users can specify the URL of a summary page they want to link to and send the request.
		+
		+	[[File:Repository Linking- Deposit Workflow.png\|600px\|thumb\|none]]
		+
		+	The input component displays all requests that have been sent, with a red bar indicating a failed request and a green bar representing a successful request. Once a link between two items has been made, the input component should prevent the same link request from being made again.

	Once links have been established these appear on the summary pages. If the link is established between two EPrints repositories which both have the COAR Notify implementation installed and configured, the links will appear on the summary pages for the remote repository too.		Once links have been established these appear on the summary pages. If the link is established between two EPrints repositories which both have the COAR Notify implementation installed and configured, the links will appear on the summary pages for the remote repository too.

@@ Line 18: / Line 18: @@
 The repository linking functionality is included as part of the main COAR Notify implementation. This allows two records held in different repositories (e.g. a publications repository and a separate research data repository) to establish links between each other.
-===Workflow Updates===
+Once links have been established these appear on the summary pages. If the link is established between two EPrints repositories which both have the COAR Notify implementation installed and configured, the links will appear on the summary pages for the remote repository too.
 To include the new input component in the deposit workflow, first add a new stage if required:
@@ Line 38: / Line 44: @@
    </stage>
 </pre>
-===Summary Page Updates===
+====Summary Page Updates====
 To display incoming and outgoing repository links in summary pages, add the following to the citation file.

@@ Line 43: / Line 43: @@
 <pre>
    <epc:print expr="$item.property('notify_links')" />
-</pr>
+</pre>
 ==Download and Install==

← Older revision		Revision as of 12:51, 31 July 2025
Line 18:		Line 18:
	The repository linking functionality is included as part of the main COAR Notify implementation. This allows two records held in different repositories (e.g. a publications repository and a separate research data repository) to establish links between each other.		The repository linking functionality is included as part of the main COAR Notify implementation. This allows two records held in different repositories (e.g. a publications repository and a separate research data repository) to establish links between each other.

		+
		+	===Workflow Updates===
		+	To include the new input component in the deposit workflow, first add a new stage if required:
		+
		+	<pre>
		+	<flow>
		+	<stage ref="type"/>
		+	<stage ref="files"/>
		+	<stage ref="core"/>
		+	<stage ref="links"/>
		+	</flow>
		+	</pre>
		+
		+	And add the following to define the new stage:
		+
		+	<pre>
		+	<stage name="links">
		+	<component type="Field::NotifyLink"><field ref="notify_links"/></component>
		+	</stage>
		+	</pre>
		+	===Summary Page Updates===

	==Download and Install==		==Download and Install==

@@ Line 15: / Line 15: @@
 ===LDN Dataset===
-==Download==
+==Repository Linking==
-Ingredient: https://github.com/eprintsug/coar_notify
+The repository linking functionality is included as part of the main COAR Notify implementation. This allows two records held in different repositories (e.g. a publications repository and a separate research data repository) to establish links between each other.
 Bazaar Plugin: https://github.com/eprintsug/coar_notify/tree/epm
 ==Version History==

← Older revision		Revision as of 12:32, 31 July 2025
Line 11:		Line 11:

	===LDN Inbox===		===LDN Inbox===
		+	The repository's LDN Inbox is available at <nowiki>https://myrepo.com/coar_notify/inbox</nowiki>

	===LDN Dataset===		===LDN Dataset===