Your gateway to millions of microforms and digital reproductions of books

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
get_involved-promote_your_collections-eromm_request-api [2011-08-10, 17:07]
jahnke [Properties of the response object]
get_involved-promote_your_collections-eromm_request-api [2024-02-29, 08:55]
schleier removed
Line 1: Line 1:
 ====== EROMM Request API ====== ====== EROMM Request API ======
 +**//Please note: This page is still in development.//​**
 +
 With just a little scripting, you can plug EROMM Request into your local Document Order and Delivery System or ILS or even build your own application to maintain your incoming requests. The EROMM Request API consists of a number of (RESTful) webservices which will return JSON objects as default (or HTML if you explicitly ask for it). With just a little scripting, you can plug EROMM Request into your local Document Order and Delivery System or ILS or even build your own application to maintain your incoming requests. The EROMM Request API consists of a number of (RESTful) webservices which will return JSON objects as default (or HTML if you explicitly ask for it).
  
Line 92: Line 94:
 |//​auth.supplier//​|Supplier ID associated with the current login| |//​auth.supplier//​|Supplier ID associated with the current login|
 |//​auth.user//​|User ID associated with the current login| |//​auth.user//​|User ID associated with the current login|
 +|//​data//​|In response to a call that lists requests (e.g. new requests, updated requests etc.) the request information is given in a list of objects in the //data// property. The properties used are the same as for a single request, except that //verbose// and //​data.messages//​ are not included|
 |//​data.messages.[].dateCreated//​|Date on which the message has been created| |//​data.messages.[].dateCreated//​|Date on which the message has been created|
 |//​data.messages.[].message//​|Message ID| |//​data.messages.[].message//​|Message ID|
Line 109: Line 112:
 |//​token//​|the current authentication token| |//​token//​|the current authentication token|
 |//​user//​|ID of the user who initiated the request (for full information see //​verbose.user//​)| |//​user//​|ID of the user who initiated the request (for full information see //​verbose.user//​)|
-|//​verbose.supplier.address|Address of the supplying institution|+|//​verbose.supplier.address//|Address of the supplying institution|
 |//​verbose.supplier.info//​|Short information on the supplying institution| |//​verbose.supplier.info//​|Short information on the supplying institution|
 |//​verbose.supplier.isil//​|ISIL of the supplying institution,​ if the supplying institution is a library| |//​verbose.supplier.isil//​|ISIL of the supplying institution,​ if the supplying institution is a library|
Line 122: Line 125:
 |//​verbose.title.pTitleSet//​|Collective title of the mulit-volume work the original publication is part of| |//​verbose.title.pTitleSet//​|Collective title of the mulit-volume work the original publication is part of|
 |//​verbose.title.sImprint//​|Imprint statement of the surrogate| |//​verbose.title.sImprint//​|Imprint statement of the surrogate|
-|//​verbose.title.sLocation|Location of the surrogate (library and shelfmark)| +|//​verbose.title.sLocation//|Location of the surrogate (library and shelfmark)| 
-|//​verbose.title.sPhysicalDescription|physical description of the surrogate|+|//​verbose.title.sPhysicalDescription//|physical description of the surrogate|
 |//​verbose.title.sSeries//​|Title of the reprodction series, the item is part of| |//​verbose.title.sSeries//​|Title of the reprodction series, the item is part of|
 |//​verbose.title.sVolume//​|Volume number if the item is part of a reproduction series| |//​verbose.title.sVolume//​|Volume number if the item is part of a reproduction series|
Last modified:: 1970-01-01, 1:00