Date: Thu, 28 Mar 2024 16:51:28 -0400 (EDT) Message-ID: <569144507.28918.1711659088005@lyrasis1-roc-mp1> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_28917_1766790931.1711659088005" ------=_Part_28917_1766790931.1711659088005 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Identifiers can be specified in REST API calls and generated either automa=
tically using the internal PID minter or via an external REST service.
If an identifier has already been generated by an application, you can s= pecify it when creating resources using the PUT method:
PUT /re= st/abc123
Response:
Status:= 201 Created =20 Headers: Location: http://localhost:8080/rest/abc123
To have identifiers automatically generated using the internal PID minte= r, an application can use the POST method:
POST /r= est
Response:
Status:= 201 Created =20 Headers: Location: http://localhost:8080/rest/5b6ff353-b4fc-4b9a-8e36-89f74645327b= pre>
Fedora 4 can also be configured to retrieve identifiers from an external= HTTP minter service. When a new object or datastream is created usin= g the POST method, an identifier will be created using the external PID min= ter. See Configuring an External PID Minter.
To use a different identifier generation process, you can create a custo= m PID minter implementation, which can be configured in the same way as the= external PID minter. If your identifiers are generated from an HTTP = service, then you should consider extending (or improving) Htt= pPidMinter.java to meet your needs. Implementing UniqueValueSupplier.java is a= nother option.