Digital Object Identifier (DOI)
Introduction¶
The Digital Object Identifier (DOI) plugin provides additional API endpoints that allow the integration of any Mauro multi-facet aware catalogue item to be recorded in a DOI system; this then allows unique, permanent identifiers to those catalogue items that can then be distributed across documents or articles over the web to act as links back to the Mauro content. The DOI system always ensures that a DOI name will always refer to a Mauro catalogue item as long as the DOI name is known. The plugin uses DataCite as the repository of Mauro DOI names; more information can be found at the DataCite website.
In order to use Digital Object Identifiers, the Mauro instance must:
- Have the Mauro Digital Object Identifier plugin installed.
- Set up and configure DataCite to acts as the DOI system.
The full details of this set up can be viewed in the user guide Using Digital Object Identifiers.
Profile¶
Profile summary¶
The plugin automatically exposes a profile called Digital Object Identifiers DataCite Dataset Schema. Depending on whether the profile is used or unused on a catalogue item, the summary of the profile can be found with one of these endpoints:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 |
|
Get the profile¶
To get the profile, use the usual profiles endpoint:
For the case of the DOI profile:
- The {namespace} will be
uk.ac.ox.softeng.maurodatamapper.plugins.digitalobjectidentifiers.profile
. - The {name} will be
DigitalObjectIdentifiersProfileProviderService
.
Information
The GET
endpoint will always return the profile data, even if the profile has not yet been assigned to the catalogue item. In the case where it has not been assigned yet, an empty profile structure will be returned containing all the fields to prepare.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 |
|
Save the profile¶
Using the JSON structure from the GET
endpoint above and entering values into the sections/fields/currentValue
JSON properties, you can save the changes made to the profile, and attach the profile to the catalogue item at the same time, like so.
Where:
- The {namespace} will be
uk.ac.ox.softeng.maurodatamapper.plugins.digitalobjectidentifiers.profile
. - The {name} will be
DigitalObjectIdentifiersProfileProviderService
.
If successful, this will return the same JSON response as the GET
endpoint above.
Remove the profile¶
To remove the DOI profile from the catalogue item:
Where:
- The {namespace} will be
uk.ac.ox.softeng.maurodatamapper.plugins.digitalobjectidentifiers.profile
. - The {name} will be
DigitalObjectIdentifiersProfileProviderService
.
DOI Management¶
The profile endpoints above are standard endpoints used in Mauro. This section covers the custom endpoints added by the DOI plugin.
Get DOI status¶
For any catalogue item, the current status of the DOI name on that item can be queried as follows:
If a status exists, a 200 OK
response will be returned with this response body:
1 2 3 4 |
|
The fields are as follows:
- identifier (String): The Digital Object Identifier (DOI) name assigned to this catalogue item as generated by the DOI system. If a DOI has not been generated yet, this will not be provided.
- state (Constant): The current DOI state of this catalogue item, which can one of:
- not submitted - no DOI has been requested yet.
- draft - a draft DOI has been assigned, allowing further changes to the profile.
- final - a DOI has been assigned and locked, finalising this catalogue item's profile.
- retired - a previous DOI has been retired and can no longer be used for cross-reference.
Submit DOI status¶
Submitting the catalogue item and its DOI profile can only be done for publicly readable and finalised catalogue items. This is to ensure that:
- Every citation has access to the catalogue item.
- The catalogue item cannot be modified any further, keeping the citation the same for all future uses.
Information
It may be possible to not have assigned the Digital Object Identifiers DataCite Dataset Schema to a catalogue item before it was finalised. To solve this issue, the DOI profile has special permissions to allow it to be edited post-finalisation, so long as the DOI is not yet in the Final state.
Therefore, you may use the POST /api/{multiFacetAwareDomainType}/{id}/profiles/{namespace}/{name}
endpoint as many times as necessary to make alterations to the profile before continuing further.
To submit the catalogue item's profile to the DOI system to obtain a DOI name, use this endpoint.
This endpoint requires no request body; the profile should already have been saved before this point. The submissionType can be one of the following:
- draft - submit a draft profile to obtain the DOI name.
- finalise - submit a final profile to obtain the DOI name.
- retire - retire an existing DOI name to no longer be in active use.
The response returned will be the contents of the catalogue item the DOI was for. The plugin will also automatically populate the DOI profile identifier
metadata key for the catalogue item.
Remove DOI¶
To remove all DOI metadata:
DOI Resolution¶
The identifier
in the DOI profile will hold the unique identifier as registered in the DOI system, for example 10.1109/5.771073
. The DOI system has a guaranteed method of locating every registered DOI name through a non-changing URL; this will actually redirect back to your client URL by providing the DOI name in the URL - in Mauro, this would be similar to https://{domain}/#/doi/10.1109/5.771073
To actually locate the catalogue item assigned to this DOI name, this endpoint will fetch the Mauro catalogue item to which the DOI name is mapped.
The JSON response will contain the full catalogue item details for that DOI name. See the REST API for the exact details returned per catalogue item domain type.