.ole-impex-master.1.5.10.source-code.OLE_PUR_PO_TYP_T.xml Maven / Gradle / Ivy

Go to download
<?xml version="1.0" encoding="UTF-8"?>
<!--  Auto-generated by the Maven Impex Plugin -->
<!DOCTYPE dataset SYSTEM "data.dtd">
<dataset>
    <OLE_PUR_PO_TYP_T OLE_PO_TYPE_ID="1.0" OLE_PO_TYPE="Firm, Fixed" VER_NBR="1.0" OBJ_ID="OLE1" ROW_ACT_IND="Y" DESC_TXT="Firm orders are commitments from a library to purchase a quantity of a title from a provider.  Once all quantities are resolved on a firm order (received &amp; paid for, or cancelled) the order is considered complete and that no further relationship continues with a provider with regards to that firm order." />
    <OLE_PUR_PO_TYP_T OLE_PO_TYPE_ID="2.0" OLE_PO_TYPE="Standing" VER_NBR="1.0" OBJ_ID="OLE2" ROW_ACT_IND="Y" DESC_TXT="Standing orders are commitments from a library to purchase titles published over time, e.g., a series.  A standing order is an order where it is not known what all the titles in the series are going to be.  Each title comes as it is published and it is then that the library describes it, receives it, and pays for it.  Unless discontinued, a standing order will be modified by year-end so that it continues against a new fiscal year.  Unlike subscriptions, standing orders are continued as opposed to being renewed." />
    <OLE_PUR_PO_TYP_T OLE_PO_TYPE_ID="3.0" OLE_PO_TYPE="Subscription" VER_NBR="1.0" OBJ_ID="OLE3" ROW_ACT_IND="Y" DESC_TXT="Subscription orders are commitments from a library to purchase a run [subscription] of a title from a provider.  A subscription order can be for a package of titles, often when the titles are e-journals.  Subscriptions last for a given term (most common being one year), and are renewed to continue the relationship with a provider." />
    <OLE_PUR_PO_TYP_T OLE_PO_TYPE_ID="4.0" OLE_PO_TYPE="Membership" VER_NBR="1.0" OBJ_ID="OLE4" ROW_ACT_IND="Y" DESC_TXT="Membership orders are commitments from a library to purchase a subscription to a membership from a provider.  Having a membership may give a library permission to order materials from the provider or might cause the provider to periodically send materials to the library. Generally, memberships are renewed to continue the relationship with a provider." />
    <OLE_PUR_PO_TYP_T OLE_PO_TYPE_ID="5.0" OLE_PO_TYPE="Approval" VER_NBR="1.0" OBJ_ID="OLE5" ROW_ACT_IND="Y" DESC_TXT="Approval orders are tentative commitments from a library to purchase titles from a provider; approval orders generally come from a provider with whom the library has established an approval plan (automatic shipment of materials based on a librarys acquisitions profile).  Once approved and quantities are resolved (received &amp; paid) the approval order is considered complete and no further relationship continues with the provider with regards to that approval order. In this respect, an approval order resembles a firm order.  If the provider provides records for titles sent on approval, the orders created through an ingest would be set to order type=approval." />
    <OLE_PUR_PO_TYP_T OLE_PO_TYPE_ID="7.0" OLE_PO_TYPE="Blanket" VER_NBR="7.0" OBJ_ID="OLE7" ROW_ACT_IND="Y" DESC_TXT="Blanket orders are commitments from a library to purchase (sometimes after approval) all titles from a provider that fit within a predestinated profile (Author, subject, publisher, etc.)  The titles to be sent from the provider are not known until they are received at the library.  The library processes each title as it is sent from the provider by describing it, receiving it, and invoicing it.  Unless discontinued, a blanket order will be modified by year-end so that they continue against a new fiscal year.  Unlike subscriptions, blanket orders are continued as opposed to being renewed." />
    <OLE_PUR_PO_TYP_T OLE_PO_TYPE_ID="8.0" OLE_PO_TYPE="Integrating resource" VER_NBR="8.0" OBJ_ID="OLE8" ROW_ACT_IND="Y" DESC_TXT="These are similar to subscriptions, except that each new piece supersedes or replaces a previous one.  A common example is legal publications, in which each section of a work is periodically reissued as laws change, and the previous version of that section discarded." />
    <OLE_PUR_PO_TYP_T OLE_PO_TYPE_ID="9.0" OLE_PO_TYPE="Continuing" VER_NBR="1.0" OBJ_ID="OLE9" ROW_ACT_IND="Y" DESC_TXT="Continuing assumes Serials Receiving will be used, and doesn't invoke any claiming cycle based on line item receiving." />
</dataset>