+++ /dev/null
-<?xml version='1.0' encoding='UTF-8'?>\r
-<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xi="http://www.w3.org/2001/XInclude"\r
- xmlns:xl="http://www.w3.org/1999/xlink" version="5.0" xml:id="Alternate_Serial_Control">\r
- <info>\r
- <title>Alternate Serial Control</title>\r
- <abstract>\r
- <para>\r
- This tutorial describes a basic workflow in which the user will\r
- register a subscription to a serial publication, express the\r
- distribution of copies of that publication to branches, define the\r
- format of captions to be affixed to each issue, specify details of\r
- the publication pattern, instruct the system to predict future\r
- issues, and finally receive copies of an issue. This tutorial is\r
- not intended to represent exhaustive documentation of Evergreen\r
- features relating to serials, as those features are continually\r
- evolving as of this writing, but it should provide a basis on which\r
- user exploration of serials features can take place. Hopefully,\r
- that exploration will initiate feedback that will lead to the\r
- continuing improvement of serials in Evergreen.\r
- </para>\r
- </abstract>\r
- </info> \r
- <simplesect>\r
- <title>Creating a Copy Template</title>\r
- <para>\r
- To create a serial subscription in the Alternate Serial Control\r
- interfaces, you're first going to need a copy template. For many\r
- use cases, you can create one copy template and re-use it all the\r
- time, but if you don't yet have one ready, follow these steps.\r
- </para>\r
- <para>\r
- Find the copy template editor under the Admin menu of the staff\r
- client.\r
- </para>\r
- <screenshot>\r
- <mediaobject>\r
- <imageobject>\r
- <imagedata fileref="../media/find-copy-template-menu.png" />\r
- </imageobject>\r
- </mediaobject>\r
- </screenshot>\r
- <para>Once that page has loaded, click <guibutton>New Template</guibutton>.</para>\r
- <screenshot>\r
- <mediaobject>\r
- <imageobject>\r
- <imagedata fileref="../media/create-copy-template.png" />\r
- </imageobject>\r
- </mediaobject>\r
- </screenshot>\r
- <para>\r
- You don't actually need to fill out all of these fields. If you don't\r
- want serial copies to get barcodes and show up individually in your\r
- catalog, you only need to set the first two fields, which are "owning\r
- library" and "name." Note that "owning library" in this case refers\r
- to the library that owns the copy template itself. This has nothing to\r
- do with what libraries receive copies or what library manages the\r
- subscription. We'll get to that later.\r
- </para>\r
- <para>\r
- If you do want your copies to have barcodes (and perhaps to circulate)\r
- and to appear individually in your catalog, you will need at least to\r
- fill in the fields shown in the above image.\r
- </para>\r
- </simplesect>\r
- <simplesect>\r
- <title>To the Catalog</title>\r
- <para>\r
- Initiate a catalog search in the staff client to find the bibliographic\r
- record to which you'd like to attach a subscription. If you don't\r
- already have the record in your system, you can import it via any of\r
- your preferred methods (MARC import, Z39.50 search, etc.) and then\r
- look it up in the catalog.\r
- </para>\r
- <para>\r
- From the record detail page, click "Actions for this Record," and then\r
- click "Alternate Serial Control." You note that we've used a magazine\r
- called Flying for our example.\r
- </para>\r
- <screenshot>\r
- <mediaobject>\r
- <imageobject>\r
- <imagedata fileref="../media/start-from-catalog.png" />\r
- </imageobject>\r
- </mediaobject>\r
- </screenshot>\r
- </simplesect>\r
- <simplesect>\r
- <title>The Subscription</title>\r
- <para>\r
- Here you'll be presented with an interface that would show you any\r
- existing subscriptions against the bibliographic record you've chosen,\r
- if there were any. More importantly for our purposes, it provides a\r
- "New Subscription" button. Click that.\r
- </para>\r
- <screenshot>\r
- <mediaobject>\r
- <imageobject>\r
- <imagedata fileref="../media/create-sub.png" />\r
- </imageobject>\r
- </mediaobject>\r
- </screenshot>\r
- <para>\r
- The only required fields here are <guilabel>owning library</guilabel> and <guilabel>start date.</guilabel>\r
- You can choose to specify and end date if you have one. <guilabel>Expected date\r
- offset</guilabel> means the difference between the nominal publishing date of any\r
- given issue and the date that you generally expect to receive your copy.\r
- If a publication is dated with the first of each month, but you\r
- generally receive it five days before that, you might enter <quote>-5 days</quote>\r
- into that field.\r
- </para>\r
- <para>\r
- Once you have created this basic subscription, you'll see that it has\r
- an ID number, which is display as a link that you can click. Click\r
- that link to manage the subscription in greater detail.\r
- </para>\r
- <screenshot>\r
- <mediaobject>\r
- <imageobject>\r
- <imagedata fileref="../media/subscription-manage.png" />\r
- </imageobject>\r
- </mediaobject>\r
- </screenshot>\r
- <para>\r
- Now you're looking at the Subscription Details page, which has four\r
- tabs. The first tab, labeled Summary, shows information you've already\r
- seen. Proceed to the next tab, Distributions, to start telling\r
- Evergreen where you want copies of your serial to go.\r
- </para>\r
- </simplesect>\r
- <simplesect>\r
- <title>Distributions</title>\r
- <screenshot>\r
- <mediaobject>\r
- <imageobject>\r
- <imagedata fileref="../media/sub-details.png" />\r
- </imageobject>\r
- </mediaobject>\r
- </screenshot>\r
- <para>\r
- Using the <guibutton>New Distribution</guibutton> button, create a distribution for each\r
- branch for which you expect to receive copies. Each distribution\r
- needs at least a label, a <quote>holding library</quote>, and a <quote>receive unit\r
- template.</quote> <quote>Receive unit template</quote> is where you select the copy\r
- template we created at the beginning of this tutorial. Label can be\r
- anything, and will only appear at receive time. It is not publicly\r
- visible. "Holding library" refers to the library that will get copies.\r
- </para>\r
- <para>\r
- The last two fields have something to do with binding multiple copies\r
- into larger shelving units, but they are currently ignored by the\r
- Alternate Serial Control, which does not support such binding, and you\r
- should leave these fields blank.\r
- </para>\r
- <screenshot>\r
- <mediaobject>\r
- <imageobject>\r
- <imagedata fileref="../media/create-distrib.png" />\r
- </imageobject>\r
- </mediaobject>\r
- </screenshot>\r
- <para>\r
- After saving your distribution (and creating any others for other\r
- libraries for which you will receive items), click on each link in the\r
- Label column to set up the streams for each distribution.\r
- </para>\r
- </simplesect>\r
- <simplesect>\r
- <title>Streams</title>\r
- <para>\r
- <quote>Streams</quote> are perhaps the most confusing concept in the Alternate\r
- Serials Control interfaces, but I'll try to explain them concisely: Each\r
- stream represents one *recurring* copy of a serial. So if you have a\r
- library called Example Branch 1 (BR1 for short), and you want BR1 to\r
- get four copies for every issue, then you should create one\r
- distribution for BR1 and four streams for that distribution.\r
- </para>\r
- <screenshot>\r
- <mediaobject>\r
- <imageobject>\r
- <imagedata fileref="../media/distribs-to-streams.png" />\r
- </imageobject>\r
- </mediaobject>\r
- </screenshot>\r
- <para>\r
- You can create streams one at a time by clicking <guibutton>New Stream</guibutton>. In this\r
- case you have the opportunity to give each stream a routing label. This\r
- routing label only shows up at receive time and on routing lists, and\r
- is not visible in the catalog or anywhere publicly viewable. The\r
- routing label is entirely optional.\r
- </para>\r
- <screenshot>\r
- <mediaobject>\r
- <imageobject>\r
- <imagedata fileref="../media/new-stream.png" />\r
- </imageobject>\r
- </mediaobject>\r
- </screenshot>\r
- <para>\r
- If you don't care about routing labels, or need to create more than\r
- just a couple of steams, use the <guibutton>Create Many Streams</guibutton> button to create\r
- several at once.\r
- </para>\r
- <screenshot>\r
- <mediaobject>\r
- <imageobject>\r
- <imagedata fileref="../media/create-many-streams.png" />\r
- </imageobject>\r
- </mediaobject>\r
- </screenshot>\r
- <para>\r
- If you wish to set up routing lists, use the checkboxes on the left\r
- side of the grid interface to select one stream at a time, and click\r
- <guibutton>Routing List for Selected Stream</guibutton>. If you don't care about routing\r
- lists, you may skip to the Captions and Patterns heading of this\r
- document.\r
- </para>\r
- </simplesect>\r
- <simplesect>\r
- <title>Setting Up Routing Lists</title>\r
- <para>\r
- <emphasis>\r
- As of this writing, routing lists features have been written,\r
- but have not yet been slated for inclusion in a 2.0 series\r
- Evergreen release.\r
- </emphasis>\r
- </para>\r
- <screenshot>\r
- <mediaobject>\r
- <imageobject>\r
- <imagedata fileref="../media/routing-list-manage.png" />\r
- </imageobject>\r
- </mediaobject>\r
- </screenshot>\r
- <para>\r
- A routing list is made up of <guilabel>users</guilabel>, who will presumably get their\r
- hands on a copy of a serial before that copy hits its regular shelving\r
- location. Those users can be either <guilabel>readers</guilabel>, meaning actual\r
- Evergreen users with a barcode, or <guilabel>departments</guilabel>, which can really be\r
- anything and are represented by a free-form text field. There is also\r
- a <guilabel>note</guilabel> field available in either case.\r
- </para>\r
- <screenshot>\r
- <mediaobject>\r
- <imageobject>\r
- <imagedata fileref="../media/routing-list-add.png" />\r
- </imageobject>\r
- </mediaobject>\r
- </screenshot>\r
- <para>\r
- Enter any combination of <guilabel>readers</guilabel> and <guilabel>departments</guilabel> you need using\r
- the supplied fields and the "Add" button. Readers are specified by\r
- their barcodes in the appropriately labeled field.\r
- </para>\r
- <screenshot>\r
- <mediaobject>\r
- <imageobject>\r
- <imagedata fileref="../media/routing-list-drag.png" />\r
- </imageobject>\r
- </mediaobject>\r
- </screenshot>\r
- <para>\r
- You can re-arrange users in the list by dragging and dropping each\r
- numbered row. When you've got the list you want, click <guibutton>Save Changes</guibutton>.\r
- You can remove unwanted users by clicking the <guibutton>[X]</guibutton> link by that\r
- user's list order number.\r
- </para>\r
- </simplesect>\r
- <simplesect>\r
- <title>Captions and Patterns</title>\r
- <para>\r
- After you've set up all the streams you need on all of your\r
- distributions, it's time to move on to the next tab in the Subscription\r
- Details interface: the <guilabel>Captions and Patterns</guilabel> tab.\r
- </para>\r
-\r
- <screenshot>\r
- <mediaobject>\r
- <imageobject>\r
- <imagedata fileref="../media/caption-pattern-tab.png" />\r
- </imageobject>\r
- </mediaobject>\r
- </screenshot>\r
- <para>\r
- Caption and Pattern objects define the same material that would be\r
- described in an 853, 854, or 855 MARC tag. Here you define how your\r
- issues will be captioned and how often you get them.\r
- </para>\r
- <para>\r
- Click the "Add Caption and Pattern" to get a blank row to work with,\r
- and set the leftmost dropdown to Basic, Supplement, or Index, depending\r
- on what you want to define the pattern for. For common periodicals,\r
- Basic is often all that's needed.\r
- </para>\r
- <para>\r
- Next, unless you know how to type a JSON representation of your 85X\r
- tags by hand, click the <guibutton>Wizard</guibutton> button.\r
- </para>\r
- <screenshot>\r
- <mediaobject>\r
- <imageobject>\r
- <imagedata fileref="../media/scap-wiz-page-1.png" />\r
- </imageobject>\r
- </mediaobject>\r
- </screenshot>\r
- <para>\r
- This Caption and Pattern Wizard is where you'll enter information\r
- according to Library of Congress-specified standards about how this\r
- serial works. The first page of the wizard is for specifying\r
- enumeration captions (commonly involving particles labeled <guilabel>v.</guilabel> and\r
- <guilabel>no.</guilabel>).\r
- </para>\r
- <para>\r
- You can have up to six levels of enumeration captions and two\r
- alternate levels. Each level except the first and first alternate\r
- come with attendant questions about how many units of this level\r
- belong to the higher level. This is all directly based on subfields\r
- $a through $h and $u and $v of the MFHD standard.\r
- </para>\r
- <para>\r
- The wizard has several pages, and after you fill out each page the\r
- way you want, click <guibutton>Next</guibutton> in the upper right corner. You can go\r
- back if you've forgotten something by using the <guibutton>Prev</guibutton> button.\r
- </para>\r
- <screenshot>\r
- <mediaobject>\r
- <imageobject>\r
- <imagedata fileref="../media/scap-wiz-page-2.png" />\r
- </imageobject>\r
- </mediaobject>\r
- </screenshot>\r
- <para>\r
- The wizard's second page is concerned with calendar changes (i.e., at\r
- what point on the calendar does the highest level enumeration unit\r
- change). You can add as many of these as you like, and each one can be\r
- one of a) the start of a given month, b) the start of a given season,\r
- or c) a specific date. This all corresponds to subfield $x of the MFHD\r
- standard.\r
- </para>\r
- <screenshot>\r
- <mediaobject>\r
- <imageobject>\r
- <imagedata fileref="../media/scap-wiz-page-3.png" />\r
- </imageobject>\r
- </mediaobject>\r
- </screenshot>\r
- <para>\r
- The wizard's third page is for defining chronology captions. Make sure\r
- that each chronology caption you specify is smaller than the last. Only\r
- mark the <guilabel>Display in Holding Field</guilabel> checkbox if you want the literal\r
- words <quote>year</quote> and <quote>month</quote> and so on to appear next to values like <quote>2010</quote>\r
- and <quote>Nov.</quote>\r
- </para>\r
- <screenshot>\r
- <mediaobject>\r
- <imageobject>\r
- <imagedata fileref="../media/scap-wiz-page-4.png" />\r
- </imageobject>\r
- </mediaobject>\r
- </screenshot>\r
- <para>\r
- The fourth page of the wizard deals with indicator codes and the\r
- subfield $w from the MFHD standard. I recommend setting the first two\r
- dropdowns as shown in the above image, unless you are a serials\r
- librarian who knows your stuff and you have a good reason to do\r
- otherwise. Set your frequency ($w) to the appropriate value for your\r
- publication. For truly irregular frequencies, you may wish to select\r
- <guilabel>use number of issues per year</guilabel>, in which case you enter a raw number\r
- of issues per year.\r
- </para>\r
- <para>\r
- After you have finished the wizard and clicked Compile Pattern Code,"\r
- make sure the <guilabel>Active</guilabel> checkbox is marked for the caption and pattern\r
- object you have just created, and click <guibutton>Save Changes</guibutton>.\r
- </para>\r
- <screenshot>\r
- <mediaobject>\r
- <imageobject>\r
- <imagedata fileref="../media/save-scap.png" />\r
- </imageobject>\r
- </mediaobject>\r
- </screenshot>\r
- </simplesect>\r
- <simplesect>\r
- <title>On to Issuances</title>\r
- <para>\r
- We're finally close to the point where we define an initial issuance\r
- and let Evergreen predict a run of issuances, and attendant items, from\r
- there.\r
- </para>\r
- <para>\r
- Proceed to the Issuances tab of the Subscription Detail interface, and\r
- click on <guibutton>New Issuance</guibutton>.\r
- </para>\r
- <screenshot>\r
- <mediaobject>\r
- <imageobject>\r
- <imagedata fileref="../media/create-iss-1.png" />\r
- </imageobject>\r
- </mediaobject>\r
- </screenshot>\r
- <para>\r
- What we're doing here is hand-entering one example issuance, and you\r
- should use the *last issuance you have before you want prediction to\r
- take over.* So if you want to predict all the issues of a monthly\r
- periodical beginning with November 2010, enter the information for your\r
- October 2010 issue.\r
- </para>\r
- <para>\r
- In the holding code section of the New Issuance dialog, click the \r
- <guibutton>Wizard</guibutton> button to get a fields tailor-made for the caption and pattern\r
- you're using, and fill in the information that's appropriate for the\r
- example issuance you're using. Click <guibutton>Compile</guibutton> when you have all those\r
- fields filled in.\r
- </para>\r
- <screenshot>\r
- <mediaobject>\r
- <imageobject>\r
- <imagedata fileref="../media/create-iss-2.png" />\r
- </imageobject>\r
- </mediaobject>\r
- </screenshot>\r
- <para>\r
- Once everything is filled in on your example issue, click <guibutton>Save</guibutton>. You\r
- have now given the system everything it needs to predict a run of\r
- issues (and the attendant copies that will go to your branches).\r
- </para>\r
- <para>\r
- Click the <guibutton>Generate Predictions</guibutton> button. You'll get a mini-dialog\r
- asking you how many issues to predict. If your subscription has an\r
- end date, you can choose to predict until the subscription's end date.\r
- If your subscription doesn't have an end date, you can indicate how\r
- many issues you want the system to predict (so enter 12 if you want\r
- a year's worth of issues on a monthly publication).\r
- </para>\r
- <screenshot>\r
- <mediaobject>\r
- <imageobject>\r
- <imagedata fileref="../media/predict-how-many.png" />\r
- </imageobject>\r
- </mediaobject>\r
- </screenshot>\r
- <para>\r
- After you click <guibutton>Generate</guibutton>, the system should take a moment to predict\r
- your run of issuances and copies, and then you should see the grid of\r
- issuances populated below.\r
- </para>\r
- <para>\r
- You can now delete the example issuance that we created for the\r
- system to base its prediction on. Mark its checkbox on the left side\r
- of the grid and click<guibutton>Delete Selected</guibutton>.\r
- </para>\r
- <screenshot>\r
- <mediaobject>\r
- <imageobject>\r
- <imagedata fileref="../media/generated-iss-delete-dummy.png" />\r
- </imageobject>\r
- </mediaobject>\r
- </screenshot>\r
- <para>\r
- Your subscription is now completely set up. Let's receive some\r
- copies.\r
- </para>\r
- </simplesect>\r
- <simplesect>\r
- <title>\r
- Batch Receiving\r
- </title>\r
- <para>\r
- The Subscription Details interface has a <guibutton>Batch Item Receive</guibutton> button\r
- that will take you to the Batch Receiving interface for this\r
- subscription.\r
- </para>\r
- <para>\r
- Generally, you won't need to edit anything pertaining to the\r
- subscription itself when receiving items, so you can also get to\r
- Batch Receiving through the <guimenuitem>Actions for this Item</guimenuitem> menu when\r
- viewing a record in the catalog (right next to <guimenuitem>Alternate Serial\r
- Control</guimenuitem> from earlier in this tutorial).\r
- </para>\r
- <screenshot>\r
- <mediaobject>\r
- <imageobject>\r
- <imagedata fileref="../media/batch-receive-choose-iss.png" />\r
- </imageobject>\r
- </mediaobject>\r
- </screenshot>\r
- <para>\r
- The Batch Receiving interface will present you with a selection of\r
- as-yet unreceived issuances. The earliest expected issuance with\r
- any as-yet unreceived copies will always be at the top of the list,\r
- so generally you will click next here.\r
- </para>\r
- <screenshot>\r
- <mediaobject>\r
- <imageobject>\r
- <imagedata fileref="../media/batch-receive-simple.png" />\r
- </imageobject>\r
- </mediaobject>\r
- </screenshot>\r
- <para>\r
- <quote>Simple</quote> mode for Batch Receiving gives you few options - this is\r
- how you receive items that won't have barcodes and won't appear\r
- individually in the catalog. Each item can have a optional note\r
- (stored internally; not displayed anywhere as of this writing, but\r
- not ultimately intended as a publicly-viewable note), and you can\r
- unmark any rows in the table for items that you have not received.\r
- </para>\r
- <para>\r
- More discussion on how to indicate that you haven't received all the\r
- items you were expecting will follow a few paragraphs later in this\r
- tutorial.\r
- </para>\r
- <para>\r
- If you do want to barcode your items, check the <guilabel>Create Units for\r
- Received Items</guilabel> checkbox in the extreme lower right of the\r
- interface.\r
- Units are copy-equivalent objects that will hold a barcode and can\r
- appear in the catalog (and even be targeted for holds). Marking\r
- this checkbox will give you many more fields on each row of the\r
- receiving table.\r
- </para>\r
- <screenshot>\r
- <mediaobject>\r
- <imageobject>\r
- <imagedata fileref="../media/batch-receive-autogen-1.png" />\r
- </imageobject>\r
- </mediaobject>\r
- </screenshot>\r
- <para>\r
- If you have a printed stack of barcodes available, you can scan\r
- each one into the barcode field of each row of the table. You can\r
- also let the system generate your barcodes automatically, if you\r
- so desire. To accomplish this, mark the auto-generate checkbox,\r
- and enter your first barcode into the first row of the table. Then\r
- press the tab key.\r
- </para>\r
- <para>\r
- The rest of the barcode fields will automatically populate with the\r
- next barcodes in sequence, including check digits.\r
- </para>\r
- <screenshot>\r
- <mediaobject>\r
- <imageobject>\r
- <imagedata fileref="../media/batch-receive-autogen-2.png" />\r
- </imageobject>\r
- </mediaobject>\r
- </screenshot>\r
- <para>\r
- As for the other fields in the table besides barcode, you can set\r
- them to whatever values you need. Note that anything with a\r
- barcode must also have a call number, so you'll have to put\r
- something there. Drop-downs for call numbers will be populated\r
- with any existing call-number associated with the bibliographic\r
- record for your serial. You can choose from these call numbers,\r
- or, if perhaps you're using a call-number-per-issue policy, you\r
- can create a new call number to apply to the table of items every\r
- time you receive a batch.\r
- </para>\r
- <para>\r
- To spare you the pain of setting potentially dozens of fields in the\r
- receiving table individually, you can enter a value into the very\r
- top row and click <guibutton>Apply</guibutton> at the far right to apply that same value\r
- to its entire column throughout the table.\r
- </para>\r
- <screenshot>\r
- <mediaobject>\r
- <imageobject>\r
- <imagedata fileref="../media/batch-receive-apply.png" />\r
- </imageobject>\r
- </mediaobject>\r
- </screenshot>\r
- <para>\r
- Now, as for the question of what to do when you didn't receive all\r
- the items you were supposed to get, you can choose what rows in\r
- the table you want to represent the unreceived items. So if you\r
- only received six out of the expected eight, and you're trying to\r
- distribute items evenly between two branches, you might unmark two\r
- checkboxes as shown in the image below.\r
- </para>\r
- <para>\r
- Not only does unmarking the checkbox turn the row grey and prevent\r
- that item from being received when you later click <guibutton>Receive Selected\r
- Items</guibutton> later, but the system also remembers which items you have not\r
- yet received, so that you can receive them later if they arrive\r
- separately. The system's keeping track of unreceived items will\r
- also facilitate a claiming interface, when that is designed and\r
- implemented.\r
- </para>\r
- <screenshot>\r
- <mediaobject>\r
- <imageobject>\r
- <imagedata fileref="../media/batch-receive-partial.png" />\r
- </imageobject>\r
- </mediaobject>\r
- </screenshot>\r
- <para>\r
- When you've filled in all the item rows, look in the lower left of\r
- the interface for the <guibutton>Receive Selected Items</guibutton> button and click\r
- that.\r
- </para>\r
- <screenshot>\r
- <mediaobject>\r
- <imageobject>\r
- <imagedata fileref="../media/batch-receive-receive.png" />\r
- </imageobject>\r
- </mediaobject>\r
- </screenshot>\r
- <para>\r
- You see that the items that were marked for receipt are now cleared\r
- from this interface, as they have been received.\r
- </para>\r
- <screenshot>\r
- <mediaobject>\r
- <imageobject>\r
- <imagedata fileref="../media/batch-receive-received.png" />\r
- </imageobject>\r
- </mediaobject>\r
- </screenshot>\r
- <para>\r
- Since we left all <guilabel>Routing List</guilabel> checkboxes marked, if any of the items\r
- we just received actually have a routing list, we now have another tab\r
- open with a routing list ready to print.\r
- </para>\r
- <screenshot>\r
- <mediaobject>\r
- <imageobject>\r
- <imagedata fileref="../media/batch-receive-print-routing.png" />\r
- </imageobject>\r
- </mediaobject>\r
- </screenshot>\r
- <para>\r
- If you set up a routing list as described earlier in this tutorial,\r
- yours will look like this. Multiple routing lists will automatically\r
- print on separate pages.\r
- </para>\r
- <para>\r
- If you received some items with a barcode (and if the copy template\r
- and shelving location you used are OPAC visible), you can now see the\r
- items you received in the catalog.\r
- </para>\r
- <screenshot>\r
- <mediaobject>\r
- <imageobject>\r
- <imagedata fileref="../media/received-items-in-catalog.png" />\r
- </imageobject>\r
- </mediaobject>\r
- </screenshot>\r
- </simplesect>\r
-</chapter>\r
-\r
projects / Evergreen-DocBook.git / blobdiff