View by product

Which XML delivery mode is the best for my needs?

Last updated on December 05, 2023

Method	Typical use	Main characteristics
XML Flat Files via sFTP server	When my use-case needs the full Embase data and I work with this in-house	Initial full data dump Daily changes including new records, updates on existing records, and deletions The full data can now be updated on a weekly basis if needed, and we recommend to reload it 3 times/year after an Emtree release, to benefit from the indexing backposting
API XML/JSON	API is the advised method only to query very specific data sets, not for updating the full data	Queries a subset of the current data (<100,000 records) Currently has a different output format from Flat Files, but will be aligned in the future
XML download from .com	Is sometimes used for development purposes but not a supported DaaS method	The content aligns with other .com exports (excel, word, etc.) but the format currently is different from the DaaS formats such as Flat File and API.

Method

Typical use

Main characteristics

XML Flat Files via sFTP server

When my use-case needs the full Embase data and I work with this in-house

Initial full data dump
Daily changes including new records, updates on existing records, and deletions
The full data can now be updated on a weekly basis if needed, and we recommend to reload it 3 times/year after an Emtree release, to benefit from the indexing backposting

API XML/JSON

API is the advised method only to query very specific data sets, not for updating the full data

Queries a subset of the current data (<100,000 records)
Currently has a different output format from Flat Files, but will be aligned in the future

XML download from .com

Is sometimes used for development purposes but not a supported DaaS method

The content aligns with other .com exports (excel, word, etc.) but the format currently is different from the DaaS formats such as Flat File and API.

Current method	What it means for my company?	What are my next actions?
XML Flat Files via sFTP server	New delivery is available – migration can start now and is to be finished in 2023	Get the info package about how the new delivery process and file format Make sure my technical team starts setting-up the access to the new s3 bucket and testing the new data to implement necessary changes on our end Inform Elsevier once we have transferred our processes to the new delivery
API XML/JSON	New API is now available.	Get the info package about new API from your sales representative Have the technical team testing the new API and Inform Elsevier once the process is migrated
Combination of Flat File and API updates	Start now to migrate Flate File process. API to be migrated later.	Review for my use-case if combining two formats is still the best process for us If yes: follow the two migrations as described for each method If no: discuss with Elsevier how to best switch to a single method

Current method

What it means for my company?

What are my next actions?

XML Flat Files via sFTP server

New delivery is available – migration can start now and is to be finished in 2023

Get the info package about how the new delivery process and file format
Make sure my technical team starts setting-up the access to the new s3 bucket and testing the new data to implement necessary changes on our end
Inform Elsevier once we have transferred our processes to the new delivery

API XML/JSON

New API is now available.

Combination of Flat File and API updates

Start now to migrate Flate File process.
API to be migrated later.

Review for my use-case if combining two formats is still the best process for us
1. If yes: follow the two migrations as described for each method
2. If no: discuss with Elsevier how to best switch to a single method

Did we answer your question?