To be backward compatible, the current way to configure an authority over a metadata will automatically imply that the same configuration applies to all the collections.įinally, the hierarchical controlled vocabulary feature will be supported thanks to the search methods proposed in (to be updated according to the new endpoints structure). This is currently partially broken in DSpace 7 beta 2.
#DSPACE CONTROL DESK MEANS FREE#
The reason of this change can be found in the way that value-pairs are managed, it is possible to define a collection where the dc.type comes from a list and another collection that uses a different list or either just free text. This is a bit more flexible than what was feasible in DSpace < 7 as the authority plugin was associated at level of metadata and it was not possible to associate different plugin for the same metadata depending on the collection. It should be noted that the above search method means that an authority plugin can be now associated with a specific metadata eventually for a specific collection. There is not plan to change what is eventually stored (as the authority ID is not necessarily stored) in the metadatavalue, the authority pluginname will be retrieved when necessary via a new search method. Please note that the ID will be a combination of the authority pluginname and the authority value usually stored in the metadata. This endpoint is needed to provide a persistent direct access to authority value and support the Controlled-Vocabulary hierarchical visualization via the additional search methods included here (to be updated according to the new proposed endpoint /integration/authorityValues) In the case that no result is found the angular application will be free to prompt an alert or keep the current value displaying it as is.Ī new endpoint /api/integration/ authorityValues/: will be implemented supporting only direct GET request to a specific ID. when a submission is resumed) as the display value must be shown to the user instead of the stored value. This parameter will be used by angular to retrieve the Choice related to an existing metadatavalue (i.e. To indicate that the search must use the getBestMatch method of the authority framework and only return the first Choice that matches exactly with the authority if provided or with the value. Moreover, we want to add an extra parameter to the /api/integration/authorities//choices endpoint If the authority value must be stored or not when available will be indicated by a new attribute in the authority endpointīut the REST client can also guess this directly from the authorit圜hoice response that could eventually include an authorityValue link without an authority attribute. The relevant changes here are there is not anymore an ID attribute, as this object is not directly addressable in the URL the _link section eventually contains a reference to an authorityValue but there is not self link Please note that the existence of an authority will not imply that an authority id must be stored.
#DSPACE CONTROL DESK MEANS PATCH#
should use in the subsequent PATCH request. The value and eventually the authority are what the client should store in the metadatavalue, i.e. The display value is what we expect that the Angular UI (or any other REST client) will show to the user. "value": "Research Subject Categories::HUMANITIES and RELIGION::Religion/Theology", "value": "Research Subject Categories::HUMANITIES and RELIGION::Religion/Theology::Church studies", "value": "Research Subject Categories::HUMANITIES and RELIGION::Religion/Theology::History of religion", Will be renamed in /api/integration/authorities// choicesĪnd will be changed to return options to present in the UI not directly related with an authority value, i.e. The following REST contract will be changed more specifically the dropdown in submission, aka value pairs.use a single infrastructure to provide support for all the different controlled values features available in DSpace, i.e.This mean that NO changes in the existing metadata and related configuration (browse, search) will be needed for Institution that comes from a previous version modify the 7.0beta2 implementation to revert changes in how the information is stored, avoiding to force the use of the authority value where not necessary/liked.Therefore, this page is now OBSOLETE and the REST CONTRACT should be considered the latest version. As agreement has been achieved it has moved forward into this REST Contract PR. This page represented a temporary discussion area.
0 kommentar(er)
