Tech Blog

EOD (Embedded Order Data) with multiple funds for a New Order Import Profile

In this post we will discuss using an EOD input file which

  1. Corresponds to field / subfield mapping in the “New Order Import Profile
  2. Includes multiple funds

First a quick short comment for those who do not want to read the full blog:

In order to define multiple funds in an EOD file define in the import profile define the “fund distribution field” and subfield,  and the “percent subfield”.

Below we define list price in 960 subfield s, Fund distribution field in 960 subfield u and fund percent in subfield: v

Then we put them in the input file as follows, where FUND A pays 10% and FUND B pays 90%.

</marc:datafield>
  <marc:datafield tag="960" ind1=" " ind2=" ">
  <marc:subfield code="s">100.00</marc:subfield>
  <marc:subfield code="u">FUND A</marc:subfield>
  <marc:subfield code="v">10</marc:subfield>
  <marc:subfield code="u">FUND B</marc:subfield>
  <marc:subfield code="v">90</marc:subfield>
</marc:datafield>

The POL gets created with two funds: FUND A pays 10% and FUND B pays 90%.

Now the full blog:

In our case we have an import profile of type “New Order” called “Coutts order new books”.

This import profile is based on but not identical to the import profile of the same name which has been contributed to the community zone.

Because we are focusing on the EOD input file will look at the “PO Line Information” tab of the import profile.

This is what we have defined in the “PO Line Information” tab

  • Vendor Reference Number field: 947 subfield: y
  • Vendor Reference Number type field: 947 subfield: z
  • List price field: 960 subfield: s
  • Default PO Line owner: Main Library
  • Fund distribution field: 960 subfield u ; Fund Percent subfield: v
  • Reporting code field: 960 subfield r
  • Interested users field: 960 subfield i
  • Note field: 960 subfield: n
  • Receiving note field: 947 subfield: x

The full input file (MARC XML with one record) is as follows:

<?xml version="1.0" encoding="UTF-8" ?>
<marc:collection xmlns:marc="http://www.loc.gov/MARC21/slim" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd">
  <marc:record>
    <marc:leader>01140nam a2200289   4500</marc:leader>
    <marc:controlfield tag="001">613</marc:controlfield>
    <marc:controlfield tag="008">190306s2008    xx a     b    001 0 eng d</marc:controlfield>
    <marc:datafield tag="020" ind1=" " ind2=" ">
      <marc:subfield code="a">978201903111110</marc:subfield>
    </marc:datafield>
    <marc:datafield tag="050" ind1="0" ind2="4">
      <marc:subfield code="a">YLK 613</marc:subfield>
      <marc:subfield code="2">22</marc:subfield>
    </marc:datafield>
    <marc:datafield tag="100" ind1="1" ind2=" ">
      <marc:subfield code="a">Kortick, Yoel</marc:subfield>
      <marc:subfield code="d">1971-</marc:subfield>
    </marc:datafield>
    <marc:datafield tag="245" ind1="1" ind2="4">
      <marc:subfield code="a">Libraries and information centers in the world of APIs</marc:subfield>
      <marc:subfield code="c">by Yoel Kortick with introduction by Roger Jette</marc:subfield>
    </marc:datafield>
    <marc:datafield tag="260" ind1=" " ind2=" ">
      <marc:subfield code="a">Dimona :</marc:subfield>
      <marc:subfield code="b">Dimona Press ;</marc:subfield>
      <marc:subfield code="c">2019.</marc:subfield>
    </marc:datafield>
    <marc:datafield tag="300" ind1=" " ind2=" ">
      <marc:subfield code="a">xiv, 133 p. </marc:subfield>
    </marc:datafield>
    <marc:datafield tag="504" ind1=" " ind2=" ">
      <marc:subfield code="a">Includes bibliographical references and index.</marc:subfield>
    </marc:datafield>
    <marc:datafield tag="650" ind1=" " ind2="0">
      <marc:subfield code="a">Library science</marc:subfield>
    </marc:datafield>
    <marc:datafield tag="650" ind1=" " ind2="0">
      <marc:subfield code="a">Information science</marc:subfield>
    </marc:datafield>
    <marc:datafield tag="650" ind1=" " ind2="0">
      <marc:subfield code="a">Application program interfaces (Computer software)</marc:subfield>
    </marc:datafield>
    <marc:datafield tag="700" ind1="1" ind2=" ">
      <marc:subfield code="a">Jette, Roger</marc:subfield>
    </marc:datafield>
      <marc:datafield tag="960" ind1=" " ind2=" ">
      <marc:subfield code="s">100.00</marc:subfield>
      <marc:subfield code="u">LEDGER1001-40-10</marc:subfield>
      <marc:subfield code="v">10</marc:subfield>
      <marc:subfield code="u">LEDGER1008-40-10</marc:subfield>
      <marc:subfield code="v">90</marc:subfield>
    </marc:datafield>
  </marc:record>
</marc:collection>

The relevant part of the input file is as follows.

It states that the price is 100.00

  • The first fund is         LEDGER1001-40-10         and it uses 10 % of the total price (code “LEDGER1001-40-10” is  “Sociology E-resources”
  • The second fund is   LEDGER1008-40-10        and it uses 90 % of the total prices (code “LEDGER1008-40-10 is “Public Health and Preventive Medicine E-resources” is “Public Health and Preventive Medicine E-resources”

The relevant fields are

  • Default PO Line owner: Main Library
  • Fund distribution field: 960 subfield u ; Fund Percent subfield: v

</marc:datafield>
  <marc:datafield tag="960" ind1=" " ind2=" ">
  <marc:subfield code="s">100.00</marc:subfield>
  <marc:subfield code="u">LEDGER1001-40-10</marc:subfield>
  <marc:subfield code="v">10</marc:subfield>
  <marc:subfield code="u">LEDGER1008-40-10</marc:subfield>
  <marc:subfield code="v">90</marc:subfield>
</marc:datafield>

The file is imported and now we will look at it

We see exactly as defined in the input file::

  • Public Health and Preventive Medicine E-resources (90.0%) (01/01/2019 – 31/12/2019)
  • Sociology E-resources (10.0%) (01/01/2019 – 31/12/2019)

Leave a Reply