[open-ils-commits] [GIT] Evergreen ILS branch master updated. ab6fc5b5abdd11bb185811b1cdd661318d3bacfc

Thu Nov 9 16:32:27 EST 2017

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Evergreen ILS".

The branch, master has been updated
       via  ab6fc5b5abdd11bb185811b1cdd661318d3bacfc (commit)
      from  58d7749a488717ff9e0ef060a088426a3657bb5f (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit ab6fc5b5abdd11bb185811b1cdd661318d3bacfc
Author: Angela Kilsdonk <akilsdonk at esilibrary.com>
Date:   Thu Nov 9 13:31:21 2017 -0800

    Docs: Serials Module 3.0
    
    Documentation for the Serials module in Evergreen 3.0
    
    Signed-off-by: Angela Kilsdonk <akilsdonk at equinoxinitiative.org>

diff --git a/docs/media/serials_ct1.PNG b/docs/media/serials_ct1.PNG
new file mode 100644
index 0000000..5f78c5a
Binary files /dev/null and b/docs/media/serials_ct1.PNG differ
diff --git a/docs/media/serials_extra1.PNG b/docs/media/serials_extra1.PNG
new file mode 100644
index 0000000..0bdbfe7
Binary files /dev/null and b/docs/media/serials_extra1.PNG differ
diff --git a/docs/media/serials_extra2.PNG b/docs/media/serials_extra2.PNG
new file mode 100644
index 0000000..af795b9
Binary files /dev/null and b/docs/media/serials_extra2.PNG differ
diff --git a/docs/media/serials_mfhd1.PNG b/docs/media/serials_mfhd1.PNG
new file mode 100644
index 0000000..8b0f1c5
Binary files /dev/null and b/docs/media/serials_mfhd1.PNG differ
diff --git a/docs/media/serials_mfhd2.PNG b/docs/media/serials_mfhd2.PNG
new file mode 100644
index 0000000..c033931
Binary files /dev/null and b/docs/media/serials_mfhd2.PNG differ
diff --git a/docs/media/serials_mfhd3.PNG b/docs/media/serials_mfhd3.PNG
new file mode 100644
index 0000000..3b652d4
Binary files /dev/null and b/docs/media/serials_mfhd3.PNG differ
diff --git a/docs/media/serials_mfhd4.PNG b/docs/media/serials_mfhd4.PNG
new file mode 100644
index 0000000..6d3be96
Binary files /dev/null and b/docs/media/serials_mfhd4.PNG differ
diff --git a/docs/media/serials_mfhd5.PNG b/docs/media/serials_mfhd5.PNG
new file mode 100644
index 0000000..7e3c90b
Binary files /dev/null and b/docs/media/serials_mfhd5.PNG differ
diff --git a/docs/media/serials_mfhd6.PNG b/docs/media/serials_mfhd6.PNG
new file mode 100644
index 0000000..222b1e6
Binary files /dev/null and b/docs/media/serials_mfhd6.PNG differ
diff --git a/docs/media/serials_routing1.PNG b/docs/media/serials_routing1.PNG
new file mode 100644
index 0000000..12aba41
Binary files /dev/null and b/docs/media/serials_routing1.PNG differ
diff --git a/docs/media/serials_sub0.PNG b/docs/media/serials_sub0.PNG
new file mode 100644
index 0000000..5efad47
Binary files /dev/null and b/docs/media/serials_sub0.PNG differ
diff --git a/docs/media/serials_sub1.PNG b/docs/media/serials_sub1.PNG
new file mode 100644
index 0000000..34435de
Binary files /dev/null and b/docs/media/serials_sub1.PNG differ
diff --git a/docs/media/serials_sub10.PNG b/docs/media/serials_sub10.PNG
new file mode 100644
index 0000000..ca2f1c3
Binary files /dev/null and b/docs/media/serials_sub10.PNG differ
diff --git a/docs/media/serials_sub11.PNG b/docs/media/serials_sub11.PNG
new file mode 100644
index 0000000..a190a81
Binary files /dev/null and b/docs/media/serials_sub11.PNG differ
diff --git a/docs/media/serials_sub2.PNG b/docs/media/serials_sub2.PNG
new file mode 100644
index 0000000..e2c808c
Binary files /dev/null and b/docs/media/serials_sub2.PNG differ
diff --git a/docs/media/serials_sub3.PNG b/docs/media/serials_sub3.PNG
new file mode 100644
index 0000000..89ef1be
Binary files /dev/null and b/docs/media/serials_sub3.PNG differ
diff --git a/docs/media/serials_sub4.PNG b/docs/media/serials_sub4.PNG
new file mode 100644
index 0000000..e749b25
Binary files /dev/null and b/docs/media/serials_sub4.PNG differ
diff --git a/docs/media/serials_sub5.PNG b/docs/media/serials_sub5.PNG
new file mode 100644
index 0000000..33ffd04
Binary files /dev/null and b/docs/media/serials_sub5.PNG differ
diff --git a/docs/media/serials_sub6.PNG b/docs/media/serials_sub6.PNG
new file mode 100644
index 0000000..44ebb6e
Binary files /dev/null and b/docs/media/serials_sub6.PNG differ
diff --git a/docs/media/serials_sub7.PNG b/docs/media/serials_sub7.PNG
new file mode 100644
index 0000000..48e7e5e
Binary files /dev/null and b/docs/media/serials_sub7.PNG differ
diff --git a/docs/media/serials_sub8.PNG b/docs/media/serials_sub8.PNG
new file mode 100644
index 0000000..be1812e
Binary files /dev/null and b/docs/media/serials_sub8.PNG differ
diff --git a/docs/media/serials_sub9.PNG b/docs/media/serials_sub9.PNG
new file mode 100644
index 0000000..f34c617
Binary files /dev/null and b/docs/media/serials_sub9.PNG differ
diff --git a/docs/media/serials_wizard1.PNG b/docs/media/serials_wizard1.PNG
new file mode 100644
index 0000000..9b6345d
Binary files /dev/null and b/docs/media/serials_wizard1.PNG differ
diff --git a/docs/media/serials_wizard2.PNG b/docs/media/serials_wizard2.PNG
new file mode 100644
index 0000000..96c4309
Binary files /dev/null and b/docs/media/serials_wizard2.PNG differ
diff --git a/docs/media/serials_wizard3.PNG b/docs/media/serials_wizard3.PNG
new file mode 100644
index 0000000..ccd7ba8
Binary files /dev/null and b/docs/media/serials_wizard3.PNG differ
diff --git a/docs/media/serials_wizard4.PNG b/docs/media/serials_wizard4.PNG
new file mode 100644
index 0000000..50f0c98
Binary files /dev/null and b/docs/media/serials_wizard4.PNG differ
diff --git a/docs/media/serials_wizard5.PNG b/docs/media/serials_wizard5.PNG
new file mode 100644
index 0000000..6b94925
Binary files /dev/null and b/docs/media/serials_wizard5.PNG differ
diff --git a/docs/media/serials_wizard6.PNG b/docs/media/serials_wizard6.PNG
new file mode 100644
index 0000000..7184b6c
Binary files /dev/null and b/docs/media/serials_wizard6.PNG differ
diff --git a/docs/root.adoc b/docs/root.adoc
index 940cb84..52e437d 100644
--- a/docs/root.adoc
+++ b/docs/root.adoc
@@ -375,17 +375,17 @@ Serials
 
 include::serials/A-intro.adoc[]
 
-include::serials/B-copy_template.adoc[]
+include::serials/B-serials_admin.adoc[]
 
-include::serials/C-subscription-SCV.adoc[]
+include::serials/C-serials_workflow.adoc[]
 
-include::serials/D-subscription-ASCV.adoc[]
+include::serials/D-Receiving.adoc[]
 
-include::serials/E-edit_subscriptions.adoc[]
+include::serials/E-routing_lists.adoc[]
 
-include::serials/F-Receiving.adoc[]
+include::serials/F-Special_issue.adoc[]
 
-include::serials/G-Special_issue.adoc[]
+include::serials/G-binding.adoc[]
 
 include::serials/H-holdings_statements.adoc[]
 
diff --git a/docs/root_serials.adoc b/docs/root_serials.adoc
index 1426e11..e5eaacb 100644
--- a/docs/root_serials.adoc
+++ b/docs/root_serials.adoc
@@ -36,22 +36,22 @@ include::serials/A-intro.adoc[]
 
 :leveloffset: 0
  
-include::serials/B-copy_template.adoc[]
+include::serials/B-serials_admin.adoc[]
 
-include::serials/C-subscription-SCV.adoc[]
+include::serials/C-serials_workflow.adoc[]
 
-include::serials/D-subscription-ASCV.adoc[]
+include::serials/D-Receiving.adoc[]
 
-include::serials/E-edit_subscriptions.adoc[]
+include::serials/E-routing_lists.adoc[]
 
-include::serials/F-Receiving.adoc[]
+include::serials/F-Special_issue.adoc[]
 
-include::serials/Group_Serials_Issues_in_the_OPAC_2.2.adoc[]
-
-include::serials/G-Special_issue.adoc[]
+include::serials/G-binding.adoc[]
 
 include::serials/H-holdings_statements.adoc[]
 
+include::serials/Group_Serials_Issues_in_the_OPAC_2.2.adoc[]
+
 :leveloffset: -1
 
 include::opac/using_the_public_access_catalog.adoc[]
diff --git a/docs/serials/A-intro.adoc b/docs/serials/A-intro.adoc
index 1e430de..c85ee36 100644
--- a/docs/serials/A-intro.adoc
+++ b/docs/serials/A-intro.adoc
@@ -1,35 +1,7 @@
 Serials
 -------
 
-Serial Control View vs. Alternate Serial Control View 
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Serial Control View and Alternate Serial Control View offer you two views of Serials. Both views enable you to create subscriptions, add distributions, define captions, predict future issues, and receive items. Serial Control View was designed for users who work with a smaller number of issues and was designed to accommodate workflows in academic and special libraries. Alternate Serial Control View was designed for users who receive a larger number of issues and was designed for use in public libraries.
-
-In version 2.4, the two interfaces have taken a big step toward unification.  Now in the Serial Control View, within the Subscription editor, you will find an embedded version of the Alternate Serial Control View.  This new unified interface tries to provide the best features of both views, giving full access to the Alternate view functions from within the tabbed Serial Control View.  One exception is that you cannot predict new issues from within the embedded Alternate view; instead you should use the standard Serial Control View method of predicting issues, <<_generate_prediction,explained here>>.  Also, some improvements were made to the embedded Alternate view to prevent losing features that were available in the old Serial Control View editors.  These changes include: new "Edit Notes" buttons on the subscriptions and distributions editors; labeled dropdown for distribution summary options ("Add to record entry", "Use record entry only", etc.); new legacy record entry li
 nkage (allows one to tie a distribution's information to a particular serial record entry (i.e. a MFHD record)).
-
-Outside of the Subscription Editor, the two views maintain their previous looks and usage.  You are encouraged to use the new combination view and provide feedback to the link:http://libmail.georgialibraries.org/mailman/listinfo/open-ils-general[Evergreen general discussion list].
-
-The views are interoperable, but because they were designed for different purposes, some differences emerge. For example, Serial Control View enables you to create and edit serials in a single tabbed interface while Alternate Serial Control View leads you through a series of steps on multiple screens. In addition, receiving functions vary between views. Both receiving interfaces enable you to batch receive issues. However, the Serials Batch Receive interface, which is associated with Alternate Serial Control View, allows for more customization of each receiving unit while the Items tab in Serial Control View allows for greater flexibility in creating multi-issue units, such as in binding serials.
-
-[NOTE]
-The new combination view tries to provide the best of both views in one place. Try it out and send your feedback to the link:http://libmail.georgialibraries.org/mailman/listinfo/open-ils-general[Evergreen general discussion list].
-
-.Serials Control View and Alternate Serials Control View Comparison
-[options="header"]
-|====================================================================================================
-|Function	|Serials Control View	|Alternate Serials Control View	|Combination View
-|Menu Style	|Menu driven	|Wizard oriented	|Both
-|Setting Up subscription	|No calendar drop downs	|Includes calendar drop down |Includes calendar drop down
-|Creating streams	|No setup required	|Requires streams	|No setup required
-|Creating captions and patterns	|Wizard available	|Wizard available	|Wizard available
-|Adding Starting Issue	|Includes holdings code wizard	|Includes holdings code wizard	|Includes holdings code wizard
-|Generate Predictions	|Make predictions	|Generate predictions	|Make predictions
-|Add items for special issue	|No functionality	|New items on issuances tab	|New items on issuances tab
-|Receiving issues	|Multiple modes in Items tab	|Batch Receive	|Both
-|====================================================================================================
-
 MFHD Records
 ~~~~~~~~~~~~
 
-MARC Format for Holdings Display (MFHD) display in the OPAC in addition to holding statements generated by Evergreen from subscriptions created in the Serials Control View or the Alternate Serials Control View.  The MFHDs are editable as MARC but the holdings statements generated from the control view are system generated. Multiple MFHDs can be created and are tied to Organizational Units.
+MARC Format for Holdings Display (MFHD) display in the catalog in addition to holding statements generated by Evergreen from subscriptions created in the Serials Module. The MFHDs are editable as MARC but the holdings statements generated from the control view are system generated. Multiple MFHDs can be created and are tied to Organizational Units.
diff --git a/docs/serials/B-copy_template.adoc b/docs/serials/B-copy_template.adoc
deleted file mode 100644
index ed38cf2..0000000
--- a/docs/serials/B-copy_template.adoc
+++ /dev/null
@@ -1,41 +0,0 @@
-Copy Template for Serials
--------------------------
-
-A copy template enables you to specify item attributes that should be applied by default to copies of serials. You can create one copy template and apply it to multiple serials. You can also create multiple copy templates. Templates will be used in the Alternate Serial Control View or the Serial Control View.
-
-Create a copy template
-~~~~~~~~~~~~~~~~~~~~~~
-
-To create a copy template, click *Administration* -> *Local Administration* ->  *Copy Template Editor*.
-
-. Enter a Name for the template.
-. Select an owning library from the _Owning Lib_ drop down menu. This organization owns the copy template. A staff member with permissions at that organization can modify the copy template. The menu is populated from the organizations that you created in *Administration* -> *Server Administration* ->  *Organizational Units*.
-. Check _Circulate?_ if you want the item to circulate.
-. Check _Holdable?_ if patrons can place holds on the item.
-. Check _OPAC Visible?_ if you want patrons to be able to see the item in the OPAC after you receive it.
-. Select a _Loan Duration_ rule from the drop down menu. This field is required.
-. Select a _Fine Level_ for the item from the drop down menu. This field is required.
-. Select a copy location from the _Location_ drop down menu. The menu is populated from the copy locations that you created in *Administration* -> *Local Administration* ->  *Copy Locations*.
-. Select a _Circ Modifier_ from the drop down menu. The menu is populated from the modifiers that you created in *Administration* -> *Server Administration* ->  *Circulation Modifiers*.
-. Select a _Floating Group_ if the item is part of a floating collection.
-. Check _Deposit?_ if patrons must place a deposit on the copy before they can use it.
-. Check _Reference?_ if the item is a reference item.
-. Check _Mint Condition?_ if the item is in mint condition.
-. Enter age protection rules in the _Age Protect_ field. Age protection allows you to control the extent to which an item can circulate 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 at your branch can use it.
-. Enter a message in the _Alert Message_ field. This message will appear every time the item is checked out to a patron.
-. Enter a code from the MARC fixed fields into the _Circ as Type_ field if you want to control the circulation based on the item type.
-. Enter a _Deposit Amount_ if patrons must place a deposit on the copy before they can use it.
-. Enter the _Price_ of the item.
-. Select a copy status from the _Status_ drop down menu. The copy statuses can be managed in *Administration* -> *Server Administration* ->  *Copy Statuses*.
-. Click *Save*.
-
-Edit a copy template
-~~~~~~~~~~~~~~~~~~~~
-
-You can make changes to an existing copy template. Changes that you make to a copy template will apply to any items that you receive after you edited the template.
-
-. Double-click the row you want to edit. The copy template will appear, and you can edit the fields.
-. After making changes, click *Save*.
-
-[NOTE]
-From the copy template interface, you can delete copy templates that have never been used. First check the box for the template you wish to delete, then click *Delete Selected*.
diff --git a/docs/serials/B-serials_admin.adoc b/docs/serials/B-serials_admin.adoc
new file mode 100644
index 0000000..1676a00
--- /dev/null
+++ b/docs/serials/B-serials_admin.adoc
@@ -0,0 +1,151 @@
+Serials Administration
+----------------------
+
+The serials module can be administered under a new menu option:  *Administration->Serials Administration*.  The new Serials Administration menu currently allows staff to configure _Serial Copy Templates_ and _Pattern Templates_.
+
+
+Serial Copy Templates
+~~~~~~~~~~~~~~~~~~~~~
+Serials copy templates enable you to specify item attributes that should be applied by default to copies of serials.  Serials copy templates are associated with distributions in a subscription and are applied when serials copies are received.  Serial copy templates can also be used as a binding template to apply specific item attributes to copies that are being bound together.
+
+
+Creating a Serial Copy Template
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+To create a serial copy template, go to *Administration->Serials Administration->Serial Copy Templates*:
+
+. Click *Create Template* in the upper-right hand corner. A dialog box will appear.
+. Within the dialog box assign the template a _Template Name_ and set any item attributes that you want in the template:
+.. *Circulate?*: indicate if the items can circulate.
+.. *Circulation Library*: Select the circulation library from the drop down menu.
+.. *Shelving Location*: Select the shelving location for the item from the drop down menu.  This menu is populated from the locations created in Admin->Local Administration->Copy Locations Editor.
+.. *Circulation Modifier*: Select the circulation modifier for the item from the drop down menu.  This menu is populated from the modifiers created in Admin->Server Administration->Circulation Modifiers.
+.. *Loan Duration*: Select a loan duration from the drop down menu.  This menu is populated from the loan durations created in Admin->Server Administration->Circulation Duration Rules.  This field is required.  
+.. *Circulate as Type*: Select a Type of record from the drop down menu if you want to control circulation based on the Type fixed field in the MARC bibliographic record.  Most libraries choose to control circulation based on Circulation Modifier instead of Circulate as Type in Evergreen.
+.. *Holdable?*: Yes or No-- indicate if holds can be placed on the items.
+.. *Age-based Hold Protection*:  Select a rule from the drop down menu.  Age-based hold protection allows you to control the extent to which an item can circulate 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 at your branch can use it.
+.. *Fine Level*:  Select a fine level from the drop down menu.  This menu is populated from the fine levels created in Admin->Server Administration->Circulation Recurring Fine Rules.  This field is required.
+.. *Floating*:  Select a Floating policy from the drop down menu if the items belong to a floating collection.
+.. *Status*:  Select a copy status from the Status drop down menu. This menu is populated from the statuses created in Admin → Server Administration → Copy Statuses.
+.. *Reference?*:  Yes or No-- indicate if the item is a reference item.
+.. *OPAC Visible?*: Yes or No-- indicate if the item should be visible in the OPAC.
+.. *Price*:  Enter the price of the item.
+.. *Deposit?*:  Yes or No-- indicate if patrons must place a deposit on the copy before they can use it.
+.. *Deposit Amount*:  Enter a Deposit Amount if patrons must place a deposit on the copy before they can use it.
+.. *Quality*:  Good or Damaged-- indicate the physical condition of the item.
+. Click *Save*.
+. The new serial copy template will now appear in the list of templates.
+
+image::media/serials_ct1.PNG[]
+
+
+Modifying a Serial Copy Template
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+To modify a Serial Copy Template:
+
+. Select the template to modify by checking the box for the template or clicking anywhere on the template row.  Go to *Actions->Edit Template* or _right-click_ on the template row and select *Edit Template*.
+. The dialog box will appear.  Make any changes to the item attributes and click *Save*.
+
+
+Deleting a Serial Copy Template
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+To delete a Serial Copy Template:
+
+. Select the template to modify by checking the box for the template or clicking anywhere on the template row.
+. Go to *Actions->Delete Template* or _right-click_ on the template row and select *Delete Template*.
+
+NOTE: Serials copy templates that are being used by subscriptions cannot be deleted.
+
+
+Prediction Pattern Templates
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+Prediction pattern templates allow you to create templates for prediction patterns that can be shared with other staff users in your library branch, system, or throughout the consortium.  Prediction patterns are used to predict issues on serials subscriptions.  Templates can be created in the Administration module, as described below, and can also be created and shared directly in a subscription.
+
+
+Creating a Prediction Pattern Template
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+To create a template, go to *Administration->Serials Administration->Prediction Pattern Templates*:
+
+. Click *New Record* in the upper-right hand corner.  A dialog box called _Prediction Pattern Template_ will appear.
+. Assign a _Name_ to the template, such as "Monthly", to create a monthly publication pattern.
+. Next to Pattern Code click *Pattern Wizard*.  The Prediction Pattern Code Wizard will appear.  This wizard has five tabs that will step you through creating a prediction pattern for your publication.
+
+.. Enumeration Labels
+... _If the publication does not use enumeration and instead only uses dates_, select the radio button adjacent to _Use Calendar Dates Only_ and click *Next* in the upper right-hand corner and go to b. Chronology Display in this document.
+... _If the publication uses enumerations (commonly used)_, select the radio button adjacent to _Use enumerations_. The enumerations conform to $a-$h of the 853,854, and 855 MARC tags.
+... Enter the first level of enumeration in the field labeled _Level 1_.  A common first level enumeration is volume, or "v.".  If there are additional levels of enumeration, click *Add Level*.
+... A second field labeled _Level 2_ will appear.  Enter the second level of enumeration in the field.  A common second level enumeration is number, or "no.".
+.... Select if the second level of enumeration is a set _Number_, _Varies_, or is _Undetermined_.
+.... If _Number_ is selected (commonly used):
+..... Enter the number of bibliographic units per next higher level (e.g. 12 no. per v.).  This conforms to $u in the 853, 854, and 855 MARC tags.
+..... Select the radio button for the enumeration scheme: _Restarts at unit completion_ or _Increments continuously_.  This conforms to $v in the 853, 854, and 855 MARC tags.
+.... You can add up to six levels of enumeration.
+... Check the box adjacent to _Add alternative enumeration_ if the publication uses an alternative enumeration.
+... Check the box adjacent to _First level enumeration changes during subscription year_ to configure calendar changes if needed.  A common calendar change is for the first level of enumeration to increment every January.
+.... Select when the Change occurs from the drop down menu: _Start of the month_, _Specific date_, or _Start of season_.
+.... From the corresponding drop down menu select the specific point in time at which the first level of enumeration should change.
+.... Click *Add more* to add additional calendar changes if needed.
+... When you have completed the enumerations, click *Next* in the upper right-hand corner.
+
+
+image::media/serials_wizard1.PNG[]
+
+
+.. Chronology Display
+... To use chronological captions for the subscription, check the box adjacent to _Use Chronology Captions?_
+... Choose a chronological unit for the first level.  If you want to display the term for the unit selected, such as "Year" and "Month" next to the chronology caption in the catalog, then select the checkbox for Display level descriptor? (not commonly used).
+... To add additional levels of chronology for display, click *Add level*.
+.... Note: Each level that you add must be a smaller chronological unit than the previous level (e.g. Level 1 = Year, Level 2 = Month).
+... Check the box adjacent to _Use Alternative Chronology Captions?_ If the publication uses alternative chronology.
+... After you have completed the chronology caption, click *Next* in the upper-right hand corner.
+
+
+image::media/serials_wizard2.PNG[]
+
+
+.. MFHD Indicators
+... *Compression Display Options*: 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.
+... *Caption Evaluation*: Choose the appropriate caption evaluation from the drop down menu.  Caption Evaluation corrdesponds to the second indicator in the 853 tag.
+... Click *Next* in the upper right hand corner.
+
+
+image::media/serials_wizard3.PNG[]
+
+
+.. Frequency and Regularity
+... Indicate the frequency of the publication by selecting one of the following radio buttons:
+.... *Pre-selected* and choose the frequency from the drop down menu.
+.... *Use number of issues per year* and enter the total number of issues in the field.
+... If the publication has combined, skipped, or special issues, that should be accounted for in the publication pattern, check the box adjacent to _Use specific regularity information?_.
+.... From the first drop down menu, select the appropriate publication information: _Combined_, _Omitted_, or _Published_ issues.
+.... From the subsequent drop down menus, select the appropriate frequency and issue information.
+.... Add additional regularity rows as needed.
+.... For a Combined issue, enter the relevant combined issue code.  E.g., for a monthly combined issue, enter 02/03 to specify that February and March are combined.
+... After you have completed frequency and regularity information, click *Next* in the upper-right hand corner.
+
+
+image::media/serials_wizard4.PNG[]
+
+
+.. Review
+... Review the Pattern Summary to verify that the pattern is correct.  You can also click on the expand arrow icon to view the _Raw Pattern Code_.
+... If you want to share this pattern, assign it a name and select if it will be shared with your library, the system, or across the consortium.
+...  Click *Save*.
+
+
+image::media/serials_wizard5.PNG[]
+
+
+. Back in the Prediction Pattern Template dialog box, select the Owning Library, which will default to the workstation library.
+. If you want to share the template, set the Share Depth to indicate how far out into your consortium the template will be shared.
+
+
+image::media/serials_wizard6.PNG[]
+
+
+. The Prediction Pattern will now appear in the list of templates and can be used to create predictions for subscriptions.
+
+NOTE: Prediction Patterns can be edited after creation as long as all predicted issues have the status of "Expected".  Once an issue is moved into a different status, the Prediction Pattern cannot be changed.
diff --git a/docs/serials/C-serials_workflow.adoc b/docs/serials/C-serials_workflow.adoc
new file mode 100644
index 0000000..543a788
--- /dev/null
+++ b/docs/serials/C-serials_workflow.adoc
@@ -0,0 +1,142 @@
+Serials Module
+--------------
+
+The Serials Module can be used to create subscriptions, distributions, streams, and prediction patterns.  As well as to generate predictions and receive issues as they come in to the library.
+
+
+To access the Serials Module, go to a serials record in the catalog, and click on *Serials->Manage Subscriptions*.  This will open the serials interface for that particular record.  In this interface you can:
+
+. Create and manage subscriptions
+. Create and manage predictions
+. Create and manage issues
+. Create and manage MFHDs
+
+
+image::media/serials_sub0.PNG[]
+
+
+Create a Subscription
+~~~~~~~~~~~~~~~~~~~~~
+
+. From a bibliographic record, go to *Serials->Manage Subscriptions*, view the _Manage Subscriptions_ tab. 
+. Within the _Manage Subscriptions_ tab, create a new subscription by clicking *New Subscription*.  The subscription editor will appear:
+.. Select the _Owning Library for_ the subscription.  The owning library indicates the organizational unit(s) whose staff can use this subscription. The rule of parental inheritance applies to this list. For example, if a system is made the owner of a subscription, then users, with appropriate permissions, at the branches within the system could also use this subscription.  This field is required.
+.. Enter the date that the subscription begins in the _Start Dat_e field. This field is required.
+.. An _End Date_ for the subscription may also be entered, but it is not required.
+.. Optionally, enter an _Expected Offset_.  This is the difference between the nominal publishing date of an issue and the date that you expect to receive your copy. 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.
+.. Next, create a Distribution for the subscription by selecting the Library for the distribution.  Distributions identify the branches that will receive copies of a serial.
+... Note: If the Owning Library of the subscription was set at the branch level, the Library will be the same as the Owning Library.  If the Owning Library of the subscription was set at the system level, the Library will be set to the holdings library.
+.. Enter a Label for 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.
+.. Select the preferred _OPAC Display for holdings_: Chronological or Enumeration.
+.. Select the _Receiving Template_ that will be applied to items as they are received.  The receiving templates are configured in Administration->Serials Administration->Serial Copy Templates.
+.. Next, create a Stream by assigning a label to the stream in the _Send to_ field. The stream indicates the number of copies that should be sent to the distribution library.   You can click *Add copy stream* if the library will receive multiple copies of the serial.
+. After the subscription, distribution, and copy information is configured, click *Save* and go to the _Manage Predictions_ tab to create the prediction pattern that will be used to generate predictions for this title.
+
+NOTE: After creating a subscription, you can use the Actions menu to take a variety of actions with the subscription, such as adding Subscription or Distribution Notes, linking it to an MFHD record, or creating routing lists.
+
+
+image::media/serials_sub1.PNG[]
+
+
+Create and Manage Predictions
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+From the _Manage Predictions_ tab you can create a new prediction pattern from scratch, use an existing pattern template, or use an existing pattern template as the basis for a new prediction pattern.
+
+Predict Issues Using a New Prediction Pattern
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+. Within the _Manage Predictions_ tab, _Select [a] subscription_ to work on from the drop down menu.
+. To create a new prediction pattern, click *Add New*.
+.. The box next to *Active* will be checked by default.
+.. Select the _Type of pattern_ from the drop down menu and click *Create Pattern*.  The Pattern Wizard will appear.
+.. Follow the steps in the section _Creating a Pattern Template_ in this documentation to create a new pattern using the wizard.
+
+
+image::media/serials_sub2.PNG[]
+
+
+. After creating the pattern in the wizard, click *Create*.  The new prediction pattern will now appear under Existing Prediction Patterns.
+. To create predictions, click *Predict New Issues*.
+
+NOTE: You can also predict new issues from the _Manage Issues_ tab.
+
+
+image::media/serials_sub3.PNG[]
+
+
+. A dialog box called _Predict New Issues: Initial Values_ will appear.
+.. Select the _Publication date_ for the subscription.  This will be publication date of the first issue you expect to receive.
+.. The _Type_ will correspond to the type of prediction pattern selected.
+.. Enter any _Enumeration labels_ for the first expected issue.
+.. Enter any _Chronology labels_ for the first expected issue.
+.. Enter the _Prediction count_.  This is the number of issues that you want to predict.
+. Click *Save*.
+. Evergreen will generate the predictions and bring you to the _Manage Issues_ tab to review the predicted issues.
+
+
+image::media/serials_sub4.PNG[]
+
+
+Predict Issues Using a Prediction Pattern Template
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+. Within the _Manage Predictions_ tab, *Select [a] subscription* to work on from the drop down menu.
+. _Select a template_ from the drop down menu that appears under the Add New button and click *Create from Template*.  The pattern information will appear below the drop down menu.
+
+
+image::media/serials_sub5.PNG[]
+
+
+. If you want to use the pattern "as is" click *Create*.
+.. If you want to review or modify the pattern, click *Edit Pattern*.  The Pattern Wizard will appear.
+.. The Pattern Wizard  will be pre-populated with the pattern template selected.  Follow the steps in the section Creating a Pattern Template in this documentation to modify the template or click *Next* on each tab to review the template.
+.. After modifying or reviewing the pattern in the wizard, click *Create*.  The prediction pattern will now appear under Existing Prediction Patterns.
+. To create predictions, click *Predict New Issues*.
+.. Note: you can also predict new issues from the _Manage Issues_ tab.
+. A dialog box called _Predict New Issues: Initial Values_ will appear.
+.. Select the _Publication date_ for the subscription.  This will be publication date of the first issue you expect to receive.
+.. The _Type_ will correspond to the type of prediction pattern selected.
+.. Enter any _Enumeration labels_ for the first expected issue.
+.. Enter any _Chronology labels_ for the first expected issue.
+.. Enter the _Prediction count_.  This is the number of issues that you want to predict.
+. Click *Save*.
+. Evergreen will generate the predictions and bring you to the _Manage Issues_ tab to review the predicted issues.
+
+
+Predict Issues Using a Prediction Pattern from a Bibliographic and/or MFHD Record
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+Evergreen can also generate a prediction pattern from existing MFHD records attached to a serials record and from MFHD patterns embedded directly in the bibliographic record.
+
+. Within the _Manage Predictions_ tab, *Select [a] subscription* to work on from the drop down menu.
+. Click *Import from Bibliographic and/or MFHD Records*.
+
+
+image::media/serials_sub6.PNG[]
+
+
+. A dialog box will appear that presents the available MFHD records and the prediction pattern that will be imported.
+. Check the box adjacent to the MFHD record that you would like to import and click *Import*.  The new prediction pattern will now appear under _Existing Prediction Patterns_.
+
+
+image::media/serials_sub7.PNG[]
+
+
+. If you want to review or modify the pattern, click *Edit Pattern*.  The Pattern Wizard will appear.
+.. The Pattern Wizard  will be pre-populated with the pattern from the MFHD selected.  Follow the steps in the section . Creating a Pattern Template.  in this documentation to modify the template or click *Next* on each tab to review the template.
+. To create predictions, click *Predict New Issues*.
+.. Note: you can also predict new issues from the _Manage Issues_ tab.
+. A dialog box called _Predict New Issues: Initial Values_ will appear.
+.. Select the _Publication date_ for the subscription.  This will be publication date of the first issue you expect to receive.
+.. The _Type_ will correspond to the type of prediction pattern selected.
+.. Enter any _Enumeration labels_ for the first expected issue.
+.. Enter any _Chronology labels_ for the first expected issue.
+.. Enter the _Prediction count_.  This is the number of issues that you want to predict.
+. Click *Save*.
+. Evergreen will generate the predictions and bring you to the _Manage Issues_ tab to review the predicted issues.
+
+
+Manage Issues
+^^^^^^^^^^^^^
+After generating predictions in the _Manage Predictions_ tab, you will see a list of the predicted issues in the Manage Issues tab.  A variety of actions can be taken in this tab, including receiving issues, predicting new issues, adding special issues.
+
+
+image::media/serials_sub8.PNG[]
diff --git a/docs/serials/C-subscription-SCV.adoc b/docs/serials/C-subscription-SCV.adoc
deleted file mode 100644
index a76f1c4..0000000
--- a/docs/serials/C-subscription-SCV.adoc
+++ /dev/null
@@ -1,218 +0,0 @@
-
-Serials Control View
---------------------
-
-As of Evergreen 2.4, the Serial Control View incorporates the Alternate Serial Control interface in the Subscription editor. 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.4.
-
-Create a Subscription
-~~~~~~~~~~~~~~~~~~~~~
-A subscription is designed to hold all information related to a single serial title.  Therefore, each library is likely to have only one subscription per serial title.
-
-image::media/scv-combined-sub.png[Subscription]
-
-. Click the *Subscriptions* tab.
-. In the tree on the left, select the branch that will own the subscription.
-. Right-click to show the *Actions* menu, or click *Actions for Selected Row*, and click *Add Subscription*.
-. Enter the date that the subscription begins in the Start Date field.
-. Enter the date that the subscription ends in the End Date field. This field is optional.
-. 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 field. 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.
-. When finished, click *Save*. Or to exit the editor without saving, click *Cancel*.
-
-[NOTE]
-You can add notes to the subscription by clicking *View/Edit Notes*. These notes can also be accessed from the Items tab by right-clicking on an item and choosing *View Sub. Notes*. Also, the Notes column in the Items tab displays the total notes of each kind (Item notes, then Distribution notes, then Subscription notes).
-
-Create a Distribution
-~~~~~~~~~~~~~~~~~~~~~
-
-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.
-
-From the new combination Serial Control View
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-image::media/scv-combined-dist.png[Distribution]
-
-. Choose a subscription from the list on the left
-. In the panel on the right, click the *Distributions* tab
-. Click the *New Distribution* button
-. Enter your desired label in the Label field. 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.
-. Select a Holding Library from the drop down menu. The holding library is the branch that will receive the copies.
-. Select a Display Grouping
-. Choose a Legacy Record Entry to attach to this serial record. 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 a copy template from the Receive Unit Template drop down menu. This menu is populated with the copy templates that you created in Copy Template Editor.
-. Select a Summary method. This determines how the Holdings Summary will treat the Legacy Record Entry (i.e. MFHD record) in relation to the Serial Control holdings data.
-  * Add to record entry - Displays the MFHD holdings summary first, followed by the summary generated from the Serial Control received issues
-  * Use record entry only - Displays only the MFHD holdings summary
-  * Do not use record entry - Displays only the holdings summary generated from Serial Control received issues
-  * Merge with record entry - Merges the two holdings summaries into a single statement
-. Enter a Unit label prefix. This information will display in Serial Control View when the items are received, but it does not print in the Spine Label printing interface.
-. Enter a Unit label suffix. This information will display in Serial Control View when the items are received, but it does not print in the Spine Label printing interface.
-. Click the *Save* button to finish.
-
-[NOTE]
-Label, Holding Library, and Receive Unit Template are required fields when creating a distribution.
-
-[NOTE]
-Streams are created automatically in the Serial Control View. For information on using Streams in the combination Serial Control View, see <<_creating_a_stream,Creating a Stream>>.
-
-From the original Serial Control View
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-image::media/scv-distr.png[Distribution]
-
-. Click *Distributions* beneath the subscription from the tree on the left. Right click to show the *Actions* menu, or click *Actions for Selected Rows*, and click *Add distribution*.
-. 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.
-. Select a Summary method. This determines how the Holdings Summary will treat the Legacy Record Entry (i.e. MFHD record) in relation to the Serial Control holdings data.
-  * Add to record entry - Displays the MFHD holdings summary first, followed by the summary generated from the Serial Control received issues
-  * Use record entry only - Displays only the MFHD holdings summary
-  * Do not use record entry - Displays only the holdings summary generated from Serial Control received issues
-  * Merge with record entry - Merges the two holdings summaries into a single statement
-. 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 in the Spine Label printing interface.
-. 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 in the Spine Label printing interface.
-. The holding library is filled in by default and is the library to which you attached the subscription.
-. 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.
-. 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.
-. 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.
-. Receive Unit Template -  The template that should be applied to copies when they are received. Select a template from the drop down menu.
-. Bind Unit Template - The template that should be applied to copies when they are bound. Select a template from the drop down menu.
-. When finished, click *Create Distribution(s)* in the bottom right corner of the screen.
-. A confirmation message appears. Click *OK*.
-
-[NOTE]
-You can add notes to the distribution by clicking *Distribution Notes*. These notes can also be accessed from the Items tab by right-clicking on an item and choosing *View Dist. Notes*. Also, the Notes column in the Items tab displays the total notes of each kind (Item notes, then Distribution notes, then Subscription notes).
-
-Create Captions and Patterns
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-From the new combination Serial Control View
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-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.
-
-. In the panel on the right, click the *Captions and Patterns* tab.
-. Click *Add New*.
-. In the Type drop down menu, select the MARC tag to which you would like to add data.
-. In the Pattern Code text 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.
-. The Caption and Pattern is Active by default. You can deactivate it at any time by unchecking the box and clicking *Save Changes*. Only one active caption and pattern is allowed per type.
-. Click *Save Changes* to finish.
-. To delete a pattern, simply click the red X button.
-
-From the original Serial Control View
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-. Click *Captions and patterns* beneath the subscription from the tree on the left. Right click to the show the *Actions* menu, or click *Actions for Selected Rows*, and click *Add Caption/Pattern*.
-. Apply a type, which can be for basic subscription, supplements, or indices
-. Apply active.  Only one active caption and pattern is allowed per type
-. In the Pattern Code box, you can enter a JSON representation of the 85X tag by hand, or you can click the Pattern Code Wizard to enter the information in a user-friendly format.
-
-Use the Pattern Code Wizard
-^^^^^^^^^^^^^^^^^^^^^^^^^^^
-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.
-
-To add a pattern code, click *Wizard*.
-
-Page 1: Enumerations
-++++++++++++++++++++
-
-image::media/cap-wiz-num.jpg[Enumeration]
-
-. To add an enumeration, check the box adjacent to Use enumerations.. The enumerations conform to $a-$h of the 853,854, and 855 MARC tags.
-. A field for the First level will appear. Enter the enumeration for the first level. A common first level enumeration is volume, or "v."
-. Click *Add Enumeration*.
-. A field for the Second level will appear. Enter the enumeration for the second level. A common first level enumeration is number, or "no."
-. Enter the number of bibliographic units per next higher level. This conforms to $u in the 853, 854, and 855 MARC tags.
-. Choose the enumeration scheme from the drop down menu. This conforms to $v in the 853, 854, and 855 MARC tags.
-+
-[NOTE]
-You can add up to six levels of enumeration.
-+
-. Add Alternate Enumeration if desired.
-. When you have completed the enumerations, click *Next*.
-
-
-Page 2: Calendar
-++++++++++++++++
-
-image::media/cap-wiz-cal.jpg[Enumeration]
-
-. To use months, seasons, or dates in your caption, check the box adjacent to Use calendar changes.
-. Identify the point in the year at which the highest level enumeration caption changes.
-. In the Type drop down menu, select the points during the year at which you want the calendar to restart.
-. In the Point drop down menu, select the specific time at which you would like to change the calendar
-. To add another calendar change, click *Add Calendar Change*. There are no limits on the number of calendar changes that you can add.
-. When you have finished the calendar changes, click *Next*.
-
-Page 3: Chronology
-++++++++++++++++++
-
-image::media/cap-wiz-chron.jpg[Chronology]
-
-. To add chronological units to the captions, check the box adjacent to Use chronology captions.
-. Choose a chronology for the first level. If you want to display the terms such as "year" and "month" next to the chronology caption in the catalog, then check the box beneath Display in holding field.
-. To include additional levels of chronology, click *Add Chronology Caption*. Each level that you add must be smaller than the previous level.
-. After you have completed the chronology caption, click *Next*.
-
-Page 4: Compress and Expand Captions
-++++++++++++++++++++++++++++++++++++
-
-image::media/cap-wiz-freq.jpg[Compress or Expand]
-
-. 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.
-. Choose the appropriate caption evaluation from the drop down menu.
-. 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, recommended practice is that you use only regular frequencies. Planned development will create an additional step to aid in the creation of irregular frequencies.
-. Click *Next*.
-
-Page 5: Regularity Information 
-++++++++++++++++++++++++++++++
-
-image::media/cap-wiz-chan.jpg[Changes]
-	
-. If needed, check box for Use specific regularity information
-. Choose the appropriate information for combined, omitted or published issues
-. Choose the appropriate frequency and issue
-. Add additional rows as required
-
-Page 5: Finish Captions and Patterns
-++++++++++++++++++++++++++++++++++++
-
-. To complete the wizard, click *Create Pattern Code*.
-. Return to Subscription Details.
-. Confirm that the box adjacent to Active is checked. Click *Save Changes*. The row is now highlighted gray instead of orange.
-	
-Creating an Issuance
-~~~~~~~~~~~~~~~~~~~~
-
-The Issuances function enables you to manually create an issue. Evergreen will use the initial issue that you manually create to predict future issues.
-
-From the new combination Serial Control View
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-image::media/scv-combined-iss.png[Issuance]
-
-. In the panel on the right, click the *Issuances* tab.
-. Click *New Issuance*.
-. The Subscription, Creator, and Editor fields contain subscription and user IDs, respectively. These fields are disabled because Evergreen automatically fills in these fields.
-. 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.
-. Enter the Date Published of the issuance. 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.
-. Select a Caption/Pattern from the drop down menu. The numbers in the drop down menu correspond to the IDs of the caption/patterns that you created.
-. The Holding Type appears by default and corresponds to the Type that you selected when you created the Caption/Pattern.
-. In the holding code area of the New Issuance dialog, click *Wizard*. The Wizard enables you to add holdings information.
-. Enter the volume of the item in hand in the v. field.
-. Enter the number of the item in hand in the no. field.
-. Enter the year of publication in the Year field.
-. 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.
-. Enter the day of publication in the day field if applicable.
-. Click *Compile* to generate the holdings code.
-. Click *Save* to finish.
-
-From the original Serial Control View
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-image::media/scv-iss.png[Issuance]
-
-. Click *Issuances* beneath the subscription from the tree on the left. Right click to show the *Actions* menu, or click *Actions for Selected Rows*, and click *Add Issuance*.
-. As of Evergreen 2.2, the Issuance editor is the same as mentioned above in the new combination view.
-
-Generate Prediction
-~~~~~~~~~~~~~~~~~~~
-
-. Select the Subscription in the tree on the left.
-. Right-click to show the *Actions* menu, or click *Actions for Selected Row*, then click *Make predictions*.
-. A pop up box will ask you how many items you want to predict. Enter the number, and click *OK*.
-. A confirmation message will appear. Click *OK*.
-. To view the predicted issues, select a Subscription from the tree on the left, then click the *Issuances* tab in the panel on the right.
diff --git a/docs/serials/D-Receiving.adoc b/docs/serials/D-Receiving.adoc
new file mode 100644
index 0000000..6a9855c
--- /dev/null
+++ b/docs/serials/D-Receiving.adoc
@@ -0,0 +1,88 @@
+Receiving
+---------
+Issues can be received through the _Manage Issues_ tab or through the _Quick Receive_ option located in the bibliographic record display.  While receiving, staff can select if issues should be barcoded during receipt.
+
+
+Quick Receive
+~~~~~~~~~~~~~
+. From a serials record in the catalog, go to *Serials->Quick Receive*.
+. A dialog box will appear.  Select the _Library_ and _Subscription_ for which you are receiving issues from the drop down menu and click *OK/Continue*.
+. A _Receive items_ dialog box will appear with the next expected issue.
+.. To receive the item(s) and barcode them:
+... The _Copy Location_ and _Circulation Modifier_ will be pre-populated from the Receive Template associated with the Distribution.  Changes can be made to the pre-populated information.
+.... Note: Copy location, call number, and circulation modifier can be applied to multiple copies in batch using the batch modify.
+... *Call Number*: Enter a call number.  Any item with a barcode must also have a call number.
+... *Barcode*:  Scan in the barcode that will be affixed to the issue.
+... The box adjacent to _Receive the issue_ will be checked by default.
+... Check the box adjacent to _Routing List_ to print an existing routing list.
+... Click *Save* to receive the issue.  The Status of the issue will update to "Received" and a Date Received will be recorded.  The barcoded copy will now appear in the holdings area of the catalog and the Holdings Summary in the Issues Held tab in the catalog will reflect the newly received issue.
+.. To receive the item(s) without barcoding them:
+... Uncheck the box adjacent to _Barcode Items_ and click *Save*.  The Holdings Summary in the Issues Held tab in the catalog will reflect the newly received issue.
+
+
+image::media/serials_sub9.PNG[]
+
+
+Receiving from the Manage Issues tab
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+The Manage Issues tab can be used to receive the next expected issue and to receive multiple expected issues.  This tab can be accessed by retrieving the serial record, going to *Serials->Manage Subscriptions*, and selecting the _Manage Issues_ tab.
+
+
+Receive Next Issue and Barcode
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+. Within the _Manage Issues_ tab, *Select [a] subscription* to work on from the drop down menu.  The list of predicted issues for the subscription will appear.
+. Check the box adjacent to _Barcode on receive_.
+. Click *Receive Next*.
+. A _Receive items_ dialog box will appear with the next expected issue and item(s).
+. The _Copy Location_ and _Circulation Modifier_ will be pre-populated from the Receive Template associated with the Distribution.  Changes can be made to the pre-populated information.
+. *Call Number*: Enter a call number.  Any item with a barcode must also have a call number.
+. *Barcode*: Scan in the barcode that will be affixed to the item(s).
+. The box to _Receive the item(s)_ will be checked by default.
+. Check the box adjacent to _Routing List_ to print an existing routing list.
+. Click *Save* to receive the item(s).  The Status of the issue will update to "Received" and a Date Received will be recorded.  The barcoded item(s) will now appear in the holdings area of the catalog and the Holdings Summary in the Issues Held tab in the catalog will reflect the newly received issue.
+
+
+Receive Next Issue (no barcode)
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+. In the _Manage Issues_ tab, make sure the box adjacent to _Barcode on receive_ is unchecked and click *Receive Next*.
+. A _Receive items_ dialog box will appear with the message "Will receive # item(s) without barcoding."
+. Click *OK/Continue* to receive the issue.  The Status of the issue will update to "Received" and a Date Received will be recorded.  The Holdings Summary in the Issues Held tab in the catalog will reflect the newly received issue.
+
+
+image::media/serials_sub10.PNG[]
+
+
+Batch Receiving
+~~~~~~~~~~~~~~~
+Multiple issues can be received at the same time using the _Manage Issues_ tab.
+
+
+Batch Receive and Barcode
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+. Within the _Manage Issues tab_, *Select [a] subscription* to work on from the drop down menu.  The list of predicted issues for the subscription will appear.
+. Check the box adjacent to _Barcode on receive_.
+. Check the boxes adjacent to the expected issues you want to receive.
+. Go to *Actions->Receive selected* or _right-click_ on the rows and select *Receive selected* from the drop down menu.
+. A _Receive items_ dialog box will appear with the selected issues and items.
+. The _Copy Location_ and _Circulation Modifier_ will be pre-populated from the Receive Template associated with the Distribution.  Changes can be made to the pre-populated information.
+. *Call Number*: Enter a call number.  Any item with a barcode must also have a call number.
+. *Barcode*: Scan in the barcodes that will be affixed to the items.
+. The box to _Receive_ the items will be checked by default.
+. Check the box adjacent to _Routing List_ to print an existing routing list.
+. Click *Save* to receive the items.  The Status of the items will update to "Received" and a Date Received will be recorded.  The barcoded items will now appear in the holdings area of the catalog and the Holdings Summary in the Issues Held tab in the catalog will reflect the newly received issues.
+
+
+image::media/serials_sub11.PNG[]
+
+
+Receive multiple issues (no barcode)
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+. Within the _Manage Issues_ tab, *Select [a] subscription* to work on from the drop down menu.  The list of predicted issues for the subscription will appear.
+. Make sure the box next to _Barcode on receive_ is unchecked and check the boxes adjacent to the expected issues you want to receive.
+. A _Receive items_ dialog box will appear with the message "Will receive # item(s) without barcoding."
+. Click *OK/Continue* to receive the issues.  The Status of the issue will update to "Received" and a Date Received will be recorded.  The Holdings Summary in the Issues Held tab in the catalog will reflect the newly received issues.
+
diff --git a/docs/serials/D-subscription-ASCV.adoc b/docs/serials/D-subscription-ASCV.adoc
deleted file mode 100644
index ade97ed..0000000
--- a/docs/serials/D-subscription-ASCV.adoc
+++ /dev/null
@@ -1,216 +0,0 @@
-Alternate Serial Control View
------------------------------
-
-Using the Alternate Serial Control View, you can create a subscription, a distribution, a stream, and a caption and pattern, and you can generate predictions and receive issues. To access Alternate Serial Control View, open a serials record, and click *Actions for this Record* -> *Alternate Serial Control*. This opens the Subscriptions interface
-
-. Create a subscription
-. Create a distribution
-. Create a a stream (within the distribution)
-. Create a caption and pattern (or import from bibliographic or legacy serial records)
-. Create at least the first issuance and generate predictions
-
-Creating a Subscription
-~~~~~~~~~~~~~~~~~~~~~~~
-
-A subscription is designed to hold all information related to a single serial title.  Therefore, each library is likely to have only one subscription per serial title.
-
-image::media/ascv-sub.jpg[Creating a Subscription]
-
-. Add new subscriptions to a serials record that exists in the catalog.
-. Create a subscription
-. Click New Subscription.
-. Select an owning library. The owning library indicates the organizational unit(s) whose staff can use this subscription. This menu is populated with the shortnames that you created for your libraries in the organizational units tree in Administration -> Server Administration -> Organizational Units. The rule of parental inheritance applies to this list. For example, if a system is made the owner of a subscription, then users, with appropriate permissions, at the branches within the system could also use this subscription.
-. Enter the date that the subscription begins in the start date. Recommended practice is that you select the date from the drop down calendar although you can manually enter a date. Owning library and start date are required fields in the new subscription pop up box.
-. Enter the date that the subscription ends in the end date. Recommended practice is to select a date from the drop down calendar, but you can manually enter a date, also.
-. 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.
-. Click Save.
-
-After you save the subscription, it will appear in a list with a hyperlinked ID number. Use the drop down menu at the top of the screen to view subscriptions at other organizations.
-
-Creating a Distribution
-~~~~~~~~~~~~~~~~~~~~~~~
-
-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.
-
-image::media/ascv-dist1.png[Creating a Distribution]
-
-. Click the Distributions tab.
-. Click New Distribution.
-. Enter a name for the distribution in the Label field. 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.
-. Select a holding library from the drop down menu. The holding library is the branch that will receive the copies.
-. Select a copy template from the Receive Unit Template drop down menu. This menu is populated with the copy templates that you created in Copy Template Editor.
-+
-[NOTE]
-Label, Holding Library, and Receive Unit Template are required fields in the new distribution pop up box.
-+
-. Ignore the fields, Unit Label Prefix and Unit Label Suffix. These fields are not functional in Alternate Serial Control View.
-+
-image::media/ascv-dist2.png[New Distribution Form]
-+
-. Click Save. The distribution will appear in a list in the Distributions tab in the Subscription Details.
-
-Creating a Stream
-~~~~~~~~~~~~~~~~~
-
-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.
-
-. Click the hyperlinked title of the distribution. The number of streams that have already been created for this distribution displays adjacent to the title. 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 stream and assign it a routing label.
-. Click New Stream
-. 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.
-. Click Save.
-+
-[NOTE]
-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.
-+
-. Click Create Many Streams.
-. Enter the number of streams that you want to create in the How many. Field.
-. Click Create.
-
-Creating a Routing List
-^^^^^^^^^^^^^^^^^^^^^^^
-
-Within Alternate Serial Control View, you have the option to create routing lists for selected streams. Routing lists enable you to designate specific users and/or departments that serial items need to be routed to upon receiving. These routing lists can now display user addresses when you receive the items. This feature is particularly useful for working with homebound patrons.
-
-Create a Routing List in Alternate Serial Control View that will display the User's Address:
-
-. Select the checkbox for the stream that needs a routing list
-
-. Click *Routing List for Selected Stream*
-
-. Click the *Reader (barcode):* radio button and enter the user's barcode into the field
-
-. Click *Add*
-
-. Click *Save Changes*
-
-image::media/Added_User_to_Routing_Slip.jpg[]
-
-When you receive the item in *Serials Batch Receive* or from within Alternate Serial Control's *Batch Item Receive*, the routing list will print the user's address. For more information, see the chapter on Batch Receiving.
-
-image::media/Address_on_Routing_Slip.jpg[]
-
-The default template can be configured to not include the user's mailing or billing address on the routing list. Libraries already using customized templates will not be affected.
-
-Creating a Caption and Pattern
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-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.
-
-. Open the Subscription Details.
-. Click the Captions and Patterns tab.
-. Click Add Caption and Pattern.
-. In the Type drop down box, select the MARC tag to which you would like to add data.
-. 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.
-. 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.
-
-
-[NOTE]
-A subscription may have multiple captions and patterns listed in the subscription details, but only one Caption and Pattern can be active at any time. If you want to add multiple patterns, e.g. for Basic and Supplement, Click Add Caption and Pattern.
-
-
-Use the Pattern Code Wizard
-^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-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.
-
-To add a pattern code, click Wizard.
-
-Page 1: Enumerations
-++++++++++++++++++++
-
-image::media/cap-wiz-num.jpg[Enumeration]
-
-. To add an enumeration, check the box adjacent to Use enumerations. The enumerations conform to $a-$h of the 853,854, and 855 MARC tags.
-. A field for the First level will appear. Enter the enumeration for the first level. A common first level enumeration is volume, or "v."
-. Click Add Enumeration.
-. A field for the Second level will appear. Enter the enumeration for the second level. A common first level enumeration is number, or "no."
-. Enter the number of bibliographic units per next higher level. This conforms to $u in the 853, 854, and 855 MARC tags.
-. Choose the enumeration scheme from the drop down menu. This conforms to $v in the 853, 854, and 855 MARC tags.
-+
-[NOTE]
-You can add up to six levels of enumeration.
-+
-. Add Alternate Enumeration if desired.
-. When you have completed the enumerations, click Next.
-
-Page 2: Calendar
-++++++++++++++++
-
-image::media/cap-wiz-cal.jpg[Enumeration]
-
-. To use months, seasons, or dates in your caption, check the box adjacent to Use calendar changes.
-. Identify the point in the year at which the highest level enumeration caption changes.
-. In the Type drop down menu, select the points during the year at which you want the calendar to restart.
-. In the Point drop down menu, select the specific time at which you would like to change the calendar
-. To add another calendar change, click Add Calendar Change. There are no limits on the number of calendar changes that you can add.
-. When you have finished the calendar changes, click Next.
-
-Page 3: Chronology
-++++++++++++++++++
-
-image::media/cap-wiz-chron.jpg[Chronology]
-	
-. To add chronological units to the captions, check the box adjacent to Use chronology captions.
-. Choose a chronology for the first level. If you want to display the terms, "year" and "month" next to the chronology caption in the catalog, then check the box beneath Display in holding field.
-. To include additional levels of chronology, click Add Chronology Caption. Each level that you add must be smaller than the previous level.
-. After you have completed the chronology caption, click Next.
-
-Page 4: Compress and Expand Captions
-++++++++++++++++++++++++++++++++++++
-
-image::media/cap-wiz-freq.jpg[Compress or Expand]
-
-. 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.
-. Choose the appropriate caption evaluation from the drop down menu.
-. 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, recommended practice is that you use only regular frequencies. Planned development will create an additional step to aid in the creation of irregular frequencies.
-. Click Next.
-
-Page 5: Regularity Information 
-++++++++++++++++++++++++++++++
-
-image::media/cap-wiz-chan.jpg[Changes]
-
-. If needed, check box for Use specific regularity information
-. Choose the appropriate information for combined, omitted or published issues
-. Choose the appropriate frequency and issue
-. Add additional rows as required
-
-Page 5: Finish Captions and Patterns
-++++++++++++++++++++++++++++++++++++
-
-. To complete the wizard, click Create Pattern Code.
-. Return to Subscription Details.
-. Confirm that the box adjacent to Active is checked. Click Save Changes. The row is now highlighted gray instead of orange.
-
-Creating an Issuance
-~~~~~~~~~~~~~~~~~~~~
-
-The Issuances tab enables you to manually create an issue. Evergreen will use the initial issue that you manually create to predict future issues.
-
-image::media/ascv-issues.jpg[Changes]
-
-. Click the Issuances tab in the Subscription Details.
-. Click New Issuance.
-. The Subscription, Creator, and Editor fields contain subscription and user IDs, respectively. These fields are disabled because Evergreen automatically fills in these fields.
-. 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.
-. 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.
-. Select a Caption/Pattern from the drop down menu. The numbers in the drop down menu correspond to the IDs of the caption/patterns that you created.
-. The Holding Type appears by default and corresponds to the Type that you selected when you created the Caption/Pattern.
-. In the holding code area of the New Issuance dialog, click Wizard. The Wizard enables you to add holdings information.
-. Enter the volume of the item in hand in the v. field.
-. Enter the number of the item in hand in the no. field.
-. Enter the year of publication in the Year field.
-. 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.
-. Enter the day of publication in the day field if applicable.
-. Click Compile to generate the holdings code.
-
-Generate Item Predictions
-~~~~~~~~~~~~~~~~~~~~~~~~~
-
-After you manually create the first issue, Evergreen will predict future issuances. Use the Generate Predictions functionality to predict future issues.
-
-. Click *Subscription Details* -> *Issuances* -> *Generate Predictions*.
-. 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 <<_creating_a_subscription,creating a subscription>> 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.
-. Click Generate.
-. Evergreen will predict a run of issuances and copies. The prediction will appear in a list.
-. You can delete the first, manual issuance by clicking the check box adjacent to the issuance and clicking Delete Selected.
diff --git a/docs/serials/E-edit_subscriptions.adoc b/docs/serials/E-edit_subscriptions.adoc
deleted file mode 100644
index 0c8d5fd..0000000
--- a/docs/serials/E-edit_subscriptions.adoc
+++ /dev/null
@@ -1,19 +0,0 @@
-Edit Subscriptions
-------------------
-Subscriptions can be edited to change the caption and pattern and other information.
-
-Serials Control View
-~~~~~~~~~~~~~~~~~~~~
-
-. To access Serial Control View, open a serials record, and click *Actions for this Record* -> *Serial Control*. This opens the Subscriptions interface
-. Click the subscriptions tab
-. Click on the appropriate link to edit
-
-
-Alternate Serials Control View
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-. To access Alternate Serial Control View, open a serials record, and click *Actions for this Record* -> *Alternate Serial Control*. This opens the Subscriptions interface
-. Click the hyperlinked ID number to edit the subscription. 
-. Click on the appropriate tab to edit the information
-
diff --git a/docs/serials/E-routing_lists.adoc b/docs/serials/E-routing_lists.adoc
new file mode 100644
index 0000000..d1237f3
--- /dev/null
+++ b/docs/serials/E-routing_lists.adoc
@@ -0,0 +1,19 @@
+Routing Lists
+-------------
+
+Routing lists enable you to designate specific users and/or departments that serial items need to be routed to upon receiving.
+
+*Create a Routing List*
+
+. To create a routing list for a subscription, go to the _Manage Subscriptions_ tab for a serials record, select the subscription from the list and go to *Actions->Additional Routing*, or _right-click_ and select *Additional Routing*.  A dialog box will appear where you can create the routing list.
+.. Scan or type in the barcode of the user the items should be routed to in the _Reader (barcode)_ field and click *Add Route*.  Continue adding barcodes until the list is complete.
+.. To route items to a location, click the radio button next to _Department_, type in the routing location, and click *Add Route*.
+.. A _Note_ may be added along with each addition to the list.
+.. The names and departments on the list will appear at the top of the dialog box and can be reordered by clicking the arrows or removed by clicking the x next to each name or department.
+. When the list is complete, click *Update*.
+
+
+image::media/serials_routing1.PNG[]
+
+
+Routing lists can be printed as items are received (see the documentation on Receiving for more information).  They can also be printed directly from the _Manage Issues_ tab in a subscription by selecting the item(s) and going to *Actions->Print routing lists* or _right-clicking_ on the item(s) and selecting *Print routing lists* from the menu.
diff --git a/docs/serials/F-Receiving.adoc b/docs/serials/F-Receiving.adoc
deleted file mode 100644
index ccbbe12..0000000
--- a/docs/serials/F-Receiving.adoc
+++ /dev/null
@@ -1,102 +0,0 @@
-Receiving
----------
-You can receive either through the Serials Control View or in Batch Receive with the simple or advanced interface.
-
-Serials Control View Receiving
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-image::media/scv-rec.png[Receiving]
-
-. To receive items, click the *Receive* radio button. In the top pane, the items that have yet to be received are displayed. In the bottom pane, recently received items are displayed with the most recent at the top.
-. Select the branch that will receive the items from the drop down box.
-. Select the item that you want to receive.
-. Select the current working unit. Click *Set Current Unit*, located in the lower right corner of the screen. A drop down menu will appear.
-	* If you want to barcode each item individually, select *Auto per item*. This setting is recommended for most receiving processes.
-	* If you want each item within a unit to share the same barcode, then select *New Unit*. This setting is advised for most binding processes.
-	* If you want the item to be received or bound into an existing item, select *Recent* and select the desired item from the menu. To make a change in bound items, receive or bind the items into an already existing unit.
-. Click *Receive/Move Selected*.
-. Enter a barcode and call number if prompted to do so.
-. A message confirming receipt of the item appears. Click *OK*.
-. The screen refreshes. Now the item has moved from the top pane to the bottom pane. (If you have checked "Show all", the item also remains in the top pane, with a received date added to it.) In the bottom pane, the item that you have just received is now at the top of the list of the received items.
-
-After receiving items, you can view the updated holdings in the OPAC.
-
-Notes in the Receiving Interface
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-image::media/scv-notes.png[Alert Notes in Receiving Interface]
-
-The total number of notes for each item is displayed in the "Notes" column in the Items tab. The column header says "Notes (Item/Dist/Sub)" to explain how the numbers are organized in the column: First is the total number of Item Notes on that item, second is the number of Distribution Notes for that item's distribution, and last is the number of Subscription Notes on that item's subscription. To view and modify any of these notes, right-click on an item and click *View Sub. Notes*, *View Dist. Notes* or *View Item Notes*.
-
-Serial Alerts At Receive Time
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-In the Serial Control View, you can now flag a note as an "alert" to
-make it more visible on the receiving interface. This flag is available
-as a checkbox on subscription, distribution and item notes. The new *Alerts*
-button on the Items tab displays the number of alert notes that are available
-for the selected items, and clicking this button opens a window which
-displays all applicable alert notes, sorted by type. Notes can also be
-edited or deleted from this window.
-
-Set Special Statuses
-^^^^^^^^^^^^^^^^^^^^
-
-image::media/scv-status.png[Set Item Status]
-
-The Serial Control interface prevents direct editing of serial item statuses
-for data integrity reasons. As an alternative to direct control, the interface
-offers menu options for setting items to 'claimed', 'not held', and
-'not published'. Note that these statuses are still currently useful for
-reporting and display purposes only. The 'claimed' status changes the display 
-but does not yet connect with the Acquisitions module in any way. Also note 
-that, once you set an item to 'not held' or 'not published', that item will 
-be hidden from the list unless you check the *Show All* checkbox.
-
-Batch Receiving
-~~~~~~~~~~~~~~~
-
-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.
-
-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*.
-
-Simple Batch Receiving
-^^^^^^^^^^^^^^^^^^^^^^
-Follow these steps to receive items in batch in a simple interface.
-
-image::media/scv-srec.jpg[Receiving]
-
-. The Batch Receive interface displays issues that have not yet been received. The earliest expected issue appears at the top of the list.
-. In the right lower corner, you see a check box to *Create Units for Received Items*. If you do not check this box, then you will receive items in simple mode.
-. Click *Next*.
-. 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.
-. 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.
-. Click *Apply*. The note should appear in the note field in each distribution.
-. Then click *Receive Selected Items*.
-. The received items are cleared from the screen.
-
-Advanced Batch Receiving
-^^^^^^^^^^^^^^^^^^^^^^^^
-Follow these steps to receive items in batch in a simple interface.
-
-image::media/scv-srec.jpg[Receiving]
-
-. The Batch Receive interface displays issues that have not yet been received. The earliest expected issue appears at the top of the list.
-. 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.
-. This will allow you to utilize the copy templates and input additional information about the copy:
-. Barcode - You can scan printed barcodes into the barcode field for each copy, or you can allow the system to auto-generate barcodes. 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.
-	. Circ Modifiers -  The circ modifiers drop down menu is populated with the circulation modifiers that you created in *Administration* -> *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.
-	. Call Number -  Enter a call number. Any item with a barcode must also have a call number.
-	. Note - Add a note. There are no limits on the number of characters that can be entered in this field. The note only displays in this screen.
-	. Copy Location - The copy location drop down menu is populated with the copy locations that you created in *Administration* -> *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.
-	. 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.
-	. 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.
-. When you are ready to receive the items, click *Receive Selected Items*.
-. The items that have been received are cleared from the Batch Receive interface. The remaining disabled item is an unreceived item.
-. 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.
-
-Duplicate Barcode Alert
-^^^^^^^^^^^^^^^^^^^^^^^
-
-Evergreen will now display an alert if a duplicate barcode is entered in the Serials Batch Receive interface.  If a staff member enters a barcode that already exists in the database while receiving new serials items in the Serials Batch Receive interface, an alert message will pop up letting the staff member know that the barcode is a duplicate.  After the staff member clicks OK to clear the alert, he or she can enter a new barcode.
-
-image::media/dup_serials_barcode.JPG[Duplicate Barcode Warning]
diff --git a/docs/serials/F-Special_issue.adoc b/docs/serials/F-Special_issue.adoc
new file mode 100644
index 0000000..e3684d9
--- /dev/null
+++ b/docs/serials/F-Special_issue.adoc
@@ -0,0 +1,36 @@
+Special Issues
+--------------
+
+Adding Extra Copies
+~~~~~~~~~~~~~~~~~~~
+If the library receives an extra copy of an expected issue, the extra copy can be added to the list of predicted issues so it can be received through the serials module.
+
+*To add an extra copy of an expected issue*:
+
+. In the _Manage Issues_ tab, select the issuance that precedes the issuance that you received an extra copy of and go to *Actions->Add following issue* or _right-click_ on the issuance and select *Add following issue* from the menu.
+. A dialog box will appear.  Verify that the _Publication date_, _Type_, and _Chronology_ labels are correct.  The _Enumeration_ labels will be filled in automatically when the issue is created.
+. Click *Save* to create the extra copy of the following issue.
+. The extra copy will appear in the list of issues and can be received using your typical workflow.
+
+
+image::media/serials_extra1.PNG[]
+
+
+Adding Special Issues
+~~~~~~~~~~~~~~~~~~~~~
+If the library receives an unexpected issue of a subscription, such as Summer Issue or Holiday Issue, it can be added to the list of predicted issues as a Special Issue so it can be received through the serials module.
+
+*To add a special issue*:
+
+. In the _Manage Issues_ tab, click *Add Special Issue*.  A dialog box will appear.
+. Enter the _Publication date_ of the special issue.
+. Select the _Type_ (typically Basic).
+. Add an _Issuance Label_ to identify the special issue, such as "Holiday Issue 2017".
+. Click *Save*.
+. The special issue will appear in the list of issues and can be received using your typical workflow.
+
+
+image::media/serials_extra2.PNG[]
+
+
+NOTE: A special issue may also be added as an ad hoc issue by following the instructions for Adding Extra Copies.  Enter the Publication date and Type and check the box adjacent to Ad hoc issue?  The form will update to allow you to enter an Issuance Label.
diff --git a/docs/serials/G-Special_issue.adoc b/docs/serials/G-Special_issue.adoc
deleted file mode 100644
index ce5d9d3..0000000
--- a/docs/serials/G-Special_issue.adoc
+++ /dev/null
@@ -1,9 +0,0 @@
-Special Issues
---------------
-Currently, creating a special issue can only be done through the Alternate Serials Control View.
-
-. Create an issuance in the Serials Control View or the Alternate Serials Control View
-. In the Alternate Serials Control View, click on the name of your special issue in the list of issuances.
-. Click the New Items button
-. Enter the appropriate information
-. 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.
diff --git a/docs/serials/G-binding.adoc b/docs/serials/G-binding.adoc
new file mode 100644
index 0000000..aff03e1
--- /dev/null
+++ b/docs/serials/G-binding.adoc
@@ -0,0 +1,10 @@
+Binding Issues
+--------------
+
+*To bind received issues together:*
+
+. Go to the _Manage Issues_ tab and select the issues you want to bind together.
+. _Right-click_ on the issues or go to *Action* and select *Bind*.
+. The _Bind Items_ interface will appear and all items will be represented on the screen.  The first item's fields will be editable.  _Modify the Call Number_ if needed.  Replace the *Barcode* and click *Save*.
+
+NOTE: The barcode must be replaced with a new barcode.  The binding will fail if you attempt to reuse an existing barcode from one of the items being bound.  Evergreen views it as a duplicate barcode.
diff --git a/docs/serials/H-holdings_statements.adoc b/docs/serials/H-holdings_statements.adoc
index dd0a92c..787101b 100644
--- a/docs/serials/H-holdings_statements.adoc
+++ b/docs/serials/H-holdings_statements.adoc
@@ -12,24 +12,40 @@ Evergreen users can create, edit and delete their own MFHD.
 Create an MFHD record
 ^^^^^^^^^^^^^^^^^^^^^
 
-. 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*.
-. A message will confirm that you have created the MFHD Record. Click OK.
-. Click Reload in the top left corner of the record.
-. The Holdings Summary will appear. Click Edit Holdings in the right corner.
-. Click Edit Record.
-. The MFHD window will pop up. Enter holdings information. Click Save MFHD.
-. Close the MFHD window.
-. Click Reload in the top left corner of the record. The Holdings Summary will reflect the changes to the MFHD statement.
+*To create a MFHD record:*
+
+. From a serials record in the catalog, go to *Serials->Manage MFHDs*.  This will bring you to the _Manage MFHD_ tab within the serials module.
+. Click *Create MFHD*. 
+
+
+image::media/serials_mfhd1.PNG[]
+
+
+. A _Create new MFHD_ dialog box will appear.  _Select the library_ for which you are creating the MFHD record and click *Create*.
+. The MFHD record will appear in the list.  Go to *Actions->Edit MFHD* or _right-click_ on the row and select *Edit MFHD* from the drop down menu.
+
+
+image::media/serials_mfhd3.PNG[]
+
+
+. The MARC Editor will appear.  _Modify the MFHD record_ as needed and click *Save*.
+. The Textual Holdings statement will appear in the _Issues Held_ tab in the catalog.
+
+
+image::media/serials_mfhd6.PNG[]
+
 
 Edit a MFHD record
 ^^^^^^^^^^^^^^^^^^
 
-. Open a serial record, click *Actions for this Record* -> *MFHD Record* -> *Edit MFHD Record* and select the appropriate MFHD. 
-. Edit the MFHD
-. Click Save MFHD
+. Open a serial record, go to *Serials* -> *MFHD Record* -> *Manage MFHDs* and select the appropriate MFHD.
+. Go to *Actions* or right-click on the MFHD and select *Edit MFHD*.
+. The MARC Editor will appear.  _Modify the MFHD record_ as needed and click *Save*.
+
 
 Delete a MFHD Record
 ^^^^^^^^^^^^^^^^^^^^
 
-. Open a serial record, click *Actions for this Record* -> *MFHD Record* -> *Delete MFHD Record* and select the appropriate MFHD. 
-. Click to confirm the deletion of the MFHD
+. Open a serial record, go to *Serials* -> *MFHD Record* -> *Manage MFHDs* and select the appropriate MFHD.
+. Go to *Actions* or right-click on the MFHD and select *Delete Selected MFHDs*.
+. Click *OK/Continue* to delete the record.

-----------------------------------------------------------------------

Summary of changes:
 docs/media/serials_ct1.PNG              |  Bin 0 -> 47949 bytes
 docs/media/serials_extra1.PNG           |  Bin 0 -> 30423 bytes
 docs/media/serials_extra2.PNG           |  Bin 0 -> 15856 bytes
 docs/media/serials_mfhd1.PNG            |  Bin 0 -> 13874 bytes
 docs/media/serials_mfhd2.PNG            |  Bin 0 -> 17519 bytes
 docs/media/serials_mfhd3.PNG            |  Bin 0 -> 16418 bytes
 docs/media/serials_mfhd4.PNG            |  Bin 0 -> 24612 bytes
 docs/media/serials_mfhd5.PNG            |  Bin 0 -> 12071 bytes
 docs/media/serials_mfhd6.PNG            |  Bin 0 -> 8659 bytes
 docs/media/serials_routing1.PNG         |  Bin 0 -> 26998 bytes
 docs/media/serials_sub0.PNG             |  Bin 0 -> 55593 bytes
 docs/media/serials_sub1.PNG             |  Bin 0 -> 27987 bytes
 docs/media/serials_sub10.PNG            |  Bin 0 -> 7963 bytes
 docs/media/serials_sub11.PNG            |  Bin 0 -> 86737 bytes
 docs/media/serials_sub2.PNG             |  Bin 0 -> 27176 bytes
 docs/media/serials_sub3.PNG             |  Bin 0 -> 28046 bytes
 docs/media/serials_sub4.PNG             |  Bin 0 -> 26468 bytes
 docs/media/serials_sub5.PNG             |  Bin 0 -> 16299 bytes
 docs/media/serials_sub6.PNG             |  Bin 0 -> 16474 bytes
 docs/media/serials_sub7.PNG             |  Bin 0 -> 13506 bytes
 docs/media/serials_sub8.PNG             |  Bin 0 -> 86429 bytes
 docs/media/serials_sub9.PNG             |  Bin 0 -> 25172 bytes
 docs/media/serials_wizard1.PNG          |  Bin 0 -> 44079 bytes
 docs/media/serials_wizard2.PNG          |  Bin 0 -> 33725 bytes
 docs/media/serials_wizard3.PNG          |  Bin 0 -> 24580 bytes
 docs/media/serials_wizard4.PNG          |  Bin 0 -> 32788 bytes
 docs/media/serials_wizard5.PNG          |  Bin 0 -> 29840 bytes
 docs/media/serials_wizard6.PNG          |  Bin 0 -> 20693 bytes
 docs/root.adoc                          |   12 +-
 docs/root_serials.adoc                  |   16 +-
 docs/serials/A-intro.adoc               |   30 +----
 docs/serials/B-copy_template.adoc       |   41 ------
 docs/serials/B-serials_admin.adoc       |  151 +++++++++++++++++++++
 docs/serials/C-serials_workflow.adoc    |  142 ++++++++++++++++++++
 docs/serials/C-subscription-SCV.adoc    |  218 -------------------------------
 docs/serials/D-Receiving.adoc           |   88 +++++++++++++
 docs/serials/D-subscription-ASCV.adoc   |  216 ------------------------------
 docs/serials/E-edit_subscriptions.adoc  |   19 ---
 docs/serials/E-routing_lists.adoc       |   19 +++
 docs/serials/F-Receiving.adoc           |  102 --------------
 docs/serials/F-Special_issue.adoc       |   36 +++++
 docs/serials/G-Special_issue.adoc       |    9 --
 docs/serials/G-binding.adoc             |   10 ++
 docs/serials/H-holdings_statements.adoc |   42 ++++--
 44 files changed, 490 insertions(+), 661 deletions(-)
 create mode 100644 docs/media/serials_ct1.PNG
 create mode 100644 docs/media/serials_extra1.PNG
 create mode 100644 docs/media/serials_extra2.PNG
 create mode 100644 docs/media/serials_mfhd1.PNG
 create mode 100644 docs/media/serials_mfhd2.PNG
 create mode 100644 docs/media/serials_mfhd3.PNG
 create mode 100644 docs/media/serials_mfhd4.PNG
 create mode 100644 docs/media/serials_mfhd5.PNG
 create mode 100644 docs/media/serials_mfhd6.PNG
 create mode 100644 docs/media/serials_routing1.PNG
 create mode 100644 docs/media/serials_sub0.PNG
 create mode 100644 docs/media/serials_sub1.PNG
 create mode 100644 docs/media/serials_sub10.PNG
 create mode 100644 docs/media/serials_sub11.PNG
 create mode 100644 docs/media/serials_sub2.PNG
 create mode 100644 docs/media/serials_sub3.PNG
 create mode 100644 docs/media/serials_sub4.PNG
 create mode 100644 docs/media/serials_sub5.PNG
 create mode 100644 docs/media/serials_sub6.PNG
 create mode 100644 docs/media/serials_sub7.PNG
 create mode 100644 docs/media/serials_sub8.PNG
 create mode 100644 docs/media/serials_sub9.PNG
 create mode 100644 docs/media/serials_wizard1.PNG
 create mode 100644 docs/media/serials_wizard2.PNG
 create mode 100644 docs/media/serials_wizard3.PNG
 create mode 100644 docs/media/serials_wizard4.PNG
 create mode 100644 docs/media/serials_wizard5.PNG
 create mode 100644 docs/media/serials_wizard6.PNG
 delete mode 100644 docs/serials/B-copy_template.adoc
 create mode 100644 docs/serials/B-serials_admin.adoc
 create mode 100644 docs/serials/C-serials_workflow.adoc
 delete mode 100644 docs/serials/C-subscription-SCV.adoc
 create mode 100644 docs/serials/D-Receiving.adoc
 delete mode 100644 docs/serials/D-subscription-ASCV.adoc
 delete mode 100644 docs/serials/E-edit_subscriptions.adoc
 create mode 100644 docs/serials/E-routing_lists.adoc
 delete mode 100644 docs/serials/F-Receiving.adoc
 create mode 100644 docs/serials/F-Special_issue.adoc
 delete mode 100644 docs/serials/G-Special_issue.adoc
 create mode 100644 docs/serials/G-binding.adoc


hooks/post-receive
-- 
Evergreen ILS
