Status | ||||
---|---|---|---|---|
|
...
Class | UI field | JSON Field | Relationship / Dependency | Type of reference | Example | ||||
---|---|---|---|---|---|---|---|---|---|
Journals (works) API: oa/works/citation | Instance / Namespace | /"instances"/"ids"/"ns" | UI: Settings/Pick list: PublicationIdentifier.Type API: /oa/refdata | string | issn | ||||
/"instances"/"subType" | |||||||||
/"indexedInDOAJ"/ | |||||||||
/"oaStatus"/ | |||||||||
People (party) API: oa/party | Institution level 1 | /"institutionLevel1"/"id" | UI: Settings/Pick list: Party.InstitutionLevel1 API: /oa/refdata | UUID | |||||
Requests API: /oa/publicationRequest | Publisher | /"publisher"/"id" | UI: Settings/Pick list: PublicationRequest.Publisher API: /oa/refdata | UUID | |||||
Corresponding author | /"correspondingAuthor"/"partyOwner"/"id" | UI: People / person API: /oa/party JSON: /"id"/ | UUID | ||||||
Institution level 1 | /"correspondingAuthor"/"partyOwner"/"institutionLevel1"/"id" | UI: Settings/Pick list: Party.InstitutionLevel1 API: /oa/refdata | UUID | ||||||
/"correspondingInstitutionLevel1"/"id" | UI: Settings/Pick list: Party.InstitutionLevel1 API: /oa/refdata | UUID | |||||||
Corresponding author (implicit) | /"correspondingAuthor"/"role" | UI: Settings/Pick list: RequestParty.Role API: /oa/refdata | string | corresponding_author request_contact (not customizable) | |||||
Request contact | /"requestContact"/"partyOwner"/"id" | UI: People / person API: /oa/party JSON: /"id"/ | UUID | ||||||
/"requestContact"/"role" | UI: Settings/Pick list: RequestParty.Role API: /oa/refdata | string | corresponding_author request_contact (not customizable) | ||||||
Status | /"requestStatus"/ | UI: Settings/Pick list: PublicationRequest.RequestStatus | string | open, closed (not customizable) | |||||
Publication status (repeatable) | /"publicationStatuses"[n]/"publicationStatus"/"id" | UI: Settings/Pick list: PublicationStatus.PublicationStatus API: /oa/refdata | UUID | ||||||
License | /"license"/"id" | UI: Settings/Pick list: PublicationRequest.License API: /oa/refdata | UUID | ||||||
Publication type | /"publicationType"/"id" | UI: Settings/Pick list: PublicationRequest.Subtype API: /oa/refdata | UUID | ||||||
Journal | /"work"/"id" | UI: Journal API: oa/works/citation JSON: /"id"/ | UUID | ||||||
Journal in DOAJ | /"workIndexedInDOAJ"/"id" | UI: - API: /oa/refdata | UUID | (not customizable) | |||||
Journal OA status | /"workOAStatus"/"id" | UI: Settings/Pick list: Work.OaStatus | UUID | ||||||
Charges |
| ||||||||
Checklist |
|
...
Tip | ||||
---|---|---|---|---|
| ||||
more data ... { ... more data |
...
Tip | ||||
---|---|---|---|---|
| ||||
|
Tip | ||||
---|---|---|---|---|
| ||||
|
Tip | ||||
---|---|---|---|---|
| ||||
|
All we need is JSON conversion
...
Mainly these might be of interest:
API | Use |
---|---|
GET {{OKAPI}}/oa/refdata?max=100 | to get all reference data values and UUIDs |
POST {{OKAPI}}/oa/works/citation | to post journal data |
GET {{OKAPI}}/oa/works | to get journal data |
GET {{OKAPI}}/oa/works/{{UUID}} | to get journal data based on a specific journal UUID |
POST {{OKAPI}}/oa/party | to post people data |
GET {{OKAPI}}/oa/party | to get people data |
GET {{OKAPI}}/oa/party/{{UUID}} | to get people data based on a specific person UUID |
POST {{OKAPI}}/oa/publicationRequest | to post publication requests |
GET {{OKAPI}}/oa/publicationRequest | to get publication requests |
PUT {{OKAPI}}/oa/publicationRequest | to update requests, i.e. to import checklist items |
GET {{OKAPI}}/oa/publicationRequest/{{UUID}} | to get a publication request based on a specific request UUID |
POST {{OKAPI}}/oa/charges | to post charges |
The actual import can be done e.g. with Postman (Runner function) or ask your local IT, systems librarian or library network.
How to know and learn what the API needs?
The Folio frontend also uses the API (OKAPI) to create, update, and delete records. Using the Firefox Developer Tools / Network Analysis, the corresponding API calls from the frontend to OKAPI can be viewed, i.e. API method, endpoint and the actual payload (JSON). This can help to understand how to prepare corresponding imports for migration.