RDA updates

[sitka/doc/policy.git] / policy / policy-circulation.xml

<?xml version="1.0" encoding="utf-8"?>\r
<chapter xml:id="circulation" xmlns="http://docbook.org/ns/docbook" version="5.0" xml:lang="EN"\r
    xmlns:xi="http://www.w3.org/2001/XInclude" xmlns:xlink="http://www.w3.org/1999/xlink">\r
\r
    <info>\r
        <title>Circulation Policies</title>\r
    </info>\r
\r
    <xi:include href="policy-circ-bcone.xml"/>\r
\r
    <section>\r
        <info>\r
\r
            <title>Hold/Search Policy (Interim)</title>\r
\r
        </info>\r
\r
        <para><emphasis role="bold">Approved by the Interim Board of Directors, BC Libraries\r
                Cooperative <?linebreak?>Wednesday, April 15, 2009</emphasis></para>\r
\r
\r
        <para>In the Interim, while Federation based policy is in development, patron opac searches\r
            will scope only to their home library/library system by default, unless member libraries\r
            specify otherwise. Patron-initiated holds will be filled first by the home\r
            library/library system and then by other Sitka libraries, where agreements exist (e.g.\r
            Federation, reciprocal borrowing or service agreements); By default, holds placed on\r
            another library's material will be held at the owning library for pickup unless and\r
            until a delivery mechanism exists under the relevant agreement. Where agreements do not\r
            exist between Sitka libraries, and between Sitka libraries and non-Sitka libraries,\r
            traditional ILL should be used (Outlook)</para>\r
    </section>\r
\r
    <section>\r
        <info>\r
            <title>Fines Payment</title>\r
\r
        </info>\r
\r
        <para><emphasis role="bold">September 2008</emphasis></para>\r
\r
        <para>In the interim, Sitka sites do not accept payment of fines owed at other Sitka sites.\r
            To be reviewed pending availability of online payment functionality and/or direction\r
            from the BC Libraries Cooperative.</para>\r
    </section>\r
\r
    <section>\r
        <info>\r
            <title>Return of Items</title>\r
\r
        </info>\r
\r
        <para><emphasis role="bold">September 2008</emphasis></para>\r
\r
        <para>In the interim, Sitka sites will check in items to show in transit for all items en\r
            route to another Sitka site.</para>\r
    </section>\r
\r
    <section>\r
        <info>\r
            <title>Patron de-duplication</title>\r
\r
        </info>\r
\r
        <para>Sitka's Evergreen instance is intended to feature a shared patron database both to\r
            facilitate customer service across multiple libraries (a seamless library experience)\r
            and to promote database integrity. To achieve this objective, it is important that each\r
            Sitka patron be represented in the shared database by only one patron record - the\r
            "Master Patron Record."</para>\r
\r
        <para>A "Master Patron Record" incorporates all active transactions on a patron record at\r
            the time a library is migrating onto Sitka's database, and where possible, it also\r
            defines any existing relationships a patron has with other Sitka libraries.</para>\r
\r
        <orderedlist>\r
            <title>Operational Procedures:</title>\r
            <listitem>\r
                <para>During migration, the Sitka team will only de-duplicate those patron records\r
                    that appear with an identical barcode at two or more libraries</para>\r
            </listitem>\r
\r
            <listitem>\r
                <para>In determining which of two or more duplicate records in (1.) should be the\r
                    "Master Patron Record," the Team will use the record belonging to the library\r
                    showing the most recent circulations to that patron.</para>\r
            </listitem>\r
\r
            <listitem>\r
                <para>For all other duplicate patron records (those with different barcodes\r
                    appearing at two or more Sitka libraries), further refinement to a patron's\r
                    record will be managed by library staff in the Evergreen client using the Merge\r
                    Patrons function on the patron search screen, along with the Patron Deletion\r
                    tool.</para>\r
            </listitem>\r
        </orderedlist>\r
    </section>\r
\r
\r
</chapter>\r