blob: 03c2981a4c27c00b9f325aa1fa8d699e1cf40045 (
plain)
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
|
# Cookbook
### Updating an Existing Entity
1. Fetch (GET) the existing entity
2. Create (POST) a new editgroup
3. Update (PUT) the entity, with the current revision number in the `prev` edit
field, and the editgroup id set
4. Submit (POST? TBD) the editgroup for review
### Merging Duplicate Entities
1. Fetch (GET) both entities
2. Decide which will be the "primary" entity (the other will redirect to it)
3. Create (POST) a new editgroup
4. Update (PUT) the "primary" entity with any updated metadata merged from the
other entity (optional), and the editgroup id set
5. Update (PUT) the "other" entity with the redirect flag set to the primary's
identifier, with the current revision id (of the "other" entity) in the
`prev` field, and the editgroup id set
4. Submit (POST? TBD) the editgroup for review
### Lookup Fulltext URLs by DOI
1. Use release lookup endpoint (GET) with the DOI a query parameter, with
`expand=files`
2. If a release hit is found, iterate over the linked `file` entities, and
create a ranked list of URLs based on mimetype, URL "rel" type, file size,
or host domain.
### Batch Insert New Entities (Bootstrapping)
When bootstrapping a blank catalog, we need to insert 10s or 100s of millions
of entities as fast as possible.
1. Create (POST) a new editgroup, with provenance information included
2. Batch create (POST) entities
|
