<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="serials_GPLS">\r
<title>The Serials Module</title>\r
-<simpara>This documentation is intended for users who will be ordering subscriptions, distributing issues, and receiving issues in Evergreen . 0. Specifically, this tutorial documents the functionality in the serials module and illustrates a basic serials workflow in which the user will register a subscription to a serial publication; distribute issues of that publication to branches; define the captions to be affixed to each issue; specify details of the publication pattern; predict future issues, and receive copies of an issue. Claiming serials is not available in . 0. This document also includes a list of administrative permissions that users must have to use the serials module.</simpara>\r
+<simpara>This documentation is intended for users who will be ordering\r
+subscriptions, distributing issues, and receiving issues. Specifically, this\r
+tutorial documents the functionality in the serials module and illustrates a\r
+basic serials workflow in which the user will register a subscription to a\r
+serial publication; distribute issues of that publication to branches; define\r
+the captions to be affixed to each issue; specify details of the publication\r
+pattern; predict future issues, and receive copies of an issue. This document also \r
+includes a list of administrative permissions that users must have to use the serials module.</simpara>\r
\r
-<section id="_serial_control_view_alternate_serial_control_view_and_mfhd_records_a_summary">\r
- <title>Serial Control View, Alternate Serial Control View, and MFHD Records: A Summary</title>\r
- <simpara>Serial Control View and Alternate Serial Control View offer you two views of Serials. Both views enable you to create subscriptions, \r
- add distributions, define captions, predict future issues, and receive items. Serial Control View was designed for users who work with a \r
- smaller number of issues and was designed to accommodate workflows in academic and special libraries. Alternate Serial Control View was \r
- designed for users who receive a larger number of issues and was designed for use in public libraries.</simpara>\r
- <simpara>The views are interoperable, but because the views were designed for different purposes, some differences emerge. For example, \r
- Serial Control View enables you to create and edit serials in a single tabbed interface while Alternate Serial Control View leads you through \r
- a series of steps on multiple screens. In addition, receiving functions vary between views. Both receiving interfaces enable you to \r
- batch receive issues. However, the Serials Batch Receive interface, which is associated with Alternate Serial Control View, allows for \r
- more customization of each receiving unit while the Items tab in Serial Control View allows for greater flexibility in creating multi-issue \r
- units, such as in binding serials.</simpara>\r
- <simpara>MFHD records that you created in . 6 will also exist in . 0. Pre-existing MFHD records will display above the holdings summary \r
- for serials created in Alternate Serial Control View. See simplesect . . 2 for an example of this display. If you create a serial in \r
- Serial Control View, the generated holdings and the previous MFHD record will display in a single holdings summary, separated by a comma. \r
- You can also create new MFHD records manually.</simpara>\r
+<section\r
+id="_serial_control_view_alternate_serial_control_view_and_mfhd_records_a_summary">\r
+<title>Serial Control View, Alternate Serial Control View, and MFHD Records: A\r
+Summary</title> \r
+<simpara>Serial Control View and Alternate Serial Control View\r
+offer you two views of Serials. Both views enable you to create subscriptions,\r
+add distributions, define captions, predict future issues, and receive items.\r
+Serial Control View was designed for users who work with a smaller number of\r
+issues and was designed to accommodate workflows in academic and special\r
+libraries. Alternate Serial Control View was designed for users who receive a\r
+larger number of issues and was designed for use in public libraries.</simpara>\r
+\r
+<simpara>The views are interoperable, but because the views were designed for\r
+different purposes, some differences emerge. For example, Serial Control View\r
+enables you to create and edit serials in a single tabbed interface while\r
+Alternate Serial Control View leads you through a series of steps on multiple\r
+screens. In addition, receiving functions vary between views. Both receiving\r
+interfaces enable you to batch receive issues. However, the Serials Batch\r
+Receive interface, which is associated with Alternate Serial Control View,\r
+allows for more customization of each receiving unit while the Items tab in\r
+Serial Control View allows for greater flexibility in creating multi-issue\r
+units, such as in binding serials.</simpara> \r
+\r
+ <simpara> \r
+ Pre-existing MFHD records will display above the holdings summary for \r
+ serials created in Alternate Serial Control View. If you create a serial \r
+ in Serial Control View, the generated holdings and the previous MFHD \r
+ record will display in a single holdings summary, separated by a comma. \r
+ You can also create new MFHD records manually.</simpara> \r
</section>\r
\r
<section id="_copy_templates_for_serials">\r
<title>Copy Templates for Serials</title>\r
- <simpara>A copy template enables you to specify item attributes that should be applied by default to copies of serials. You can create one \r
- copy template and apply it to multiple serials. You can also create multiple copy templates. Templates will be used in the Alternate \r
+ <simpara>A copy template enables you to specify item attributes that \r
+ should be applied by default to copies of serials. You can create one \r
+ copy template and apply it to multiple serials. You can also create \r
+ multiple copy templates. Templates will be used in the Alternate \r
Serial Control View or the Serial Control View.</simpara>\r
<simplesect>\r
<title>Create a copy template</title>\r
<procedure>\r
<step>\r
<simpara>\r
- To create a copy template, click Admin → Local Administration → Copy Template Editor.\r
+ To create a copy template, click Admin → Local Administration \r
+ → Copy Template Editor.\r
</simpara>\r
</step>\r
<step>\r
</step>\r
<step>\r
<simpara>\r
- Select an owning library from the Owning lib drop down menu. This organization owns the copy template. A staff member \r
- with permissions at that organization can modify the copy template. The menu is populated from the organizations that you created in \r
+ Select an owning library from the Owning lib drop down menu. \r
+ This organization owns the copy template. A staff member \r
+ with permissions at that organization can modify the copy template. \r
+ The menu is populated from the organizations that you created in \r
Admin → Server Administration → Organizational Units.\r
</simpara>\r
</step>\r
</step>\r
<step>\r
<simpara>\r
- Check the box adjacent to OPAC Visible? if you want patrons to be able to see the item in the OPAC after you receive it.\r
+ Check the box adjacent to OPAC Visible? if you want patrons to be able to see \r
+ the item in the OPAC after you receive it.\r
</simpara>\r
</step>\r
<step>\r
</step>\r
<step>\r
<simpara>\r
- Select a copy Location from the drop down menu. The menu is populated from the copy locations that you created in Admin → \r
- Local Administration → Copy Locations.\r
+ Select a copy Location from the drop down menu. The menu is populated from the \r
+ copy locations that you created in Admin → Local Administration → \r
+ Copy Locations.\r
</simpara>\r
</step>\r
<step>\r
<simpara>\r
- Select a circ modifier from the drop down box. The menu is populated from the modifiers that you created in Admin → Server \r
- Administration → Circulation Modifiers.\r
+ Select a circ modifier from the drop down box. The menu is populated from the \r
+ modifiers that you created in Admin → Server Administration → \r
+ Circulation Modifiers.\r
</simpara>\r
</step>\r
<step>\r
</step>\r
<step>\r
<simpara>\r
- Check the box adjacent to Deposit? if patrons must place a deposit on the copy before they can use it.\r
+ Check the box adjacent to Deposit? if patrons must place a deposit on the copy \r
+ before they can use it.\r
</simpara>\r
</step>\r
<step>\r
</step>\r
<step>\r
<simpara>\r
- Enter age protection rules in the Age Protect field. Age protection allows you to control the extent to which an item can circulate \r
- after it has been received. For example, you may want to protect new copies of a serial so that only patrons who check out the item \r
- at your branch can use it.\r
+ Enter age protection rules in the Age Protect field. Age protection allows you \r
+ to control the extent to which an item can circulate after it has been received. \r
+ For example, you may want to protect new copies of a serial so that only patrons \r
+ who check out the item at your branch can use it.\r
</simpara>\r
</step>\r
<step>\r
<simpara>\r
- Enter a message in the Alert Message field. This message will appear every time the item is checked out to a patron.\r
+ Enter a message in the Alert Message field. This message will appear every time the \r
+ item is checked out to a patron.\r
</simpara>\r
</step>\r
<step>\r
<simpara>\r
- Enter a code from the MARC fixed fields if you want to control the circulation based on the item type in the Circ as Type field.\r
+ Enter a code from the MARC fixed fields if you want to control the circulation based \r
+ on the item type in the Circ as Type field.\r
</simpara>\r
</step>\r
<step>\r
</step>\r
<step>\r
<simpara>\r
- Enter the ID of the copy status in the Status field. A list of copy statuses and their IDs can be found in Admin → Server \r
- Administration → Copy Status.\r
+ Enter the ID of the copy status in the Status field. A list of copy statuses and their IDs \r
+ can be found in Admin → Server Administration → Copy Status.\r
</simpara>\r
</step>\r
<step>\r
</simplesect>\r
<simplesect>\r
<title>Edit a copy template</title>\r
- <simpara>You can make changes to an existing copy template. Changes that you make to a copy template will apply to any items that you \r
- receive after you edited the template.</simpara>\r
+ <simpara>You can make changes to an existing copy template. Changes that you make to a \r
+ copy template will apply to any items that you receive after you edited the template.</simpara>\r
<procedure>\r
<step>\r
<simpara>\r
</simpara>\r
</step>\r
</procedure>\r
- <simpara>From the copy template interface, you can delete copy templates that have never been used.</simpara>\r
+ <simpara>From the copy template interface, you can delete copy templates \r
+ that have never been used.</simpara>\r
</simplesect>\r
</section>\r
\r
<section id="_alternate_serial_control_view">\r
<title>Alternate Serial Control View</title>\r
- <simpara>Using the Alternate Serial Control View, you can create a subscription, a distribution, a stream, and a caption and pattern, \r
- and you can generate predictions and receive issues.\r
- To access Alternate Serial Control View, open a serials record, and click Actions for this Record → Alternate Serial Control. \r
- This opens the Subscriptions interface</simpara>\r
+ <simpara>Using the Alternate Serial Control View, you can create a subscription, \r
+ a distribution, a stream, and a caption and pattern, and you can generate \r
+ predictions and receive issues. To access Alternate Serial Control View, \r
+ open a serials record, and click Actions for this Record → Alternate Serial \r
+ Control. This opens the Subscriptions interface</simpara>\r
<simplesect>\r
<title>Subscriptions</title>\r
<simpara>Add new subscriptions to a serials record that exists in the catalog.</simpara>\r
</step>\r
<step>\r
<simpara>\r
- Select an owning library. The owning library indicates the organizational unit(s) whose staff can use this subscription. This menu \r
- is populated with the shortnames that you created for your libraries in the organizational units tree in Admin → \r
- Server Administration → Organizational Units.\r
- The rule of parental inheritance applies to this list. For example, if a system is made the owner of a subscription, then users, \r
- with appropriate permissions, at the branches within the system could also use this subscription.\r
+ Select an owning library. The owning library indicates the organizational unit(s) \r
+ whose staff can use this subscription. This menu is populated with the shortnames \r
+ that you created for your libraries in the organizational units tree in Admin → \r
+ Server Administration → Organizational Units. The rule of parental inheritance \r
+ applies to this list. For example, if a system is made the owner of a subscription, \r
+ then users, with appropriate permissions, at the branches within the system could \r
+ also use this subscription.\r
</simpara>\r
</step>\r
<step>\r
<simpara>\r
- Enter the date that the subscription begins in the start date. Recommended practice is that you select the date from the drop down \r
- calendar although you can manually enter a date.\r
- Owning library and start date are required fields in the new subscription pop up box.\r
+ Enter the date that the subscription begins in the start date. Recommended practice \r
+ is that you select the date from the drop down calendar although you can manually enter \r
+ a date. Owning library and start date are required fields in the new subscription pop up box.\r
</simpara>\r
</step>\r
<step>\r
<simpara>\r
- Enter the date that the subscription ends in the end date. Recommended practice is to select a date from the drop down calendar, but \r
- you can manually enter a date, also.\r
+ Enter the date that the subscription ends in the end date. Recommended practice is to \r
+ select a date from the drop down calendar, but you can manually enter a date, also.\r
</simpara>\r
</step>\r
<step>\r
<simpara>\r
- Enter the difference between the nominal publishing date of an issue and the date that you expect to receive your copy in the Expected \r
- Date Offset. For example, if an issue is published the first day of each month, but you receive the copy two days prior to the \r
+ Enter the difference between the nominal publishing date of an issue and the date that you \r
+ expect to receive your copy in the Expected Date Offset. For example, if an issue is \r
+ published the first day of each month, but you receive the copy two days prior to the \r
publication date, then enter -2 days into this field.\r
</simpara>\r
</step>\r
<step>\r
<simpara>\r
After you save the subscription, it will appear in a list with a hyperlinked ID number.\r
- Use the drop down menu at the top of the screen to view subscriptions at other organizations.\r
+ Use the drop down menu at the top of the screen to view subscriptions at other organizations.\r
</simpara>\r
</step>\r
</procedure>\r
</simplesect>\r
<simplesect>\r
<title>Manage a subscription</title>\r
- <simpara>Click the hyperlinked ID number to manage the subscription. The tabbed interface enables you to create distributions, captions \r
- and patterns, and issuances.</simpara>\r
+ <simpara>Click the hyperlinked ID number to manage the subscription. The tabbed interface \r
+ enables you to create distributions, captions and patterns, and issuances.</simpara>\r
</simplesect>\r
<simplesect>\r
<title>Edit a subscription</title>\r
</simplesect>\r
<simplesect>\r
<title>Distributions</title>\r
- <simpara>Distributions indicate the branches that should receive copies of a serial. Distributions work together with streams to indicate \r
- the number of copies that should be sent to each branch.</simpara>\r
+ <simpara>Distributions indicate the branches that should receive copies of a serial. \r
+ Distributions work together with streams to indicate the number of copies that should \r
+ be sent to each branch.</simpara>\r
<simplesect>\r
<title>Create a distribution</title>\r
<procedure>\r
</step>\r
<step>\r
<simpara>\r
- Enter a name for the distribution in the Label field. It may be useful to identify the branch to which you are distributing these \r
- issues in this field. This field is not publicly visible and only appears when an item is received. There are no limits on the number of \r
- characters that can be entered in this field.\r
+ Enter a name for the distribution in the Label field. It may be useful \r
+ to identify the branch to which you are distributing these issues in this \r
+ field. This field is not publicly visible and only appears when an item \r
+ is received. There are no limits on the number of characters that can be \r
+ entered in this field.\r
</simpara>\r
</step>\r
<step>\r
<simpara>\r
- Select a holding library from the drop down menu. The holding library is the branch that will receive the copies.\r
+ Select a holding library from the drop down menu. The holding library is \r
+ the branch that will receive the copies.\r
</simpara>\r
</step>\r
<step>\r
<simpara>\r
- Select a copy template from the Receive Unit Template drop down menu. This menu is populated with the copy templates that you created in \r
- Copy Template Editor.\r
+ Select a copy template from the Receive Unit Template drop down menu. This \r
+ menu is populated with the copy templates that you created in Copy Template Editor.\r
</simpara>\r
- <note><simpara>Label, Holding Library, and Receive Unit Template are required fields in the new distribution pop up box.</simpara></note>\r
+ <note><simpara>Label, Holding Library, and Receive Unit Template are required \r
+ fields in the new distribution pop up box.</simpara></note>\r
</step>\r
<step>\r
<simpara>\r
- Ignore the fields, Unit Label Prefix and Unit Label Suffix. These fields are not functional in Alternate Serial Control View.\r
+ Ignore the fields, Unit Label Prefix and Unit Label Suffix. These fields are not \r
+ functional in Alternate Serial Control View.\r
</simpara>\r
</step>\r
<step>\r
<simpara>\r
- Click Save. The distribution will appear in a list in the Distributions tab in the Subscription Details.\r
+ Click Save. The distribution will appear in a list in the Distributions tab in the \r
+ Subscription Details.\r
</simpara>\r
</step>\r
</procedure>\r
<simplesect>\r
<title>Edit a distribution</title>\r
<simpara>Edit a distribution just as you would edit a copy template.</simpara>\r
- <simpara>From the distribution interface, you can also delete distributions. Deleting the distribution would delete related data, \r
- such as streams associated with this distribution, but it would not delete units, the copy-equivalent objects that hold barcodes. \r
- Recommended practice is that you do not delete distributions.</simpara>\r
+ <simpara>From the distribution interface, you can also delete distributions. \r
+ Deleting the distribution would delete related data, such as streams associated \r
+ with this distribution, but it would not delete units, the copy-equivalent \r
+ objects that hold barcodes. Recommended practice is that you do not delete \r
+ distributions.</simpara>\r
</simplesect>\r
</simplesect>\r
<simplesect>\r
<title>Streams</title>\r
- <simpara>Distributions work together with streams to indicate the number of copies that should be sent to each branch. Distributions \r
- identify the branches that should receive copies of a serial. Streams identify how many copies should be sent to each branch. Streams \r
+ <simpara>Distributions work together with streams to indicate the number of copies that \r
+ should be sent to each branch. Distributions identify the branches that should receive copies \r
+ of a serial. Streams identify how many copies should be sent to each branch. Streams \r
are intended for copies that are received on a recurring, even if irregular, basis.</simpara>\r
- <simpara>In our example, the Apex Branch should receive copies, so we created a distribution to that branch. The Apex Branch should \r
- receive two copies, so we will create two streams to that branch.</simpara>\r
+ <simpara>In our example, the Apex Branch should receive copies, so we created a distribution \r
+ to that branch. The Apex Branch should receive two copies, so we will create two streams \r
+ to that branch.</simpara>\r
<simplesect>\r
<title>Create a stream</title> \r
- <simpara>Click the hyperlinked title of the distribution. The number of streams that have already been created for this distribution \r
- displays adjacent to the title.\r
- You can choose one of two ways to create a stream: New Stream or Create Many Streams. The New Stream button allows you to create one new \r
- stream and assign it a routing label.</simpara>\r
+ <simpara>Click the hyperlinked title of the distribution. The number of streams that have \r
+ already been created for this distribution displays adjacent to the title.\r
+ You can choose one of two ways to create a stream: New Stream or Create Many Streams. \r
+ The New Stream button allows you to create one new stream and assign it a routing label.</simpara>\r
<procedure> \r
<step><simpara>Click New Stream</simpara></step>\r
- <step><simpara>Enter a routing label so that the copy could be read by specific users or departments before the copy is shelved. The routing label appears during receiving and could be added to routing lists; it is not viewable by the public. Routing lists do not print from in 2.0. This field is optional.</simpara></step>\r
+ <step><simpara>Enter a routing label so that the copy could be read by specific users or \r
+ departments before the copy is shelved. The routing label appears during receiving and could be \r
+ added to routing lists; it is not viewable by the public. This field is optional.</simpara></step>\r
<step><simpara>Click Save.</simpara></step>\r
</procedure>\r
- <simpara>The Create Many Streams button allows you to create multiple streams at once, but it does not allow you to add a routing label when you create the stream.</simpara>\r
+ <simpara>The Create Many Streams button allows you to create multiple streams at once, but it does \r
+ not allow you to add a routing label when you create the stream.</simpara>\r
<procedure>\r
<step>\r
<simpara>\r
<simplesect>\r
<title>Edit a stream</title>\r
<simpara>Edit a stream just as you would edit a copy template.</simpara>\r
- <simpara>From the streams interface, you can also delete streams. Deleting the stream would delete related data, but it would not delete units, or the copy-equivalent objects that hold barcodes. Recommended practice is that you do not delete streams.</simpara>\r
+ <simpara>From the streams interface, you can also delete streams. Deleting the stream \r
+ would delete related data, but it would not delete units, or the copy-equivalent objects \r
+ that hold barcodes. Recommended practice is that you do not delete streams.</simpara>\r
</simplesect>\r
</simplesect>\r
<simplesect>\r
<title>Captions and Patterns</title>\r
- <simpara>The Captions and Patterns wizard allows you to enter caption and pattern data as it is described by the 853, 854, and 855 MARC tags. These tags allow you to define how issues will be captioned, and how often the library receives issues of the serial.</simpara>\r
- <simpara>In 2.0, it is not possible to create a caption and pattern and apply it to multiple subscriptions. However, you can re-use patterns if you copy and paste to and from the pattern code field in the Captions and Patterns tab.</simpara>\r
+ <simpara>The Captions and Patterns wizard allows you to enter caption and pattern data as \r
+ it is described by the 853, 854, and 855 MARC tags. These tags allow you to define how \r
+ issues will be captioned, and how often the library receives issues of the serial.</simpara>\r
<simplesect>\r
<title>Create a Caption and Pattern</title>\r
<procedure>\r
</step>\r
<step>\r
<simpara>\r
-In the Pattern Code drop down box, you can enter a JSON representation of the 85X tag by hand, or you can click the Wizard to enter the information in a user-friendly format.\r
+In the Pattern Code drop down box, you can enter a JSON representation of the 85X tag \r
+by hand, or you can click the Wizard to enter the information in a user-friendly format.\r
</simpara>\r
</step>\r
<step>\r
<simpara>\r
-The Caption and Pattern that you create is Active by default, but you can deactivate a caption and pattern at a later time by unchecking the box.\r
+The Caption and Pattern that you create is Active by default, but you can deactivate a \r
+caption and pattern at a later time by unchecking the box.\r
</simpara>\r
</step>\r
</procedure>\r
-<note><simpara>A subscription may have multiple captions and patterns listed in the subscripiton details, but only one Caption and Pattern can be active at any time.\r
+<note><simpara>A subscription may have multiple captions and patterns listed in the subscripiton \r
+details, but only one Caption and Pattern can be active at any time.\r
If you want to add multiple patterns, e.g. for Basic and Supplement, Click Add Caption and Pattern.</simpara></note>\r
</simplesect>\r
<simplesect>\r
<title>Use the Pattern Code Wizard</title>\r
-<simpara>The Pattern Code Wizard enables you to create the caption of the item and add its publication information. The Wizard is composed of five pages of questions. You can use the Next and Previous navigation buttons in the top corners to flip between pages.</simpara>\r
+<simpara>The Pattern Code Wizard enables you to create the caption of the item and add its publication information. \r
+The Wizard is composed of five pages of questions. You can use the Next and Previous navigation buttons in the top corners to flip between pages.</simpara>\r
<procedure>\r
<step>\r
<simpara>\r
</step>\r
<step>\r
<simpara>\r
-Choose a chronology for the first level. If you want to display the terms, “year” and “month” next to the chronology caption in the catlaog, then check the box beneath Display in holding field?\r
+Choose a chronology for the first level. If you want to display the terms, “year” and “month” next to the \r
+chronology caption in the catlaog, then check the box beneath Display in holding field?\r
</simpara>\r
</step>\r
<step>\r
<procedure numeration="loweralpha">\r
<step>\r
<simpara>\r
-Select the appropriate option for compressing or expanding your captions in the catalog from the compressibility and expandability drop down menu. The entries in the drop down menu correspond to the indicator codes and the subfield $w in the 853 tag. Compressibility and expandability correspond to the first indicator in the 853 tag.\r
+Select the appropriate option for compressing or expanding your captions in the catalog from the compressibility and expandability drop down menu. \r
+The entries in the drop down menu correspond to the indicator codes and the subfield $w in the 853 tag. Compressibility and expandability correspond \r
+to the first indicator in the 853 tag.\r
</simpara>\r
</step>\r
<step>\r
</step>\r
<step>\r
<simpara>\r
-Choose the frequency of your publication from the drop down menu. For irregular frequencies, you may wish to select use number of issues per year, and enter the total number of issues that you receive each year. However, in the . 0 release, recommended practice is that you use only regular frequencies. Planned development will create an additional step to aid in the creation of irregular frequencies.\r
+Choose the frequency of your publication from the drop down menu. For irregular frequencies, you may wish to select use number of issues per year, \r
+and enter the total number of issues that you receive each year. \r
+Planned development will create an additional step to aid in the creation of irregular frequencies.\r
</simpara>\r
</step>\r
<step>\r
</step>\r
<step>\r
<simpara>\r
-Enter a name for this issuance in the Label field. There are no limits on the number of characters that can be entered in this field. You may want to enter the month and year of the publication in hand.\r
+Enter a name for this issuance in the Label field. There are no limits on the number of characters that can be entered in this field. \r
+You may want to enter the month and year of the publication in hand.\r
</simpara>\r
</step>\r
<step>\r
<simpara>\r
-Enter the Date Published of the issuance that you are editing. Recommended practice is that you select the date from the drop down calendar although you can manually enter a date. If you are creating one manual issue before automatically predicting more issues, then this date should be the date of the most current issue before the prediction starts.\r
+Enter the Date Published of the issuance that you are editing. Recommended practice is that you select the date from the drop down calendar although \r
+you can manually enter a date. If you are creating one manual issue before automatically predicting more issues, then this date should be the \r
+date of the most current issue before the prediction starts.\r
</simpara>\r
</step>\r
<step>\r
</step>\r
<step>\r
<simpara>\r
-Enter the month of publication in the Month field if applicable. You must enter the calendar number of the month rather than the name of the month. For example, enter 12 if the item in hand was published in December.\r
+Enter the month of publication in the Month field if applicable. You must enter the calendar number of the month rather than the name of the month. \r
+For example, enter 12 if the item in hand was published in December.\r
</simpara>\r
</step>\r
<step>\r
</step>\r
<step>\r
<simpara>\r
-Choose the length of time for which you want to predict issues. If you select the radio button to predict until end of subscription, then Evergreen will predict issues until the end date that you created when you created the subscription. See simplesect . 1 for more information. If you do not have an end date, select the radio button to predict a certain number of issuances, and enter a number in the field.\r
+Choose the length of time for which you want to predict issues. If you select the radio button to predict until end of subscription, then Evergreen will \r
+predict issues until the end date that you created when you created the subscription. See simplesect . 1 for more information. If you do not have an \r
+end date, select the radio button to predict a certain number of issuances, and enter a number in the field.\r
<mediaobject>\r
<alt>\r
<phrase>Generate item predicitions 2</phrase> \r
</simplesect>\r
<simplesect>\r
<title>Receiving</title>\r
-<simpara>You can batch receive items through a simple or an advanced interface. The simple interface does not allow you to add barcodes or use the copy template. These items are also not visible in the OPAC. The advanced interface enables you to use the copy templates that you created, add barcodes, and make items OPAC visible and holdable.</simpara>\r
-<simpara>You can access both Batch Receive interfaces from two locations in the ILS. From the Subscription Details screen, you can click Batch Item Receive. You can also access these interfaces by opening the catalog record for the serial, and clicking Actions for this Record → Serials Batch Receive.</simpara>\r
+<simpara>You can batch receive items through a simple or an advanced interface. The simple interface does not allow you to add barcodes \r
+or use the copy template. These items are also not visible in the OPAC. The advanced interface enables you to use the copy templates \r
+that you created, add barcodes, and make items OPAC visible and holdable.</simpara>\r
+<simpara>You can access both Batch Receive interfaces from two locations in the ILS. From the Subscription Details screen, you can click \r
+Batch Item Receive. You can also access these interfaces by opening the catalog record for the serial, and clicking Actions \r
+for this Record → Serials Batch Receive.</simpara>\r
<simplesect>\r
<title>Simple Batch Receiving</title>\r
<simpara>Follow these steps to receive items in batch in a simple interface.</simpara>\r
</step>\r
<step>\r
<simpara>\r
-In simple mode, the distributions that you created are displayed. They are marked received by default. If you hover over the branch name, you can view the name of the distribution and its stream.\r
+In simple mode, the distributions that you created are displayed. They are marked received by default. If you hover over the branch name, you can view \r
+the name of the distribution and its stream.\r
</simpara>\r
</step>\r
<step>\r
<simpara>\r
-You can receive and add a note to each item individually, or you can perform these actions on all of the distributions and streams at once. To do so, look above the line, and enter the note that you want to apply to all copies and confirm that the box to Receive? is checked.\r
+You can receive and add a note to each item individually, or you can perform these actions on all of the distributions and streams at once. To do so, \r
+look above the line, and enter the note that you want to apply to all copies and confirm that the box to Receive? is checked.\r
</simpara>\r
</step>\r
<step>\r
<simpara>\r
Click Apply. The note should appear in the note field in each distribution.\r
</simpara>\r
-<note><simpara>In 2.0, the note field is only displayed in the current screen.</simpara></note>\r
+<note><simpara>The note field is only displayed in the current screen.</simpara></note>\r
</step>\r
<step>\r
<simpara>\r
</step>\r
<step>\r
<simpara>\r
-If you want to barcode each copy, display it in the catalog, and make it holdable, then check the box adjacent to Create Units for Received Items in the lower right side of the screen.\r
+If you want to barcode each copy, display it in the catalog, and make it holdable, then check the box adjacent to Create Units for Received Items in the lower \r
+right side of the screen.\r
</simpara>\r
</step>\r
<step>\r
<step>\r
<simpara>\r
Barcode – You can scan printed barcodes into the barcode field for each copy, or you can allow the system to auto-generate barcodes.\r
- …To auto-generate barcodes, check the box adjacent to Auto-generate?, and enter the first barcode into the barcode field in the first row of the table. Then press the Tab key. The remaining barcode fields will automatically populate with the next barcodes in sequence, including check digits.\r
+ …To auto-generate barcodes, check the box adjacent to Auto-generate?, and enter the first barcode into the barcode field in the first row of the table. \r
+Then press the Tab key. The remaining barcode fields will automatically populate with the next barcodes in sequence, including check digits.\r
</simpara>\r
</step>\r
<step>\r
<simpara>\r
-Circ Modifiers - The circ modifiers drop down menu is populated with the circulation modifiers that you created in Admin → Server Administration → Circulation Modifiers. If you entered a circ modifier in the copy template that you created for this subscription, then it will appear by default in the distributions.\r
+Circ Modifiers - The circ modifiers drop down menu is populated with the circulation modifiers that you created in Admin → Server Administration → \r
+Circulation Modifiers. If you entered a circ modifier in the copy template that you created for this subscription, then it will appear by default in the distributions.\r
</simpara>\r
</step>\r
<step>\r
</step>\r
<step>\r
<simpara>\r
-Copy Location – The copy location drop down menu is populated with the copy locations that you created in Admin → Local Administration → Copy Location Editor. If you entered a copy location in the copy template that you created for this subscription, then it will appear by default in the distributions.\r
+Copy Location – The copy location drop down menu is populated with the copy locations that you created in Admin → Local Administration → Copy Location \r
+Editor. If you entered a copy location in the copy template that you created for this subscription, then it will appear by default in the distributions.\r
</simpara>\r
</step>\r
<step>\r
<simpara>\r
-Price - If you entered a price in the copy template that you created for this subscription, then it will appear by default in the distributions. You can also manually enter a price if you did not include one in the copy template.\r
+Price - If you entered a price in the copy template that you created for this subscription, then it will appear by default in the distributions. You can also \r
+manually enter a price if you did not include one in the copy template.\r
</simpara>\r
</step>\r
<step>\r
<simpara>\r
-Receive? – The boxes in the Receive? Column are checked by default. Uncheck the box if you do not want to receive the item. Evergreen will retain the unreceived copies and will allow you to receive them at a later time.\r
+Receive? – The boxes in the Receive? Column are checked by default. Uncheck the box if you do not want to receive the item. Evergreen will retain the unreceived \r
+copies and will allow you to receive them at a later time.\r
</simpara>\r
</step>\r
</procedure>\r
</step>\r
<step>\r
<simpara>\r
-If the items that you received have a barcode, a copy template that was set to OPAC Visible, and are assigned a shelving location that is OPAC Visible, then you can view the received items in the catalog. Notice that the Holdings Summary has been updated to reflect the most recent addition to the holdings.\r
+If the items that you received have a barcode, a copy template that was set to OPAC Visible, and are assigned a shelving location that is OPAC Visible, \r
+then you can view the received items in the catalog. Notice that the Holdings Summary has been updated to reflect the most recent addition to the holdings.\r
</simpara>\r
</step>\r
</procedure>\r
\r
<section id="_serial_control_view">\r
<title>Serial Control View</title>\r
-<simpara>Serial Control View is separate from the Alternate Serial Control interface. Serial Control View enables you to manage serials in a single tabbed interface. This view also enables you to bind units. Serial Control View consists of five tabs: Items, Units, Distributions, Subscriptions, and Claims. Units and Claims are not functional in 2.0.</simpara>\r
+<simpara>Serial Control View is separate from the Alternate Serial Control interface. Serial Control View enables you to manage serials in a single tabbed interface. \r
+This view also enables you to bind units. Serial Control View consists of five tabs: Items, Units, Distributions, Subscriptions, and Claims. </simpara>\r
<simpara>To access Serial Control View, open a bib record and click Actions for this Record → Serial Control View.</simpara>\r
<simplesect>\r
<title>Subscriptions</title>\r
</step>\r
<step>\r
<simpara>\r
-Enter the difference between the nominal publishing date of an issue and the date that you expect to receive your copy in the Expected Date Offset. For example, if an issue is published the first day of each month, but you receive the copy two days prior to the publication date, then enter -2 days into this field.\r
+Enter the difference between the nominal publishing date of an issue and the date that you expect to receive your copy in the Expected Date Offset. For example, \r
+if an issue is published the first day of each month, but you receive the copy two days prior to the publication date, then enter -2 days into this field.\r
</simpara>\r
</step>\r
<step>\r
</simplesect>\r
<simplesect>\r
<title>Edit a subscription</title>\r
-<simpara>To edit a subscription, select the subscription in the tree on the left side of the screen. You can edit the following categories: Owning Lib, Start Date, End Date, and Date Offset. After you edit the subscription, click Modify Subscription(s) to save the changes.</simpara>\r
+<simpara>To edit a subscription, select the subscription in the tree on the left side of the screen. You can edit the following categories: Owning Lib, Start Date, \r
+End Date, and Date Offset. After you edit the subscription, click Modify Subscription(s) to save the changes.</simpara>\r
</simplesect>\r
</simplesect>\r
<simplesect>\r
<title>Distributions</title>\r
-<simpara>Distributions indicate the branches that should receive copies of a serial. Distributions work together with streams to indicate the number of copies that should be sent to each branch.</simpara>\r
+<simpara>Distributions indicate the branches that should receive copies of a serial. Distributions work together with streams to indicate the number of copies \r
+that should be sent to each branch.</simpara>\r
<simplesect>\r
<title>Create a distribution</title>\r
<procedure>\r
</step>\r
<step>\r
<simpara>\r
-Apply a new label to the distribution. It may be useful to identify the branch to which you are distributing these issues in this field. This field is not publicly visible and only appears when an item is received. There are no limits on the number of characters that can be entered in this field.\r
+Apply a new label to the distribution. It may be useful to identify the branch to which you are distributing these issues in this field. This field is not \r
+publicly visible and only appears when an item is received. There are no limits on the number of characters that can be entered in this field.\r
</simpara>\r
</step>\r
<step>\r
<simpara>\r
-Apply a prefix to the spine label if desired. This information will display in Serial Control View when the items are received, but it does not print on the spine label in . 0.\r
+Apply a prefix to the spine label if desired. This information will display in Serial Control View when the items are received.\r
</simpara>\r
</step>\r
<step>\r
<simpara>\r
-Apply a suffix to the spine label if desired. This information will display in Serial Control View when the items are received, but it does not print on the spine label in . 0.\r
+Apply a suffix to the spine label if desired. This information will display in\r
+Serial Control View when the items are received.\r
</simpara>\r
</step>\r
<step>\r
</step>\r
<step>\r
<simpara>\r
-The Legacy Record Entry contains the MFHD records that are attached to the bib record if the owning library is identical to the distribution’s holding library. A distribution can thus be an extension of an MFHD record. Select the MFHD record from the drop down menu.\r
+The Legacy Record Entry contains the MFHD records that are attached to the bib record if the owning library is identical to the distribution’s \r
+holding library. A distribution can thus be an extension of an MFHD record. Select the MFHD record from the drop down menu.\r
</simpara>\r
</step>\r
<step>\r
<simpara>\r
-The Receive Call Number field is empty until you receive the first item. When you receive the first item, you are prompted to enter a call number. That call number will populate this drop down menu.\r
+The Receive Call Number field is empty until you receive the first item. When you receive the first item, you are prompted to enter a call number. \r
+That call number will populate this drop down menu.\r
</simpara>\r
</step>\r
<step>\r
<simpara>\r
-The Bind Call Number field is empty until you bind the first item. When you receive the first item, you are prompted to enter a call number. That call number will populate this drop down menu.\r
+The Bind Call Number field is empty until you bind the first item. When you receive the first item, you are prompted to enter a call number. That \r
+call number will populate this drop down menu.\r
</simpara>\r
</step>\r
<step>\r
</simplesect>\r
<simplesect>\r
<title>Edit a distribution</title>\r
-<simpara>To edit a distribution, select the distribution in the tree on the left side of the screen. You can edit the following categories: Label, Holding Lib, Legacy Record Entry, Receive Unit Template, Bind Unit Template, Receive Call Number and Bind Call Number. After you edit the distribution, click Modify Distribution(s) to save the changes.</simpara>\r
+<simpara>To edit a distribution, select the distribution in the tree on the left side of the screen. You can edit the following categories: \r
+Label, Holding Lib, Legacy Record Entry, Receive Unit Template, Bind Unit Template, Receive Call Number and Bind Call Number. After you edit \r
+the distribution, click Modify Distribution(s) to save the changes.</simpara>\r
</simplesect>\r
</simplesect>\r
<simplesect>\r
<title>Streams</title>\r
-<simpara>Distributions work together with streams to indicate the number of copies that should be sent to each branch. Distributions identify the branches that should receive copies of a serial. Streams identify how many copies should be sent to each branch. Streams are intended for copies that are received on a recurring, even if irregular, basis.</simpara>\r
-<simpara>In our example, the Apex Branch should receive copies, so we created a distribution to that branch. The Apex Branch should receive two copies, so we will create two streams to that branch.</simpara>\r
+<simpara>Distributions work together with streams to indicate the number of copies that should be sent to each branch. Distributions \r
+identify the branches that should receive copies of a serial. Streams identify how many copies should be sent to each branch. \r
+Streams are intended for copies that are received on a recurring, even if irregular, basis.</simpara>\r
+<simpara>In our example, the Apex Branch should receive copies, so we created a distribution to that branch. The Apex Branch \r
+should receive two copies, so we will create two streams to that branch.</simpara>\r
<simplesect>\r
<title>Create a stream</title>\r
<procedure>\r
</step>\r
<step>\r
<simpara>\r
-Enter a routing label so that the copy could be read by specific users or departments before the copy is shelved. The routing label appears during receiving and could be added to routing lists; it is not viewable by the public. Routing lists do not print in . 0. This field is optional.\r
+Enter a routing label so that the copy could be read by specific users or departments before the\r
+copy is shelved. The routing label appears during receiving and could be added to routing lists; it\r
+is not viewable by the public. This field is optional.\r
</simpara>\r
</step>\r
<step>\r
</simpara>\r
</step>\r
</procedure>\r
-<simpara>The data in the Basic Summary, Supplement Summary, and Index Summary are automatically generated by the ILS when you create a caption and pattern and a holdings statement. You can create additional textual holdings manually by editing the Textual Holdings field.</simpara>\r
+<simpara>The data in the Basic Summary, Supplement Summary, and Index Summary are automatically\r
+generated by the ILS when you create a caption and pattern and a holdings statement. You can\r
+create additional textual holdings manually by editing the Textual Holdings field.</simpara>\r
</simplesect>\r
-<simplesect>\r
-<title>Edit a stream</title>\r
-<procedure>\r
-<step>\r
-<simpara>\r
-To edit a stream, select the stream in the tree on the left side of the screen. You can edit the following category:\r
-</simpara>\r
-<itemizedlist>\r
-<listitem>\r
-<simpara>\r
-Routing Label – The label given to an issue to direct it to the people or departments that should view the issue before it is available to the public.\r
-</simpara>\r
-</listitem>\r
-</itemizedlist>\r
-</step>\r
-<step>\r
-<simpara>\r
-The Basic Summary displays the distribution ID, the Textual Holdings, and the Generated Holdings. The OPAC uses data in legacy records, the generated coverage field, and the textual holdings fields to display holdings information.\r
-</simpara>\r
+<simplesect> \r
+<title>Edit a stream</title> \r
+<procedure> \r
+<step> \r
+<simpara> To edit a\r
+stream, select the stream in the tree on the left side of the screen. You can edit the following\r
+category: </simpara> \r
+<itemizedlist> \r
+<listitem> \r
+<simpara> Routing Label – The label given to an issue\r
+to direct it to the people or departments that should view the issue before it is available to the\r
+public. </simpara> \r
+</listitem> \r
+</itemizedlist> \r
+</step> \r
+<step> \r
+<simpara> The Basic Summary displays\r
+the distribution ID, the Textual Holdings, and the Generated Holdings. The OPAC uses data in legacy\r
+records, the generated coverage field, and the textual holdings fields to display holdings\r
+information. </simpara>\r
<procedure numeration="loweralpha">\r
<step>\r
<simpara>\r
</step>\r
<step>\r
<simpara>\r
-Textual Holdings – Enter any additional holdings information in this field, and it will display in the OPAC as Additional Volume Information.\r
+Textual Holdings – Enter any additional holdings information in this field, and it will display in\r
+the OPAC as Additional Volume Information.\r
</simpara>\r
</step>\r
<step>\r
</simplesect>\r
<simplesect>\r
<title>Captions and Patterns</title>\r
-<simpara>The Captions and Patterns wizard allows you to enter caption and pattern data as it is described by the 853, 854, and 855 MARC tags. These tags allow you to define how issues will be captioned, and how often the library receives issues of the serial.</simpara>\r
-<simpara>In 2.0, it is not possible to create a caption and pattern and apply it to multiple subscriptions. However, you can re-use patterns if you copy and paste to and from the pattern code field in the Captions and Patterns tab.</simpara>\r
+<simpara>The Captions and Patterns wizard allows you to enter caption and pattern data as it is\r
+described by the 853, 854, and 855 MARC tags. These tags allow you to define how issues will be\r
+captioned, and how often the library receives issues of the serial.</simpara> \r
<simplesect>\r
<title>Create a caption and pattern</title>\r
<procedure>\r
</step>\r
<step>\r
<simpara>\r
-Beneath the subscription, click Captions and Patterns, and right-click or click Actions for Selected Row → Add Caption/Pattern.\r
-</simpara>\r
+Beneath the subscription, click Captions and Patterns, and right-click or click Actions for Selected\r
+Row → Add Caption/Pattern. </simpara>\r
</step>\r
<step>\r
<simpara>\r
</step>\r
<step>\r
<simpara>\r
-Click the Unset entry beneath Type. A drop down menu will appear. Choose the type of caption and pattern that you want to create, and click Apply.\r
-</simpara>\r
+Click the Unset entry beneath Type. A drop down menu will appear. Choose the type of caption and\r
+pattern that you want to create, and click Apply. </simpara>\r
</step>\r
<step>\r
<simpara>\r
-Click the Unset entry beneath Active. A drop down menu will appear. Choose Yes if you want to activate the caption and pattern. Click Apply.\r
-</simpara>\r
+Click the Unset entry beneath Active. A drop down menu will appear. Choose Yes if you want to\r
+activate the caption and pattern. Click Apply. </simpara>\r
</step>\r
<step>\r
-<simpara>\r
-Click the Unset entry beneath the Pattern Code (temporary) field if you want to create the pattern code by hand. If you want to create it automatically, click Pattern Code Wizard in the lower right corner.\r
-</simpara>\r
+<simpara> Click the Unset entry beneath the Pattern Code (temporary) field if you want to create the\r
+pattern code by hand. If you want to create it automatically, click Pattern Code Wizard in the\r
+lower right corner. </simpara>\r
</step>\r
<step>\r
<simpara>\r
</simplesect>\r
<simplesect>\r
<title>Issuances</title>\r
-<simpara>The Issuances tab enables you to manually create an issue in the ILS. The ILS will use the initial issue that you manually create to predict future issues.</simpara>\r
-<simplesect>\r
+<simpara>The Issuances tab enables you to manually create an issue in the ILS. The ILS will use the\r
+initial issue that you manually create to predict future issues.</simpara> <simplesect>\r
<title>Create an issuance</title>\r
<procedure>\r
<step>\r
</step>\r
<step>\r
<simpara>\r
-Enter the Date Published of the issuance that you are editing. Enter the date in YYYY-MM-DD format. If you are creating one manual issue before automatically predicting more issues, then this date should be the date that you want to enter before the prediction starts. Click Apply.\r
-</simpara>\r
+Enter the Date Published of the issuance that you are editing. Enter the date in YYYY-MM-DD format.\r
+If you are creating one manual issue before automatically predicting more issues, then this date\r
+should be the date that you want to enter before the prediction starts. Click Apply. </simpara>\r
</step>\r
<step>\r
<simpara>\r
-Click in the Issuance Label field to name the issuance. There are no limits on the number of characters that can be entered in this field. You may want to enter the month and year of the publication in hand. Click Apply.\r
-</simpara>\r
+Click in the Issuance Label field to name the issuance. There are no limits on the number of\r
+characters that can be entered in this field. You may want to enter the month and year of the\r
+publication in hand. Click Apply. </simpara>\r
</step>\r
<step>\r
<simpara>\r
</simplesect>\r
<simplesect>\r
<title>Edit an issuance</title>\r
-<simpara>To edit an issuance, select the issuance in the tree on the left side of the screen. You can edit the following categories: Holding Code, Caption/Pattern, Date Published, and Issuance Label. After you edit the issuance, click Modify Issuance(s) to save the changes.</simpara>\r
+<simpara>To edit an issuance, select the issuance in the tree on the left side of the screen. You\r
+can edit the following categories: Holding Code, Caption/Pattern, Date Published, and Issuance\r
+Label. After you edit the issuance, click Modify Issuance(s) to save the changes.</simpara>\r
</simplesect>\r
</simplesect>\r
<simplesect>\r
<procedure>\r
<step>\r
<simpara>\r
-To receive items, click the Receive radio button. In the top half of the screen, the items that have yet to be received are displayed. In the bottom half of the screen, recently received items are displayed.\r
-</simpara>\r
+To receive items, click the Receive radio button. In the top half of the screen, the items that\r
+have yet to be received are displayed. In the bottom half of the screen, recently received items\r
+are displayed. </simpara>\r
</step>\r
<step>\r
<simpara>\r
</simpara>\r
</listitem>\r
<listitem>\r
-<simpara>\r
-If you want the item to be received or bound into an existing item, select Recent and select the desired issue. To making a change in bound items, receive or bind the items into an already existing unit.\r
-</simpara>\r
+<simpara> If you want the item to be received or bound into an existing item, select Recent and\r
+select the desired issue. To making a change in bound items, receive or bind the items into an\r
+already existing unit. </simpara>\r
</listitem>\r
</itemizedlist>\r
</step>\r
</simpara>\r
</step>\r
<step>\r
-<simpara>\r
-The screen refreshes. In the top half of the screen, the item displays a received date. In the bottom half of the screen, the item that you have just received is now at the top of the list of the received items.\r
-</simpara>\r
+<simpara> The screen refreshes. In the top half of the screen, the item displays a received date.\r
+In the bottom half of the screen, the item that you have just received is now at the top of the list\r
+of the received items. </simpara>\r
</step>\r
</procedure>\r
-<simpara>After receiving items, you can view the updated holdings in the OPAC. In this example, the legacy MFHD record and the items recently received in the serial control view display together in the MFHD statement.</simpara>\r
-</simplesect>\r
+<simpara>After receiving items, you can view the updated holdings in the OPAC. In this example, the\r
+legacy MFHD record and the items recently received in the serial control view display together in\r
+the MFHD statement.</simpara> </simplesect>\r
<simplesect>\r
<title>Edit Item Attributes</title>\r
-<simpara>In this pop up box, you can view the Item ID, Status, Distribution, and Shelving ID. These are generated by Evergreen. However, you may need to edit an item’s Date Expected or Received.</simpara>\r
+<simpara>In this pop up box, you can view the Item ID, Status, Distribution, and Shelving ID. These\r
+are generated by Evergreen. However, you may need to edit an item’s Date Expected or\r
+Received.</simpara> \r
<procedure>\r
<step>\r
<simpara>\r
</simplesect>\r
<simplesect>\r
<title>Delete Items</title>\r
-<simpara>You can use this menu item to delete items from your holdings. To delete items from your holdings, click Actions for Selected Rows → Delete Item.</simpara>\r
-</simplesect>\r
+<simpara>You can use this menu item to delete items from your holdings. To delete items from your\r
+holdings, click Actions for Selected Rows → Delete Item.</simpara> </simplesect>\r
</simplesect>\r
<simplesect>\r
<title>Bind Items</title>\r
-<simpara>The binding mode applies the binding template, which is defined in the distribution (see simplesect 2 for more information), to units that should be bound.</simpara>\r
- <procedure>\r
+<simpara>The binding mode applies the binding template, which is defined in the distribution (see\r
+simplesect 2 for more information), to units that should be bound.</simpara> \r
+<procedure>\r
<step>\r
<simpara>\r
Select the the branch that will receive the items from the drop down box.\r
</simpara>\r
</step>\r
<step>\r
- <simpara>\r
- Open a serial record, and in the bottom right corner above the copy information, click Add MFHD Record. You can also add the MFHD statement by clicking Actions for this Record →MFHD Holdings →Add MFHD Record.\r
- </simpara>\r
+ <simpara> Open a serial record, and in the bottom right corner above the copy information,\r
+ click Add MFHD Record. You can also add the MFHD statement by clicking Actions for this Record\r
+ →MFHD Holdings →Add MFHD Record. </simpara>\r
</step>\r
<step>\r
<simpara>\r
</procedure>\r
</section>\r
<section id="serial_permissions">\r
- <simpara>The following permissions enable you to control serials’ functions. Although you can assign each permission to users in the Admin module, it is recommended that either all serials permissions be assigned to an individual, or that they should be assigned to individuals in the following groups.</simpara>\r
- <simpara>The following permission allow you to create, manage, view, edit, and perform all other functions associated with these serials tasks:</simpara>\r
+ <simpara>The following permissions enable you to control serials’ functions. Although you\r
+ can assign each permission to users in the Admin module, it is recommended that either all serials\r
+ permissions be assigned to an individual, or that they should be assigned to individuals in the\r
+ following groups.</simpara> \r
+ <simpara>The following permission allow you to create, manage, view,\r
+ edit, and perform all other functions associated with these serials tasks:</simpara>\r
<itemizedlist>\r
<listitem>\r
<simpara>\r
</section>\r
<section id="_serials_creating_a_special_issue_to_receive"> \r
<title>Creating a Special Issue to Receive</title>\r
- <simpara>Sometimes you may have to create a special issue to receive that occur outside of the standard publication pattern. To do this you need to do the following:</simpara>\r
+ <simpara>Sometimes you may have to create a special issue to receive that occur outside of\r
+ the standard publication pattern. To do this you need to do the following:</simpara>\r
<procedure>\r
<step>\r
<simpara>\r
</simpara>\r
</step>\r
<step>\r
- <simpara>\r
- The item is now ready to receive. If you complete the Date Received field and change the status to received then it will receive the issue but it won't create the associated copy record whereas if you leave it blank and receive the item through the Serials Control View or Batch Receive function you can create the Copy Record at that time.\r
+ <simpara> The item is now ready to receive. If you complete the Date Received field and\r
+ change the status to received then it will receive the issue but it won't create the associated copy\r
+ record whereas if you leave it blank and receive the item through the Serials Control View or Batch\r
+ Receive function you can create the Copy Record at that time.\r
</simpara>\r
</step>\r
</procedure>\r
projects / Evergreen-DocBook.git / commitdiff