Advanced Export Queries

Advanced export queries can be run either manually or by using predefined export profiles. To perform an advanced export query, click the Advanced Export Queries tab. The following window opens:

For information on using predefined export profiles, see Advanced Export Profiles.

This section describes how to use SQL scripts to retrieve information about active full text journals from the SFX database. This section includes:

Manual Export
Text Tab-Delimited File Format
HTML File Format
MARC XML File Format
Aleph Sequential Format
KBART Format
PubMed XML LinkOut Format
Google Scholar Format
CDI Format
Export File Naming Conventions

Manual Export

The following section describes how to perform a manual advanced export query.

To perform a manual advanced export query:

Select one of the following output formats:
- Tab-delimited TXT
- HTML
- XML
- ALEPH Sequential
- KBART
- PubMed XML LinkOut
- Google Scholar
- CDI
Choose to include serials (for example, journals) and/or monographs (for example, books) in the export file.
When choosing to export serials, objects with the following object types are exported:
- JOURNAL
- SERIES
- CONFERENCE
- NEWSPAPER
- TRANSCRIPT
- WIRE
When choosing to export monographs, objects with the following object types are exported:
- PROCEEDING
- BOOK
- DISSERTATION
- DOCUMENT
- MANUSCRIPT
- REPORT
- CD
- DATABASE
- VIDEO
- AUDIO
- SCORE
Specify institute information (optional).

If institutes have been defined, it is possible to filter the export query results by institutes or groups. (For more information about institutes, refer to the Institute Feature section of the SFX Advanced User's Guide.) Select an institute from the Restrict to the following institutes/groups (optional) text box.

Select Default to export only books/journals active for DEFAULT. Institute-specific activations are not included.

Select one institute to export all books/journals active for that institute, active for the group to which the institute is affiliated, or active for DEFAULT. (Note that group or default activations are not included if an item is explicitly set to inactive for the institute.)

Select one group to export all books/journals active for that group or active for DEFAULT (and not explicitly set to be inactive for the group). Note that when selecting a group, objects active for institutes affiliated with the group are not included in the export file.

When more than one institute (or institutes and groups) are selected, a file is generated that contains anything active for the institutes selected, active for the group, or active for DEFAULT. Note that when the output is in CDI format, it is not possible to select multiple institutes or groups.

If you do not select an institute, the export includes all items active for at least one institute, group, or DEFAULT.

The export file contains coverage specific for the institute. If no institute or group date thresholds have been specified, the default local or global threshold is used for the coverage statement.

The following hierarchy is used:

Institute-specific date coverage
If there is no institute-specific date coverage, group-specific date coverage is used (but only if the activation is also for the group).
If there is no group-specific date coverage, then the default date coverage is used. (The local threshold is used if it exists; if not, the global threshold is used.)

In the Use the following additional export file (optional) field, specify an additional .txt file to be used when generating the export file in a form other than .txt.
In the Export active portfolios with the following services field, select the type of service you want to export. It is possible to select more than one service type.
From the Export from drop-down list, select either ALL or SPECIFIC and select the targets you want to include in the export.

Depending on what output file format you chose in step 1, different options are now displayed.

For .txt, see Text Tab-Delimited File Format
For HTML, see HTML File Format
For XML, see MARC XML File Format
For Aleph Sequential, see Aleph Sequential Format
For KBART, see KBART Format
For PubMed XML LinkOut, see PubMed XML LinkOut Format
For Google Scholar, see Google Scholar Format
For CDI, see CDI Format

Text Tab-Delimited File Format

To produce an export file in .txt format, first follow the steps in Manual Export and then continue with the following steps:

If Chinese titles are included in the export, select Simplified Chinese Title, Traditional Chinese Title, or Both Simplified and Traditional Chinese Titles to include the type of Chinese titles you want in the title field.
Click Submit.

The .txt format is intended mainly to create export files that can be used to create additional export files containing data from multiple instances.

The following data is included in the .txt file:

Column 1 – Sortable Title (used internally in SFX for sorting purposes)
Column 2 – Title
Column 3 – Title Non-Filing Character
Column 4 – ISSN
Column 5 – Object ID
Column 6 – Target Public Name
Column 7 – Threshold (textual format)
Column 8 – eISSN
Column 9 – Abbreviated Title
Column 10 – Target Service Type
Column 11 – LCCN
Column 12 – Object Portfolio ID
Column 13 – 856-u (empty)
Column 14 – 856-y (empty)
Column 15 – 856-a (empty)
Column 16 – 245_h (empty)
Column 17 – Local Threshold
Column 18 – Global Threshold
Column 19 – Target ID
Column 20 – Target Service ID
Column 21 – Object Portfolio ID
Column 22 – Categories
Column 23 – Local Attribute
Column 24 – ISBN
Column 25 – eISBN
Column 26 – Publisher
Column 27 – Place of Publication
Column 28 – Date of Publication
Column 29 – Object Type
Column 30 – Activation status for DEFAULT
Column 31 – Institute ID (if available)
Column 32 – Institute Name (if available)
Column 33 – Institute Availability (if available)

If multiple INSTITUTE entries exist for a specific journal, there are multiple entries in the .txt file—one for each institute.

Column 34 – Language (three-letter code)
Column 35 – Main Title (important for CJK sorting)
Column 36 – Full Original Title (CJK only)
Column 37 – Additional ISBNs
Column 38 – Additional eISBNs
Column 39 – Author
Column 40 – Owner
Column 41 – THRESHOLD_LOCAL
Column 42 – PARSE_PARAM
Column 43 – IS_FREE (1 = free, 0 = restricted)
Column 44 – General note
Column 45 – Authentication note
Column 46 – Internal note
Column 47 – Alternative titles
Column 48 – DB ID (CDI identifier)
Column 49 – Selective (1 = Yes, 0 = No)
Column 50 – Do not show as Full Text in CDI (1 = Yes, 0 = No)

To include author information, select the Include author information check box.
To include note and authentication information, select the Include note and authentication information check box.
To include internal note information, select the Include Internal note information check box.

If Chinese titles are included in the export, it is possible to select whether Simplified or Traditional Chinese (or both) are included in the title field. If both are exported, the format is:

HTML File Format

To produce an export file in HTML format, first follow the steps in Manual Export and then continue with the following steps:

If Chinese titles are included in the export, select Simplified Chinese Title, Traditional Chinese Title, or Both Simplified and Traditional Chinese Titles to include the type of Chinese titles you want in the title field.
Click Submit.

SFX generates a static HTML list, identifies active full-text object portfolios with active targets and target services, and reformats this data into HTML pages that list items by journal name—one page for each letter of the alphabet. The HTML pages include the following information:

Journal title
ISSN
Public target name
Appropriate thresholds (dates that the journal is available)

For each journal, two links are provided:

A direct link to the Web page of the electronic journal when clicking the journal title
A link to the SFX menu by clicking the SFX button of a particular journal

The redirection option is configured with the Menu Configuration tool located under the Configuration section of Setup & Administration. For more information on redirection, see DirectLink.

After selecting HTML for the output format, a script called E-journals runs at the UNIX level on the SFX server. After this script runs, the following opens:

Export Successful

To display a window with the first HTML file generated by the e-journal script, click Download Result.

HTML Output

The generated HTML lists are located in the following directory:

exlibris/sfx_ver/sfx4_1/<instance name>/templates/e-collection-html/results

The following is an example of an HTML list:

e-journals-A.html e-journals-G.html e-journals-M.html e-journals-S.html

e-journals-B.html e-journals-H.html e-journals-N.html e-journals-T.html

e-journals-C.html e-journals-I.html e-journals-O.html e-journals-U.html

e-journals-D.html e-journals-J.html e-journals-P.html e-journals-V.html

e-journals-E.html e-journals-K.html e-journals-Q.html e-journals-W.html

e-journals-F.html e-journals-L.html e-journals-R.html

Each time the script is run, SFX replaces the HTML files with the new files that are created. There is no need to empty this directory each time the script is run.

The following is the URL of these HTML pages:

http://<sfx_server:port>/<sfx_instance>/e_collection/e-journals-A.html

If you want to have the e-journal lists hosted on a different Web server, replace the base URL of each link with a hard-coded base URL.

The HTML template used to generate these HTML lists can be found in the following location:

exlibris/sfx_ver/sfx4_1/<instance_name>/templates/e-collection-html/listing.tmpl

This HTML template can be customized according to an institution’s preferences.

Some features, such as CJK support and the exporting of institute-specific threshold information, are not supported in the HTML export format. Instead, it is recommended that you use the A-Z list, which can be searched and browsed. For more information, see Configuration and the A-Z List section of the SFX Advanced User’s Guide.

MARC XML File Format

To produce an export file in XML format, first follow the steps in Manual Export and then continue with the following steps:

Select Fresh export or Compare export from previous file. If you select Compare export, select a previous export file to compare against.
- Fresh export – This option exports all active getFullTxt, getHolding, getAbstract, and getTOC portfolios for all active targets or a selection of active targets.
- Compare with previous export – This option exports and compares the export file with a previously created export file. In the header of each record, information indicates whether the record has changed, not changed, been deleted, or added.
  If you select Compare with previous export, you may select Exclude objects that were not changed. This excludes unchanged records but includes new, deleted, or changed ones.

The top part of the export file contains information about the type of export and the name of the SFX instance from which information was exported.

The following is an example of a fresh export:

The following is an example of a compare export:

The first time you create an export file, the drop-down list of previous files is empty, and all items in the XML file are marked as new. The second time you export, the previous file appears in the list. If you choose Compare with previous export and select the previous file, the new export file contains information about changed, unchanged, added, and deleted items. The leader of each record contains status information.

Status information can be found in the sixth character after the leader. For example:

For new records (or if this is the first export created in this format):

For records deactivated or deleted in the SFX database between the previous export and the current export:

This is an important difference between the Fresh and the Compare exports. With Compare exports, the items deleted between the current and previous export are included in the export file.

If a change was made between the previous export and the current export (for example, a change to coverage information):

If no change was made between the previous export and the current export:

The previous export files used during the comparison are stored in the following directory:

exlibris/sfx_ver/sfx4_1/<sfx_instance>/dbs/scratch/e_collection_update

(Optional) In the Specify export file prefix field, specify a prefix to be added to the export file. This is an optional feature that makes it easier to find the export file later.

A prefix can also be used to distinguish partial exports (for example, using only selective targets) from a complete export.

In the Specify base URL (856 $u) field, specify the base URL of your instance.
In the link text (856 $y) field, specify the link text information to be included for each record in the XML file. Each record of the resulting export file contains an OpenURL and link text in the 856 field.

For example:

<subfield code="u"> http://demo.exlibrisgroup.com:3210/demo?url_ver=Z39.88-2004&ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&rfr_id=info:sid/sfxit.com:opac_856&url_ctx_fmt=info:ofi/fmt:kev:mtx:ctx&sfx.ignore_date_threshold=1&rft.object_id=954925218001&svc_val_fmt=info:ofi/fmt:kev:mtx:sch_svc&svc.fulltext=yes </subfield>

<subfield code="y">SFX linking</subfield>

</datafield>

In the Specify institution info (852 $a) field, specify institution information to be included in the 852 MARC tag for each record (for example, to make it easier to merge different XML).

For example:

<subfield code="a">Science Campus</subfield>

</datafield>

In the Title note information (245 $h) field, specify text to be included in the 245 MARC field (subfield h) of each record in the export file. The text is identical for all records.

For example:

<subfield code="a">Conformal geometry and dynamics</subfield>

<subfield code="h">[electronic content available]</subfield>

</datafield>

To add categories in the <650> MARC field (optional), select the Add categories to the export file check box.

Category information is exported according to the Active mode in the Category Setup tool. Depending on the setup, SFX exports Ex Libris categories, translated categories, or local categories and corresponding assignments.

For example:

<subfield code="a">Arts and Humanities</subfield> <subfield code="x">Education & Careers</subfield>

</datafield>

<subfield code="a">Arts and Humanities</subfield>

<subfield code="x">Performing Arts, Travel and Leisure</subfield>

</datafield>

To add LOCAL attributes in the <901> MARC field (subfield $1), select the Add local attributes to the export file check box.
To include a serviceType restriction in the OpenURL, select the Include service type restriction in 856 URL check box. By default, a service type restriction is included that limits the SFX services in the resulting SFX menu to only those with service types included. To remove this element from the OpenURL, clear the check box.

For example:

<subfield code="y">SFX linking</subfield>

</datafield>

For more information on serviceType restrictions in the OpenURL, see ServiceType Feature.

To include information about all relevant institute settings in the SFX database, select the Include institute information check box.

To create a Verde localization file, select this check box.

To include author information in the SFX database, select the Include author information check box.
To include note and authentication information in the SFX database, select the Include note and authentication information check box. (Only object portfolio information is included, not target or target service.)
To include internal note information in the SFX database, select the Include Internal note information check box. (Only object portfolio information is included, not target or target service.)
To include additional title information in the XML file, select Include alternative titles.
If Chinese titles are included in the export, select Simplified Chinese Title, Traditional Chinese Title, or Both Simplified and Traditional Chinese Titles to include the type of Chinese titles you want in the title field.
Click Submit.

The Export tool identifies active getFullTxt, getSelectedFullTxt, getAbstract, getHolding, and getTOC object portfolios with active targets and target services and reformats the data into XML.

The XML file includes the following information:

Journal title
Abbreviated titles
ISSN
LCCN
Public target name
Thresholds

The following are optional:

Title note
856 MARC fields with OpenURL information and an institution indication (can be used when merging different XML files)
Categories
Local

Also, it is possible to include more information about which institutes have access to each of the journals in the export file.

The XML tags used by the export program refer to standard MARC tags.

The following tags are used:

010 subfield a: LCCN number
008: date in YYMMDD format and language code in ISO 639-2 standard format

The format of the field is: YYMMDDuuuuuuuuuxx-uu-|------u|----|LNG-d

020: ISBNs and eISBNs (repeatable)
022 subfield a: ISSN
030 subfield a: CODEN
090 subfield a: OBJECT number of the journal in the SFX database
100 subfield a: Main Author (personal name)
110 subfield a: Main Author (corporate name)
111 subfield a: Main Author (meeting name)
210 subfield a: abbreviated title information
245 subfield a: journal title
245 subfield h: journal title
246 subfield a: Alternative title

This is the same for all records. It can be added in the Export tool interface.

260 Imprint
- subfield a – Place of publication
- subfield b – Name of publisher
- subfield c – Date of publication

650 Category information (included only if the option to include categories is selected)
- subfield a – category
- subfield x – subcategory
700 subfield a: Additional Author (personal name)
710 subfield a: Additional Author (corporate name)
711 subfield a: Additional Author (meeting name)
776 subfield x: eISSN
852 subfield a: institution indication (same for all records; added in Export tool)
856 subfield u and y: OpenURL and link text
866 subfield a: activation status information
866 subfield b: threshold information in Perl statement format
This subfield is included only in case of:
- local thresholds
- global thresholds for local OPs
866 subfield c: describes type of threshold included in 866 b. Possible values:
- I – institute
- G – global
- L – local
866 subfield i: INSTITUTE for which this 866 record applies
866 subfield j: List of INSTITUTE exceptions if subfield i is DEFAULT
866 subfield s: target service Internal ID
866 subfield t: target Internal ID
866 subfield x: target name and service
866 subfield z: object portfolio Internal ID

866 subfields b, s, t, and z are not intended for end users but may facilitate integration of SFX data with external systems (for example, ejournal databases).

901 subfield a: information stored in the LOCAL field of the objects
945 field: exported only for CJK language objects
- subfield c: original language title (Chinese only; Simplified Chinese)
- subfield m: main title
- subfield s: normalized title used for sorting purposes
  - Chinese titles – Pinyin (China) or stroke sequence (Taiwan)
  - Korean titles – Hangul
  - Japanese titles – Katakana or Hiragana
subfield t: original language title (Traditional Chinese)

The following is an example of a MARC XML output:

<controlfield tag="008">080911uuuuuuuuuxx-uu-|------u|----|eng-d</controlfield>

</datafield>

<subfield code="a">The American economic review</subfield>

</datafield>

</datafield>

<subfield code="a">AMERICAN ECONOMIC REVIEW</subfield>

</datafield>

<subfield code="a">Nashville, Tenn. [etc.]</subfield>

<subfield code="b">American Economic Association.</subfield>

</datafield>

</datafield>

</datafield>

<subfield code="u"> http://demo.exlibrisgroup.com:3210/demo?url_ver=Z39.88-2004&ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&rfr_id=info:sid/

sfxit.com:opac_856&url_ctx_fmt=info:ofi/fmt:kev:mtx:ctx&sfx.ignore_date_threshold=1&rft.object_id=954921334029&svc_val_fmt=info:ofi/fmt:kev:mtx:sch_svc&svc.fulltext=yes& </subfield>

</datafield>

<subfield code="a">Available from 1911 volume: 12 issue: 3.</subfield>

<subfield code="b">$obj->parsedDate(">=",1911,12,3)</subfield>

<subfield code="x">JSTOR Arts and Sciences 1:Full Text</subfield>

</datafield>

<subfield code="a">Business, Economy and Management</subfield>

<subfield code="x">Economics</subfield>

</datafield>

<subfield code="a">Business, Economy and Management</subfield>

<subfield code="x">Finance</subfield>

</datafield>

<subfield code="a">Business, Economy and Management</subfield>

<subfield code="x">General and Others</subfield>

</datafield>

</datafield>

</record>

The name and location of the XML output file is:

exlibris/sfx_ver/sfx4_1/<sfx_instance>/dbs/scratch/e-collection.MMDDYYYYHHMMSS.xml-marc

For example:

exlibris/sfx_ver/sfx4_1/sfx_local/dbs/scratch/e-collection.10312003092008.xml-marc

The following two fields are added to the 866 field of each record in the MARC XML export:

866 Subfields
866 Subfield	Description
866 subfield i	INSTITUTE information
866 subfield j	List of INSTITUTE exceptions if subfield i is the DEFAULT INSTITUTE

(For more information about institutes, refer to the Institute Feature section of the SFX Advanced User's Guide.)

For each institute and each serviceType, a new 866 is included.

For example:

</datafield>

<subfield code="a">The American economic review</subfield>

</datafield>

</datafield>

<subfield code="a">AMERICAN ECONOMIC REVIEW</subfield>

</datafield>

<subfield code="a">Atlanta,</subfield>

<subfield code="b">AHC Media LLC</subfield>

</datafield>

</datafield>

<subfield code="a">Available from 1911 until 2002.</subfield>

<subfield code="b">$obj->parsedDate('>=','1911','undef','undef') && $obj->parsedDate('<=','2002','undef','undef')</subfield>

</datafield>

<subfield code="i">InstA</subfield>

<subfield code="x">JSTOR Arts and Sciences 1:Full Text</subfield>

</datafield>

<subfield code="a">Available from 1950 until 2002.</subfield>

<subfield code="b">$obj->parsedDate('>=','1950','undef','undef') && $obj->parsedDate('<=','2002','undef','undef')</subfield>

<subfield code="i">DEFAULT</subfield>

<subfield code="j">InstB</subfield>

<subfield code="x">JSTOR Arts and Sciences 1:Full Text</subfield>

</datafield>

</record>

The following items are included in the XML file:

Items active for DEFAULT if the activation status of the target, target service, and object portfolio is active and no target institute, target service institute, or object portfolio institute entries exist.

This means that all institutes have access to the journal. The 866 tag includes the DEFAULT institute information in subfield i.

For example:

<subfield code="a">Available from 1950 until 2002.</subfield>

<subfield code="i">DEFAULT</subfield>

<subfield code="x">JSTOR Arts and Sciences 1:Full Text</subfield>

</datafield>

Items active for DEFAULT with institute exceptions if the activation status of the target, target service, and object portfolio is active and inactive target institute, target service institute, or object portfolio institute entries exist.

This means all institutes except the ones listed have access to this journal. The 866 tag includes the DEFAULT institute information in subfield i and lists the inactive institutes in subfield j.

<subfield code="a">Available from 1911 until 2002.</subfield>

<subfield code="b">$obj->parsedDate('>=','1911','undef','undef') && $obj->parsedDate('<=','2002','undef','undef')</subfield>

<subfield code="i">DEFAULT</subfield>

<subfield code="j">InstA,InstB</subfield>

<subfield code="x">JSTOR Arts and Sciences 1:Full Text</subfield>

</datafield>

Items active for INSTITUTE

If a specific item is available for an institute, the 866 tag includes the institute name in subfield i.

For example:

<subfield code="a">Available from 1911 until 2002.</subfield>

<subfield code="b">$obj->parsedDate('>=','1911','undef','undef') && $obj->parsedDate('<=','2002','undef','undef')</subfield>

<subfield code="i">InstA</subfield>

<subfield code="x">JSTOR Arts and Sciences 1:Full Text</subfield>

</datafield>

When you create an export with more than one institute selected, the same target service is active for more than one institute, and none of the institute‑specific activations has an institute‑specific threshold statement, only one 866 tag is included per object portfolio (see example 1 below).

If at least one of the institute‑specific activations has an institute‑specific threshold statement, multiple 866 tags—one for each institute—are included (see example 2 below).

Example 1:

<controlfield tag="008">090924uuuuuuuuuxx-uu-|------u|----|eng-d</controlfield>

<subfield code="a">Abacus</subfield>

</datafield>

<subfield code="b">Blackwell Publishing Limited</subfield>

</datafield>

</datafield>

</datafield>

<subfield code="u">http://il-sfx06:3210/mit?url_ver=Z39.88-2004&ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&rfr_id=info:sid/sfxit.com:opac_856&url_ctx_fmt=info:ofi/fmt:kev:mtx:ctx&sfx.ignore_date_threshold=1&rft.object_id=954921333005&svc_val_fmt=info:ofi/fmt:kev:mtx:sch_svc&svc.fulltext=yes&</subfield>

</datafield>

<subfield code="a">Available from 2000.</subfield>

<subfield code="i">InstA, InstB</subfield>

<subfield code="j">InstC</subfield>

<subfield code="x">EBSCOhost Business Source Premier:Full Text</subfield>

</datafield>

</record>

Example 2:

<controlfield tag="008">090924uuuuuuuuuxx-uu-|------u|----|eng-d</controlfield>

<subfield code="a">Abacus</subfield>

</datafield>

<subfield code="b">Blackwell Publishing Limited</subfield>

</datafield>

</datafield>

</datafield>

</datafield>

</datafield>

</record>

To produce an export file in Aleph sequential format, first follow the steps in Manual Export and then continue with the following steps:

(Optional) In the Specify export file prefix field, specify a prefix to be added to the export file. This is an optional feature that makes it easier to find the export file later.

A prefix can also be used to distinguish partial exports (for example, using only selective targets) from a complete export.

In the Specify base URL (856 $u) field, specify the base URL of your instance.
In the link text (856$y) field, specify the link text information to be included for each record in the XML file. Each record of the resulting export file contains an OpenURL and link text in the 856 field.
To add categories in the <650> MARC field (optional), select the Add categories to the export file check box.

To include a serviceType restriction in the OpenURL, select the Include service type restriction in 856 URL check box. By default, a serviceType restriction is included that limits the SFX services in the resulting SFX menu to only those with serviceTypes included. Clearing the check box removes this element from the OpenURL.

For more information on serviceType restrictions in the OpenURL, see ServiceType Feature.

To include author information in the SFX database, select the Include author information check box.
If Chinese titles are included in the export, select Simplified Chinese Title, Traditional Chinese Title, or Both Simplified and Traditional Chinese Titles to include the type of Chinese titles you want in the title field.
Click Submit.

If more than one institute is selected in the Institute selection box and institute thresholds differ between institutes, multiple 866 MARC tags—one per threshold—are included.

The following is an example of a record in the Aleph sequential format:

000000002 LDR L 00000nas-a22-----z--4500

000000002 008 L 101124s----------------------000---eng-d

000000002 090 L $$a954925377920

000000002 210 L $$aBULL AMER METEOROL SOC

000000002 210 L $$aB AM METEOROL SOC

000000002 210 L $$aB AM METEOR

000000002 210 L $$aAMERICAN METEOROLOGICAL SOCIETY BULLETIN

000000002 210 L $$aBULL AM METEOROL SOC

000000002 210 L $$aBULL. AM. METEOR. SOC

000000002 245 L $$aBulletin of the American Meteorological Society

000000002 260 L $$aEaston, Pa.$$bAmerican Meteorological Society

000000002 022 L $$a0003-0007

000000002 776 L $$x1520-0477

000000002 856 L $$uhttp://demo.exlibrisgroup.com:3210/demo?url_ver=Z39.88-2004&ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&rfr_id=info:sid/sfxit.com:opac_856&url_ctx_fmt=info:ofi/fmt:kev:mtx:ctx&sfx.ignore_date_threshold=1&rft.object_id=954925377920&svc_val_fmt=info:ofi/fmt:kev:mtx:sch_svc&svc.fulltext=yes&$$ySFX linking

000000002 866 L $$aAvailable from 2000. $$b$obj->parsedDate('>=','2000',undef,undef)$$s17770000000000002$$t17770000000000002$$xTest 1:Full Text$$z17770000000000002

000000002 650 L $$aEarth Sciences$$xGeophysics

000000002 650 L $$aEarth Sciences$$xMeteorology

000000002 650 L $$aEnvironmental Sciences$$xAtmospheric Science

000000002 650 L $$aPhysics$$xAtmospheric Physics

KBART Format

To produce an export file in KBART format, first follow the steps in Manual Export and then continue with the following steps:

If Chinese titles are included in the export, select Simplified Chinese Title, Traditional Chinese Title, or Both Simplified and Traditional Chinese Titles to include the type of Chinese titles you want in the title field.
Click Submit.

The export tool creates one or more tab-delimited TXT files, one per target. Then, the set of files is gzipped to create one archive file.

TXT file name format:

<Target public name>[_<institute>]_<Subtarget public name>_<YYYY-MM-DD>.txt

ZIP file name format:

export_kbart_[_<institute>]_YYYYMMDDHHMMSS.zip

To avoid problems with UNIX not handling file names with specific characters, the following characters are removed from target and subtarget names:

\ / , : * ? # " < > | . ! @ # $ % ^ & ( ) + { } [ ] ~ ` ' + = ;

The first row of each tab-delimited TXT file is a header row with KBART standardized field labels. Each publication appears on a separate line, and publications with coverage gaps appear multiple times.

From 2000 until 2003

From 2005 onwards

KBART Format
Column	Description
publication_title	Publication title
print_identifier	Print-format identifier (for example, ISSN, ISBN, etc.)
online_identifier	Online-format identifier (for example, eISSN, eISBN, etc.)
date_first_issue_online	Date of first issue available online
num_first_vol_online	Number of first volume available online
num_first_issue_online	Number of first issue available online
date_last_issue_online	Date of last issue available online (or blank, if coverage is to present)
num_last_vol_online	Number of last volume available online (or blank, if coverage is to present)
num_last_issue_online	Number of last issue available online (or blank, if coverage is to present)
title_url	Title-level URL
first_author	First author (for monographs)
title_id	Title level JKEY
embargo_info	Embargo information. Consists of 3 parts: type – can be: R – available P – not available length (digits) units – can be: D – days M – months Y – years The units field also indicates the granularity of the embargo, that is, how frequently the moving wall moves.
coverage_depth	Coverage depth (SFX service type in parenthesis): fulltext (getFullTxt, getHolding) abstracts (getAbstract, getTOC) selected articles (getSelectedFullTxt)
coverage_notes	Coverage notes
publisher_name	Publisher name (if not given in the file's title)

If the same object has both an active getFullTxt and a getSelectedFullTxt portfolio and both service types have been selected for inclusion in the export, two rows are included in the KBART export, one for each service type.

The following export limitations apply to the KBART format:

If more than one institute is selected in the Export tool Institute drop-down list, there is no indication which institution subscribes to which entry in the KBART file.
Related object information is not included in the KBART file.
The following optional KBART II fields are currently not supported:
- date_monograph_published_print
- date_monograph_published_online
- monograph_volume
- monograph_edition
- first_editor
- parent_publication_id

In the KBART file name, as defined in the KBART standard, an underscore (_) is used to separate SFX targets, subtargets, and institutes. If an SFX target, subtarget, or institute name includes a hyphen (-), it is difficult to differentiate between the different elements in the KBART file name.

PubMed XML LinkOut Format

The PubMed XML LinkOut export option allows the exporting of active data from the SFX database in the LinkOut XML format, as described by PubMed.

The export can then be used as a holdings file to be submitted using the LinkOut Library Submission Utility.

The XML format is described at:

https://www.ncbi.nlm.nih.gov/books/NBK3807/

To produce an export file in PubMed XML format, first follow the steps in Manual Export and then continue with the following steps:

Enter the location of the SFX .gif (URL).
Enter the SFX base URL.
Enter the provider ID.
Enter the URL link text. This should consist of a short phrase that describes the link, such as Link to OpenURL service or Link to SFX.
If Chinese titles are included in the export, select Simplified Chinese Title, Traditional Chinese Title, or Both Simplified and Traditional Chinese Titles to include the type of Chinese titles you want in the title field.
Click Submit.

The following is an example output:

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE LinkSet (View Source for full doctype...)>

<Link>

<IconUrl LNG="EN">http://demo.exlibrisgroup.com:3210/demo/sfx.gif</IconUrl>

<Database>PubMed</Database>

<Query>"0001-8791" [is] AND "last 24 months" [dp]</Query>

<Query>"0001-6314" [is] AND 1998:2010 [dp] NOT "last 1 year" [dp] NOT future [sb]</Query>

<Query>"0001-4575" [is] AND "last 24 months" [dp]</Query>

<Query>"0003-3928" [is] AND "last 24 months" [dp]</Query>

</ObjectList>

</ObjectSelector>

<Base>http://demo.exlibrisgroup.com:3210/demo</Base>

<Rule>?sid=Entrez:PubMed&id=pmid:lo.id</Rule>

</ObjectUrl>

</Link>

</LinkSet>

<Query>"0960-9822" [is] AND 1991/01/01:2030 [dp] NOT "last 12 months" [dp] NOT future[sb]</Query>

After exporting, SFX matches the journals included in the export file against the latest PubMed journal list and removes journals not in PubMed (as per PubMed LinkOut requirements).

The journal list, which is updated daily, is taken from:

ftp://ftp.ncbi.nih.gov/pubmed/J_Medline.txt

If the same journal is available from multiple providers, the threshold statements are merged into one coverage statement. For example, for an object with ISSN 0033-3174:

Portfolio 1 ($obj->parsedDate('>=','1995','57','1'))

Portfolio 2 ($obj->parsedDate('>=','1939','1','1')) && ($obj->timediff('>','2y'))]

The coverage statement in the PubMed export is the following:

The embargo statement is dropped, since there is a portfolio without an embargo.

Google Scholar Format

The Google Scholar export option allows the exporting of active full text data from the SFX database in the export format required for the Google Scholar source. This holdings information, in addition to registration for Google Scholar, are the two requisites for using the Google Scholar source. For more information on the Google Scholar source, refer to the Google Scholar section of the SFX Source Configuration Guide.

Once registration is complete and a set of export files are created, the files are harvested by Google once every week and are used by Google to indicate in the Google Scholar search results when electronic full text is available from the end user's institutional library.

Additionally, the Google Scholar export format can be used by Ex Libris Primo Central and OCLC to retrieve holdings information from SFX. When creating or scheduling the creation of an export file for Primo Central or OCLC, do not compress the export file.

To produce an export file in Google Scholar format, first follow the steps in Manual Export. Make sure you select both Serials and Monographs types of objects (by default, only Serials is selected).

It is recommended to produce the output files in a compressed format. Select the Compress output files check box.

In order for Google to crawl the compressed files, make sure the extension of the Google Scholar holdings files in the registration form ends with .gzip instead of .xml. Access the registration form Services > Google Scholar Registration and edit the URL to Electronic Holdings field.

For example, change:
http://demo.exlibrisgroup.com:3410/demo/cgi/public/get_file.cgi?file=institutional_holding.xml

to:
http://demo.exlibrisgroup.com:3410/demo/cgi/public/get_file.cgi?file=institutional_holding.gzip

To include author information in the SFX database, select the Include author information check box.
If Chinese titles are included in the export, select Simplified Chinese Title, Traditional Chinese Title, or Both Simplified and Traditional Chinese Titles to include the type of Chinese titles you want in the title field.
Click Submit.

If data from a shared instance is used by a local instance (SFX Consortium Model 2), an export must first be run to create a .txt file from the shared instance (restricted to institutes, if appropriate). This must be included in the Use the following additional export file field when exporting in Google Scholar format from the local instance.

SFX creates export files in the export directory of the SFX instance according to the Google Scholar DTD that can be found at: https://scholar.google.com/scholar/institutional_holdings.dtd

SFX creates a full export named institutional_holding.xml and a set of 10 split files:

institutional_holding-.prt01.xml

institutional_holding-.prt02.xml

(…)

institutional_holding-.prt10.xml

The complete file is split as per Google's recommendations to ensure fast data transfer. Note that Google only downloads the 10 split files if they are available and does not download the complete file. However, since other systems (such as Ex Libris Primo or OCLC) rely on the complete file, SFX generates this file as well.

Additionally, if the option to compress files is selected (recommended for faster data transfer), the export directory contains the same files in compressed format (with the .gzip extension):

institutional_holding.gzip

institutional_holding-.prt01.gzip

institutional_holding-.prt02.gzip

(…)

institutional_holding-.prt10.gzip

It is possible to create Google Scholar holdings files with activation information for a specific institute, by selecting an institute from the institute drop-down list (see Manual Export). In this case, a separate set of export files is created, each with the institute name in the export file name.

For example, if an institute is called arts, the file names are the following:

institutional_holding-arts.xml

institutional_holding-arts.prt01.xml

institutional_holding-arts.prt02.xml

(…)

institutional_holding-arts.prt10.xml

If an older version of the Google export files exists in the instance, SFX removes these files before creating a new set of export files.

SFX removes only the files that it will later recreate. If a new set of export files is created with the compression option set to off, SFX removes only the files with the extension .xml. Files with extension .gzip are not automatically removed.

An example with comments can be found at: https://scholar.google.com/scholar/institutional_holdings.xml

The file does not include the name of any of your active target and target services (for example, the provider). It does include coverage information for each of the active portfolios in your instance, but the coverage information is merged, meaning that if the same book or journal is available from two different providers, SFX merges the coverage statements into one summary coverage statement.

Note that blank values for threshold coverage information are ignored when merging coverage information. These blank coverage statements are treated as coverage unknown (not provided by the vendor), not as unlimited or always available.

Note that the Google Scholar file created by SFX also contains the following additional information not documented in the Google Scholar DTD:

Additional tags:
- <eissn> – includes the ISSN of type ELECTRONIC
- <isbn> – repeatable; includes ISBNs of type ELECTRONIC, PRINT_HBK, and PRINT_PBK
- <sfx_id> – includes OBJECT_ID
- <object_type> – values include JOURNAL, BOOK, DISSERTATION, PROCEEDING, CONFERENCE, REPORT, DOCUMENT, SERIES, NEWSPAPER, TRANSCRIPT, DATABASE, WIRE, CD, MANUSCRIPT, VIDEO, AUDIO, SCORE
- <title> – repeatable; includes MAIN and ABBREV titles (up to four total)
- <AuthorList> – includes author information
- <eisbn> – additional ISBNs/eISBNs (repeatable)
Different item type tags according to the service types exported

It is possible to export the following types of services for the Google Scholar format: getFullTxt, getSelectedFullTxt, getHolding, getAbstract, and getTOC.

Depending on the type of service that exists for a particular exported object, a different <item type> tag value is used:

<item type="electronic"> – for getFullTxt and getSelectedFullTxt
<item type="other"> – for getHolding, getTOC, and getAbstract

If both a service of type electronic and of type other exist for one object, two items are created—one with <item type="electronic"> and one with <item type="other">.

In the following example of an output file, the object The Economist has one active getFullTxt portfolio and one active getHolding portfolio:

<institutional_holdings>

<title>The Economist</title>

<from>

</from>

</coverage>

</item>

<title>The Economist</title>

<from>

</from>

<to>

</to>

</coverage>

</item>

Note that it is recommended to schedule a regular generation of the holdings files via the Server Admin Utility in the UNIX file system and to select the Use Compression option. In this way, the library ensures that compressed and up-to-date files of its holdings are available for the Google Scholar crawlers.

For more information on scheduling the Google Scholar export via the Server Admin Utility, refer to the Server Admin Utility section of the SFX System Administration Guide.

CDI Format

To produce an export file in CDI format, first follow the steps in Manual Export and then continue with the following steps.

The following options are specific for this export:

Use this file as additional holdings file in another instance

This option is important in SFX consortia set-ups where activations from another instance (the shared or central instance) are included in a local holdings file (for SFX consortia where consortia API has been set up). Select this option if the export is created in a shared or central instance for use in a local instance where the Use the following additional export file option is selected.

Use production full text holdings when publishing to CDI + Production PC key.

This option is used when publishing to CDI when running or scheduling the CDI export in your SFX test instance. Select this option in the sfxtst41 instance if you want to use the SFX full text activations from the sfxlcl41 instance instead of the full text activations of the sfxtst41 instance. You need to specify the Primo production PC Key.

Full text activations are ignored in the SFX test instance and instead only the search activations and link target activations are published to CDI. For the full text holding file, the SFX production instance activations are used.

It is necessary to open a support case to have this option turned on for the Sandbox PC Key. Make sure to provide the sandbox PC key, the production PC key, and the production holdings URL in the support case to ensure this option can be enabled in the CDI server configuration.

The export consists of a tar.gz file in the following format:

<INST_code>_cdi_institutional_holding.tar.gz

The file is located in a directory such as:

<INST_code>_INST_cdi_institutional_holding

The tar.gz contains the following three files:

CDI Format
File Name	Description
<INST_code>_INST_holding.xml	Contains CDI Title level full text availability
<INST_code>_db_ids.xml	Contains CDI Database level full text availability
<INST_code>_searchable_dbids.xml	Contains CDI Search activations

The CDI Export file created is accessible from the following URL:

http://<SFX_base_URL>/cgi/public/get_file.cgi?file=cdi_institutional_holding.tar.gz

Export File Naming Conventions

Export files have the following file name convention for TXT, MARC XML, and Aleph Sequential files. (File names for HTML, KBART, PubMed XML LinkOut, and Google Scholar have a different format and are documented in their respective sections.)

If no institutes have been defined in the instance:

e-collection-ALL.<timestamp>.<format>

In an instance with at least one institute defined, institute name information is included in the export file name:

e-collection-<institute_name>-<institute_name>.<timestamp>.txt

If all institutes + default activations are included in the export (either no restrictions are selected from the drop-down list or all institutes + default is selected), ALL is used as the institute name.
If not all institutes are selected or the default is selected, all selected institute names (and/or the default, if applicable) are included in the file name.

If the portion of the file name with the institutes is more than 255 characters, the text multiple-institutes is used for the institute name.

See the following tables for some examples:

Export File Naming Conventions
Selected Institutes	File Name
No institute specified in the instance	e-collection-ALL.20150610102044.xml-marc
ALL institutes (InstA+InstB+DEFAULT)	e-collection-ALL.20150610103157.xml-marc
DEFAULT institute	e-collection-default.20150610102556.xml-marc
one institute (InstA)	e-collection-InstA.20150610102807.xml-marc
more than one institute (InstA+InstB)	e-collection-InstA-InstB.20150610102942.xml-marc
more than one institute (InstA+DEFAULT)	e-collection-InstA-default.20150610111507.xml-marc