Date: Thu, 28 Mar 2024 14:01:17 +0000 (UTC) Message-ID: <1969324637.5.1711634477559@81e7148dc484> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_4_473072356.1711634477558" ------=_Part_4_473072356.1711634477558 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The Third Iron Data Serv= ice API is a collection of endpoints through which arbitrary metadata may b= e retrieved from the Third Iron metadata database. The endpoints are divide= d into three categories: query endpoints, lookup by id endpoints, and relat= ed metadata retrieval endpoints.
This service is an optional add-= on to other Third Iron services designed for advanced use cases and custome= rs with existing technical knowledge. This service does not have any = UI, and is provided as a set of API endpoints only. If your organization is interested in using the Data= Service, please = contact us for pricing a= nd more information.
Query endpoints are the endpoints of the data service API which allow cl= ients to search for content that meets some criteria specified through para= meters. The Data Service API currently includes the following query endpoin= t:
Lookup by id endpoints are the endpoints of the data service API which a= llow clients to retrieve a representation of a particular record in the Thi= rd Iron metadata database by providing the unique id value assigned to the = record. Lookup is typically performed by submitting a GET request to an API= URL which includes the record=E2=80=99s id number in one of the path segme= nts of the URL. The Data Service API currently includes the following looku= p by id endpoints:
Related metadata retrieval endpoint - endpoints which allow for retrieva= l of metadata records that are related to some other known metadata record,= such as retrieving the article records related to a given issue record
A typical use case may be to use the data= service as a data source for a current awareness system that might appear = within a website or be used to generate email notifications to users. =
To begin, utilize the Journal New Content Lookup endpoint to query = the system for the time interval into the past you want to retrieve in orde= r to know which journals released new issues. For example, you can co= mpile a list of journals who released a new issue in the previous week.
Next, store the response and do any filte= ring on the results that may be appropriate (for example, storing only sele= cted ISSNs in order to single out particular journals or perhaps to filter = by SJR value in order to only see the most "prestigious" journals.).
Use the Third Iron id present in each rec= ord post-filtering then to Retrieve the Current Issue id of the journal.
Take this current issue ID and then use t= he pages response of Retrieve articles of issue t= o gain a complete listing of article metadata for that issue. Filter = the results of that as appropriate and iterate as needed over each Third Ir= on ID.