EPrints Glossary - Revision history

Drn@ecs.soton.ac.uk: /* Trigger */ Added link to page about triggers

2024-07-09T15:42:23Z

‎Trigger: Added link to page about triggers

Drn@ecs.soton.ac.uk: /* T */

2024-07-09T14:40:30Z

‎T

Drn@ecs.soton.ac.uk: /* Core field */

2023-04-21T07:42:48Z

‎Core field

Drn@ecs.soton.ac.uk: /* C */ Added Core field

2023-04-21T07:42:03Z

‎C: Added Core field

Drn@ecs.soton.ac.uk: /* S */ Added system field

2023-04-20T11:09:15Z

‎S: Added system field

Drn@ecs.soton.ac.uk: /* E */ Added EPrint control page

2023-04-20T11:03:22Z

‎E: Added EPrint control page

Drn@ecs.soton.ac.uk: /* Zero Flavour */

2023-04-10T10:47:29Z

‎Zero Flavour

Drn@ecs.soton.ac.uk: /* Z */ Added zero flavour No longer work in progress

2023-04-10T10:46:12Z

‎Z: Added zero flavour No longer work in progress

Th.lauke@arcor.de: additional recipients added

2023-01-02T10:02:21Z

additional recipients added

Th.lauke@arcor.de: typo removed

2022-09-26T09:49:12Z

typo removed

@@ Line 621: / Line 621: @@
 === Trigger ===
-Allows a function to be defined that will be called at a particular execution point.  Such as before or after an eprint record is committed or when rewriting the request for a URL to return the appropriate resource.
+[[Triggers]] allow a function to be defined that will be called at a particular execution point.  Such as before or after an eprint record is committed or when rewriting the request for a URL to return the appropriate resource.
 == U ==

@@ Line 619: / Line 619: @@
 These are [[#Data object|data objects]] that are sub-objects of [[#Second class data object|second class data objects]] to exist, which in turn are sub-objects of [[#First class data object|first class data objects]].  The main example of such a data object in [[#EPrints repository software|EPrints repository software]] is a [[#File|file]] data object.
   File --sub-object of--> Document --sub-object of--> EPrint
 == U ==

@@ Line 98: / Line 98: @@
 === Core field ===
-Same as a [[#System field]].
+Same as a [[#System field|system field]].
 === Contact page ===

@@ Line 96: / Line 96: @@
 * [[perl_lib/]]
 * [[tools/]]
 === Contact page ===

@@ Line 591: / Line 591: @@
 === Sword API ===
 This is an API provided by [[#EPrints repository software|EPrints repository software]] that complies with the [https://guides.dataverse.org/en/latest/api/sword.html SWORD specification] for a RESTful API.  It is similar to EPrints' [[#CRUD API|CRUD]] and [[#REST API|REST]] APIs but is intended to facilitate smoother interoperability between different types of Open Access repository, using an [https://datatracker.ietf.org/wg/atompub/about/ atompub] based XML format and the [https://www.dublincore.org/specifications/dublin-core/dcmi-terms/ Dublin Core schema] for [[#Metadata|metadata]] terms.
 == T ==

@@ Line 183: / Line 183: @@
 === EPrint ===
 An [[EPrint Object|eprint]] is a [[#First class data object|first class]] [[#Data object|data object]] in [[#EPrints repository software|EPrints repository software]]. These are often referred to as ''[[#Item|items]]'' or ''[[#Publication record|publication records]]'' as they are generally intended hold [[#Metadata|metadata]] about a publication of some kind.
 === EPrint history ===

@@ Line 722: / Line 722: @@
 == Y ==
 == Z ==
-=== Zero Flavour ===
+=== Zero flavour ===
 This is a minimal [[#Flavour|flavour]] to create very basic [[#Archive|archives]] with simple [[#EPrint|eprint]] [[#Data object|data objects]].  This may be useful if you want to develop a non-publications repository that requires a lot of bespoke configuration.  As it saves having to override exisiting publications-based configuration.
 [[Category:FAQ]]

@@ Line 517: / Line 517: @@
 == S ==
 === Saved search ===
-This is a [[#Second class data object|second class]] [[#Data object|data object]] that records the criteria of a particular search made by a [[#User|user]].  Its purpose is to allow the user to receive regular email updates about results that meet these criteria.
+This is a [[#Second class data object|second class]] [[#Data object|data object]] that records the criteria of a particular search made by a [[#User|user]].  Its purpose is to allow the user (or even some [[Additional_Recipients_on_Saved_Searches|additional recipients]]) to receive regular email updates about results that meet these criteria.
 === Screen plugin ===

@@ Line 691: / Line 691: @@
 === Volatile metadata field ===
-This is a [[#Metadata field|metadata field]] that is liable to change on a regular basis but does not really affect the overall content of the [[#Data object|data object]]'s [[#Metadata|metadata]], so should not prompt a new [[#Revision|revision]] to be generated.  A metadata field can be made volatile by setting the following atttribute in the field definition:
+This is a [[#Metadata field|metadata field]] that is liable to change on a regular basis but does not really affect the overall content of the [[#Data object|data object]]'s [[#Metadata|metadata]], so should not prompt a new [[#Revision|revision]] to be generated.  A metadata field can be made volatile by setting the following attribute in the field definition:
   volatile => 1,
-Metadata fields that are only intended for administrative purposes are often defined as volatile, such as the [[#EPrint|eprint]] [[#EPrint locking|edit_lock]] metadata field.  If a [[#User|user]] takes an edit lock on an eprint, if the edit_lock metadata field field was non-volatile, this would lead to a new revision being create for the eprint when ultimately nothing had yet changed.  In fact, worse still, if the edit lock was released without making any changes, a further revision would be created, which would be basically the same as the revision before the user took the edit lock.
+Metadata fields that are only intended for administrative purposes are often defined as volatile, such as the [[#EPrint|eprint]] [[#EPrint locking|edit_lock]] metadata field.  If a [[#User|user]] takes an edit lock on an eprint, if the edit_lock metadata field was non-volatile, this would lead to a new revision being create for the eprint when ultimately nothing had yet changed.  In fact, worse still, if the edit lock was released without making any changes, a further revision would be created, which would be basically the same as the revision before the user took the edit lock.
 == W ==