[{"data":1,"prerenderedAt":173},["ShallowReactive",2],{"\u002Ftools\u002Fid_manager\u002Fdocs\u002Fwebui\u002F":3},{"id":4,"title":5,"body":6,"description":149,"extension":160,"isRevision":161,"lastUpdated":162,"meta":163,"navigation":165,"path":166,"revision":167,"seo":168,"slug":169,"stem":170,"subtitle":171,"__hash__":172},"docs\u002Fdocs\u002Fid_manager\u002Fwebui\u002Findex.md","ID Management Service",{"type":7,"value":8,"toc":148},"minimark",[9,14,19,27,30,35,41,44,48,63,74,87,93,99,102,105,108,112,118,121,125,131,134,138,141,145],[10,11,13],"h2",{"id":12},"using-the-web-interface","Using the Web Interface",[15,16,18],"h3",{"id":17},"query-links-screen","Query links screen",[20,21,22],"p",{},[23,24],"img",{"alt":25,"src":26},"Query Links","img\u002Fquerylinks.png",[20,28,29],{},"The primary full query interface (which is also the home screen) makes it is possible to build a query, view the matching links, and provides a direct insight into the data. The user can also login to access the parts of the interface where they can make changes to the data (create, delete, and edit). This uses the same username credentials as is used for the API, and can either be a single user sign on (single set of credentials) or backed by an LDAP store of accounts.",[31,32,34],"h4",{"id":33},"make-a-query","Make a Query",[20,36,37],{},[23,38],{"alt":39,"src":40},"Query Links form view","img\u002Fquerylinksform.png",[20,42,43],{},"The data shown in the query page when first opened is that of an unfiltered query - no query fields have been specified, and any link in the system will match and the first page of these matches will be displayed. Each row corresponds to a single link, displaying the body and target URIs in a simplified way to make it easier to read. The hyperlinks contain the actual URIs, but the text of those links are more descriptive and simplified for reading and browsing. The additional metadata for a link will consist of things like its dcterms:title, dcterms:alternative, and group_id if it has them. Clicking on the link item at the start of the row will take the user to the page specific to that link with all its metadata.",[31,45,47],{"id":46},"query-parameters","Query parameters",[20,49,50,54,55,58,59,62],{},[51,52,53],"strong",{},"Body ID",", ",[51,56,57],{},"Target ID"," or the '",[51,60,61],{},"Either Body or Target ID","' query fields should contain the exact URI that is being queried for. If it is different, even by a single character, it will not match. The 'Either Body or Target ID' field will match any link where the value is found as either the body ID or the target ID.",[20,64,65,66,69,70,73],{},"The ",[51,67,68],{},"Body Generator"," and the ",[51,71,72],{},"Target Generator"," also need to be exact or left blank. There are a lot of identifiers in the Getty environment which have no global URI (eg something beginning with HTTP(S) that resolves to a webpage) or a persistent ID, and so it is important to state which system a particular identifier comes from and this is what the generator is used for. It encodes the metadata about which system or group is responsible for creating this ID, or what system it is maintained by. The list of generators isa fixed list, rather than being a free text field. There are only certain generators supported by an ID Managment instance which can be expanded as necessary. The generators will often be suffixed by something that strongly hints to the source within the Getty environment, like \"aspace\", \"rosetta\" or \"GRI\".",[20,75,65,76,79,80,86],{},[51,77,78],{},"Motivation"," is an important query field, as the reason why a link exists should be explained by which motivation is used. The motivation classes in use tend to be the ones prefixed by ",[81,82,83],"a",{"href":83,"rel":84},"https:\u002F\u002Fdata.getty.edu\u002Flocal\u002Fthesaurus\u002Fmotivations",[85],"nofollow"," and they can be resolved to see their precise definitions but often the suffix is human-readable and informative, like \"part_of\" or \"contains-refid\".",[20,88,65,89,92],{},[51,90,91],{},"Group ID"," is a metafield, meant for organizing and grouping together links that should be considered as a coherent set, but which might not have a clear semantic way of grouping them within the Web Annotation Model. It is easy to retrieve a set of links by group ID, and there is an API to delete all links that match a group ID also. One typical reason to use a group ID is to mark a set of links that were made that depend on a specific source resource or record. When that resource or record is updated, it is faster and easier to delete all the links the old resource had led to and add the new ones fresh, than it is to try to work out the difference and remove outdated links and only add the new.",[20,94,65,95,98],{},[51,96,97],{},"Creator"," is a free text field that is rarely used for the links created by automated processes, but will be useful when more individuals add links manually. It should reflect the name of the individual that created the link.",[20,100,101],{},"The ID Management service is a store for links, but it does not enforce what ID can connect to what other ID. A motivation is not limited to certain body or target IDs, and vice versa, any URI can be connected to any other if desired. Any authorized user can add a link as long as that link has at a minimum a body and a target, each with an ID and a valid generator, and a valid motivation. This generalized use is reflected in its basic interface. The preset queries show a number of the important patterns that are commonly used in the data, but this query interface is not for one specific purpose.",[20,103,104],{},"Click the Submit button to make the query, and the response will contain whatever links match (in database ordering - this will mostly mean the newest created links first. This db-ordered response is the fastest way to return paginated result sets and speed is often the critical factor here).",[20,106,107],{},"The Link icon at the start of each row will open a page specific to a given link, allowing the user to view just that link's information (or if logged in, edit and delete the link too).",[15,109,111],{"id":110},"presets","Presets",[20,113,114],{},[23,115],{"alt":116,"src":117},"Preset Query list","img\u002Fpresetqueries.png",[20,119,120],{},"This page lists a number of preset queries for commonly queried for things. They are purposed queries and will often return simplified responses as they are intended to be incorporated in other interfaces, as well as being generally useful. The preset queries show what sort of link annotation pattern they use, but presets like the \"What links does this identifier feature in\" and \"HMO URI to Archival component JSON-LD\" will do more than just a straightforward query and this is described in their text.",[15,122,124],{"id":123},"create-a-link","Create a Link",[20,126,127],{},[23,128],{"alt":129,"src":130},"Create link form","img\u002Fcreatelink.png",[20,132,133],{},"This link only appears when the user has been successfully authenticated. This form can hold all the possible information that can be manually set or updated in a link. It only creates a new link when the Submit button is clicked. It will redirect to the URL specific for that link (which is the links 'id' URI). A link's page also allow the user to update the data or delete the link as required.",[15,135,137],{"id":136},"authentication-loginlogout","Authentication (Login\u002Flogout)",[20,139,140],{},"The login page asks for a username and password which can be provided by the instance administrator, there is no system to sign up to use it through the app itself. It will either have a single set of credentials, or be backed by an LDAP account service.",[15,142,144],{"id":143},"motivationsgenerators","Motivations\u002FGenerators",[20,146,147],{},"These pages will show the currently registered motivations and generators respectively, and only registered URIs can be used in Links. There is no way through the web interface to adjust these URIs as adding or, especially, removing registered URIs is powerful and has repercussions that need to be communicated to all users before doing so.",{"title":149,"searchDepth":150,"depth":150,"links":151},"",2,[152],{"id":12,"depth":150,"text":13,"children":153},[154,156,157,158,159],{"id":17,"depth":155,"text":18},3,{"id":110,"depth":155,"text":111},{"id":123,"depth":155,"text":124},{"id":136,"depth":155,"text":137},{"id":143,"depth":155,"text":144},"md",false,"2026-03-30",{"contentPath":164},"\u002Fdocs\u002Fid_manager\u002Fwebui\u002F",true,"\u002Fdocs\u002Fid_manager\u002Fwebui","\u002Ftools\u002Fid_manager\u002Fdocs\u002Frevision\u002F",{"title":5,"description":149},"\u002Ftools\u002Fid_manager\u002Fdocs\u002Fwebui\u002F","docs\u002Fid_manager\u002Fwebui\u002Findex","Service for creating, updating and managing links between identifiers.","yp6GrFFf7yGo5956HSXK8atqe_SNgK5QkI5m3Fh6Nyk",1782833579825]