Thanks to Remko, Camille, and Thomas for your suggestions. I have since
modified SectionA and SectionB accordinly; Chapter is still the same as
before.
I am still getting the following errors:
------
Element include in namespace 'http://www.w3.org/2001/XInclude'
encountered in chapter, but no template matches.
Element include in namespace 'http://www.w3.org/2001/XInclude'
encountered in chapter, but no template matches.
Writing index.html for chapter
-------
What else am I still missing? Suggestions are welcome.
Betty
<?xml version="1.0" encoding="utf-8"?>
<chapter version="5.0" xmlns="http://docbook.org/ns/docbook"
xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns:xlink="http://www.w3.org/1999/xlink">
<title>This chapter is a compilation of a use case for the Syrup E-Reserve System based on the scenario The Syrup Physical-Item Story.</title>
<xi:include href="SectionA.xml"
xmlns:xi="http://www.w3.org/2001/XInclude" />
<xi:include href="SectionB.xml"
xmlns:xi="http://www.w3.org/2001/XInclude" />
</chapter><?xml version="1.0" encoding="utf-8"?>
<section version="5.0" xmlns="http://docbook.org/ns/docbook"
xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns:xlink="http://www.w3.org/1999/xlink">
<section>
<title>Adding a Reserve</title>
<para>To add a reserve, do the following:</para>
<para>
???Where does the professor enter the semester, for example, Fall 2009??? How about the course name and course number??? Is it on the MyCourse screen???
</para>
<orderedlist>
<listitem>
<para>On the Syrup E-Reserve System screen, click the <guilabel>Add a Reserve</guilabel>tab.</para>
</listitem>
<listitem>
<para>On the Add a Reserve screen, in the <userinput>Search Terms</userinput> box, type in some key words, and click the <guibutton>Query</guibutton> button.</para>
<example>
<title>Example of some key words</title>
<para>Moby Dick</para>
</example>
</listitem>
<listitem>
<para>Matches are presented in groups of ten. Choose the best match from all the possible matches.</para>
</listitem>
</orderedlist>
<para>
???Is the book "on reserve" at this point?
</para>
<section>
<title>Behind the scenes of Adding a Reserve:</title>
<orderedlist>
<listitem>
<para>Syrup stores the relevant portions of the MARC record in the Syrup item.</para>
</listitem>
<listitem>
<para>Syrup gathers all the physical-item requests for the term.</para>
</listitem>
<listitem>
<para>Syrup sends the requests, a list of MARC extracts, to Circulation.</para>
<para>
???Are MARC extracts the same as the Syrup item, relevant portions of the MARC record??? If so, we should standarize on one term.
</para>
</listitem>
<listitem>
<para>Circulation reads the requests and routes the corresponding items to Reserves.</para>
</listitem>
<listitem>
<para>Circulation possibly activates short-term loan fees before sending items to Reserves.</para>
</listitem>
</orderedlist>
<para>
???Are short-term loan fees actually fines???
</para>
</section>
</section>
<?xml version="1.0" encoding="utf-8"?>
<section version="5.0" xmlns="http://docbook.org/ns/docbook"
xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns:xlink="http://www.w3.org/1999/xlink">
<section>
<title>Subsequent Tasks after a Reserve Request:</title>
<orderedlist>
<listitem>
<para>Syrup stores the relevant portions of the MARC record in the Syrup
item.</para>
</listitem>
<listitem>
<para>Syrup gathers all the physical-item requests for the term.</para>
</listitem>
<listitem>
<para>Syrup sends the requests, a list of MARC extracts, to
Circulation.</para>
</listitem>
<para>
???Are MARC extracts the same as the Syrup item, relevant portions of the MARC record??? If so, we should standarize on one term.
</para>
<para>
???Are the Syrup items configurable???
</para>
<listitem>
<para>Circulation reads the requests and routes the corresponding items
to Reserves.</para>
</listitem>
<listitem>
<para>Circulation possibly activates short-term loan fees before sending
items to Reserves.</para>
</listitem>
</orderedlist>
<para>
???Are short-term loan fees actually fines???
</para>
</section>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]