diff --git a/.gitignore b/.gitignore
new file mode 100644
index 0000000..3f11a21
--- /dev/null
+++ b/.gitignore
@@ -0,0 +1,6 @@
+#
+#gitignore
+#
+
+# exclude build directory
+build/
diff --git a/README.md b/README.md
index 67a0825..8c78fbf 100644
--- a/README.md
+++ b/README.md
@@ -1,2 +1,3 @@
# Documentation
-CORAL Documentation Project
+
+***Beta*** CORAL Documentation Project
diff --git a/build/doctrees/authentication.doctree b/build/doctrees/authentication.doctree
index 4dae9ad..5202f95 100644
Binary files a/build/doctrees/authentication.doctree and b/build/doctrees/authentication.doctree differ
diff --git a/build/doctrees/basics.doctree b/build/doctrees/basics.doctree
index 9219652..479c8b8 100644
Binary files a/build/doctrees/basics.doctree and b/build/doctrees/basics.doctree differ
diff --git a/build/doctrees/codingguidelines.doctree b/build/doctrees/codingguidelines.doctree
index 00318c0..b1b08ab 100644
Binary files a/build/doctrees/codingguidelines.doctree and b/build/doctrees/codingguidelines.doctree differ
diff --git a/build/doctrees/docstyleguide.doctree b/build/doctrees/docstyleguide.doctree
index e7ed2d7..c9e98b4 100644
Binary files a/build/doctrees/docstyleguide.doctree and b/build/doctrees/docstyleguide.doctree differ
diff --git a/build/doctrees/environment.pickle b/build/doctrees/environment.pickle
index 7b9bbbf..21065c2 100644
Binary files a/build/doctrees/environment.pickle and b/build/doctrees/environment.pickle differ
diff --git a/build/doctrees/faq.doctree b/build/doctrees/faq.doctree
index d9b9f81..7e9ea05 100644
Binary files a/build/doctrees/faq.doctree and b/build/doctrees/faq.doctree differ
diff --git a/build/doctrees/glossary.doctree b/build/doctrees/glossary.doctree
index c763baa..bbe81e1 100644
Binary files a/build/doctrees/glossary.doctree and b/build/doctrees/glossary.doctree differ
diff --git a/build/doctrees/gokb.doctree b/build/doctrees/gokb.doctree
index e7465ae..d0a5c9f 100644
Binary files a/build/doctrees/gokb.doctree and b/build/doctrees/gokb.doctree differ
diff --git a/build/doctrees/import.doctree b/build/doctrees/import.doctree
index 33355f3..9774f0c 100644
Binary files a/build/doctrees/import.doctree and b/build/doctrees/import.doctree differ
diff --git a/build/doctrees/index.doctree b/build/doctrees/index.doctree
index 8f3c4ad..0e4f1b7 100644
Binary files a/build/doctrees/index.doctree and b/build/doctrees/index.doctree differ
diff --git a/build/doctrees/licensing.doctree b/build/doctrees/licensing.doctree
index 606add0..9f41957 100644
Binary files a/build/doctrees/licensing.doctree and b/build/doctrees/licensing.doctree differ
diff --git a/build/doctrees/licensing2.doctree b/build/doctrees/licensing2.doctree
deleted file mode 100644
index 7cff9c9..0000000
Binary files a/build/doctrees/licensing2.doctree and /dev/null differ
diff --git a/build/doctrees/management.doctree b/build/doctrees/management.doctree
new file mode 100644
index 0000000..8f5726c
Binary files /dev/null and b/build/doctrees/management.doctree differ
diff --git a/build/doctrees/merge.doctree b/build/doctrees/merge.doctree
index 7d89e16..89ef4f4 100644
Binary files a/build/doctrees/merge.doctree and b/build/doctrees/merge.doctree differ
diff --git a/build/doctrees/organizations.doctree b/build/doctrees/organizations.doctree
index 33528ee..bf438e9 100644
Binary files a/build/doctrees/organizations.doctree and b/build/doctrees/organizations.doctree differ
diff --git a/build/doctrees/organizations2.doctree b/build/doctrees/organizations2.doctree
deleted file mode 100644
index 68937ef..0000000
Binary files a/build/doctrees/organizations2.doctree and /dev/null differ
diff --git a/build/doctrees/overview.doctree b/build/doctrees/overview.doctree
index bd1c0cc..270322b 100644
Binary files a/build/doctrees/overview.doctree and b/build/doctrees/overview.doctree differ
diff --git a/build/doctrees/release.doctree b/build/doctrees/release.doctree
index 6493329..e9d6268 100644
Binary files a/build/doctrees/release.doctree and b/build/doctrees/release.doctree differ
diff --git a/build/doctrees/resources.doctree b/build/doctrees/resources.doctree
index eb1de7f..5e53370 100644
Binary files a/build/doctrees/resources.doctree and b/build/doctrees/resources.doctree differ
diff --git a/build/doctrees/styleguide.doctree b/build/doctrees/styleguide.doctree
deleted file mode 100644
index 065f2bf..0000000
Binary files a/build/doctrees/styleguide.doctree and /dev/null differ
diff --git a/build/doctrees/sushi.doctree b/build/doctrees/sushi.doctree
index 5f74d19..6f9eadb 100644
Binary files a/build/doctrees/sushi.doctree and b/build/doctrees/sushi.doctree differ
diff --git a/build/doctrees/technical.doctree b/build/doctrees/technical.doctree
index a88a64a..37c4791 100644
Binary files a/build/doctrees/technical.doctree and b/build/doctrees/technical.doctree differ
diff --git a/build/doctrees/terms.doctree b/build/doctrees/terms.doctree
index ddd98d2..78de6cb 100644
Binary files a/build/doctrees/terms.doctree and b/build/doctrees/terms.doctree differ
diff --git a/build/doctrees/translation.doctree b/build/doctrees/translation.doctree
index 2d80668..63f996e 100644
Binary files a/build/doctrees/translation.doctree and b/build/doctrees/translation.doctree differ
diff --git a/build/doctrees/usagestats.doctree b/build/doctrees/usagestats.doctree
index 052022a..88d4e22 100644
Binary files a/build/doctrees/usagestats.doctree and b/build/doctrees/usagestats.doctree differ
diff --git a/build/doctrees/website.doctree b/build/doctrees/website.doctree
index b112c31..161c399 100644
Binary files a/build/doctrees/website.doctree and b/build/doctrees/website.doctree differ
diff --git a/build/html/_images/editicon.png b/build/html/_images/editicon.png
new file mode 100644
index 0000000..e438200
Binary files /dev/null and b/build/html/_images/editicon.png differ
diff --git a/build/html/_images/image_0.png b/build/html/_images/image_0.png
index 3328c79..df5fa56 100644
Binary files a/build/html/_images/image_0.png and b/build/html/_images/image_0.png differ
diff --git a/build/html/_images/image_01.png b/build/html/_images/image_01.png
index df5fa56..3328c79 100644
Binary files a/build/html/_images/image_01.png and b/build/html/_images/image_01.png differ
diff --git a/build/html/_images/image_1.png b/build/html/_images/image_1.png
index e2d5d7a..37fc027 100644
Binary files a/build/html/_images/image_1.png and b/build/html/_images/image_1.png differ
diff --git a/build/html/_images/image_11.png b/build/html/_images/image_11.png
index 37fc027..e2d5d7a 100644
Binary files a/build/html/_images/image_11.png and b/build/html/_images/image_11.png differ
diff --git a/build/html/_images/image_2.png b/build/html/_images/image_2.png
deleted file mode 100644
index 939f3eb..0000000
Binary files a/build/html/_images/image_2.png and /dev/null differ
diff --git a/build/html/_images/image_3.png b/build/html/_images/image_3.png
deleted file mode 100644
index 9b492ed..0000000
Binary files a/build/html/_images/image_3.png and /dev/null differ
diff --git a/build/html/_images/image_4.png b/build/html/_images/image_4.png
deleted file mode 100644
index e1681b8..0000000
Binary files a/build/html/_images/image_4.png and /dev/null differ
diff --git a/build/html/_images/image_5.png b/build/html/_images/image_5.png
deleted file mode 100644
index 4f576f8..0000000
Binary files a/build/html/_images/image_5.png and /dev/null differ
diff --git a/build/html/_images/image_6.png b/build/html/_images/image_6.png
deleted file mode 100644
index 3703a56..0000000
Binary files a/build/html/_images/image_6.png and /dev/null differ
diff --git a/build/html/_images/managementAddOptionalNote.png b/build/html/_images/managementAddOptionalNote.png
new file mode 100644
index 0000000..36f0040
Binary files /dev/null and b/build/html/_images/managementAddOptionalNote.png differ
diff --git a/build/html/_images/managementEditDocumentRecord.png b/build/html/_images/managementEditDocumentRecord.png
new file mode 100644
index 0000000..be66eef
Binary files /dev/null and b/build/html/_images/managementEditDocumentRecord.png differ
diff --git a/build/html/_images/managementHomePage.png b/build/html/_images/managementHomePage.png
new file mode 100644
index 0000000..41d16a9
Binary files /dev/null and b/build/html/_images/managementHomePage.png differ
diff --git a/build/html/_images/managementNewDocument.png b/build/html/_images/managementNewDocument.png
new file mode 100644
index 0000000..a97dc83
Binary files /dev/null and b/build/html/_images/managementNewDocument.png differ
diff --git a/build/html/_images/organizationsAccountView.png b/build/html/_images/organizationsAccountView.png
new file mode 100644
index 0000000..bca5f38
Binary files /dev/null and b/build/html/_images/organizationsAccountView.png differ
diff --git a/build/html/_images/organizationsAddNewOrganization.png b/build/html/_images/organizationsAddNewOrganization.png
new file mode 100644
index 0000000..3a4f9e0
Binary files /dev/null and b/build/html/_images/organizationsAddNewOrganization.png differ
diff --git a/build/html/_images/organizationsAddNewUser.png b/build/html/_images/organizationsAddNewUser.png
new file mode 100644
index 0000000..cf3b625
Binary files /dev/null and b/build/html/_images/organizationsAddNewUser.png differ
diff --git a/build/html/_images/organizationsAliasesView.png b/build/html/_images/organizationsAliasesView.png
new file mode 100644
index 0000000..52c574d
Binary files /dev/null and b/build/html/_images/organizationsAliasesView.png differ
diff --git a/build/html/_images/organizationsContactView.png b/build/html/_images/organizationsContactView.png
new file mode 100644
index 0000000..c3a1f87
Binary files /dev/null and b/build/html/_images/organizationsContactView.png differ
diff --git a/build/html/_images/organizationsHomePage.png b/build/html/_images/organizationsHomePage.png
new file mode 100644
index 0000000..343a5f8
Binary files /dev/null and b/build/html/_images/organizationsHomePage.png differ
diff --git a/build/html/_images/organizationsIssuesView.png b/build/html/_images/organizationsIssuesView.png
new file mode 100644
index 0000000..99e3fee
Binary files /dev/null and b/build/html/_images/organizationsIssuesView.png differ
diff --git a/build/html/_images/organizationsLicensesView.png b/build/html/_images/organizationsLicensesView.png
new file mode 100644
index 0000000..85278a5
Binary files /dev/null and b/build/html/_images/organizationsLicensesView.png differ
diff --git a/build/html/_images/organizationsRecordView.png b/build/html/_images/organizationsRecordView.png
new file mode 100644
index 0000000..91bf737
Binary files /dev/null and b/build/html/_images/organizationsRecordView.png differ
diff --git a/build/html/_images/resourcesAccess.png b/build/html/_images/resourcesAccess.png
new file mode 100644
index 0000000..3debf96
Binary files /dev/null and b/build/html/_images/resourcesAccess.png differ
diff --git a/build/html/_images/resourcesAcquistion.png b/build/html/_images/resourcesAcquistion.png
new file mode 100644
index 0000000..231278e
Binary files /dev/null and b/build/html/_images/resourcesAcquistion.png differ
diff --git a/build/html/_images/resourcesAddNewNote.png b/build/html/_images/resourcesAddNewNote.png
new file mode 100644
index 0000000..8578ca8
Binary files /dev/null and b/build/html/_images/resourcesAddNewNote.png differ
diff --git a/build/html/_images/resourcesAddNewResource.png b/build/html/_images/resourcesAddNewResource.png
new file mode 100644
index 0000000..3169198
Binary files /dev/null and b/build/html/_images/resourcesAddNewResource.png differ
diff --git a/build/html/_images/resourcesAdmin.png b/build/html/_images/resourcesAdmin.png
new file mode 100644
index 0000000..e1df604
Binary files /dev/null and b/build/html/_images/resourcesAdmin.png differ
diff --git a/build/html/_images/resourcesAdminAlertSettings.png b/build/html/_images/resourcesAdminAlertSettings.png
new file mode 100644
index 0000000..ea9c927
Binary files /dev/null and b/build/html/_images/resourcesAdminAlertSettings.png differ
diff --git a/build/html/_images/resourcesAdminEditUserGroup.png b/build/html/_images/resourcesAdminEditUserGroup.png
new file mode 100644
index 0000000..a1cfa74
Binary files /dev/null and b/build/html/_images/resourcesAdminEditUserGroup.png differ
diff --git a/build/html/_images/resourcesAdminEditWorkflow.png b/build/html/_images/resourcesAdminEditWorkflow.png
new file mode 100644
index 0000000..7085d39
Binary files /dev/null and b/build/html/_images/resourcesAdminEditWorkflow.png differ
diff --git a/build/html/_images/resourcesAttachments.png b/build/html/_images/resourcesAttachments.png
new file mode 100644
index 0000000..a7a9b92
Binary files /dev/null and b/build/html/_images/resourcesAttachments.png differ
diff --git a/build/html/_images/resourcesCataloging.png b/build/html/_images/resourcesCataloging.png
new file mode 100644
index 0000000..94bcddb
Binary files /dev/null and b/build/html/_images/resourcesCataloging.png differ
diff --git a/build/html/_images/resourcesContacts.png b/build/html/_images/resourcesContacts.png
new file mode 100644
index 0000000..6dd57d5
Binary files /dev/null and b/build/html/_images/resourcesContacts.png differ
diff --git a/build/html/_images/resourcesEditAccess.png b/build/html/_images/resourcesEditAccess.png
new file mode 100644
index 0000000..dff7efc
Binary files /dev/null and b/build/html/_images/resourcesEditAccess.png differ
diff --git a/build/html/_images/resourcesEditAcquistion.png b/build/html/_images/resourcesEditAcquistion.png
new file mode 100644
index 0000000..09e5c25
Binary files /dev/null and b/build/html/_images/resourcesEditAcquistion.png differ
diff --git a/build/html/_images/resourcesEditCataloging.png b/build/html/_images/resourcesEditCataloging.png
new file mode 100644
index 0000000..25cc675
Binary files /dev/null and b/build/html/_images/resourcesEditCataloging.png differ
diff --git a/build/html/_images/resourcesEditCostInformation.png b/build/html/_images/resourcesEditCostInformation.png
new file mode 100644
index 0000000..a72afad
Binary files /dev/null and b/build/html/_images/resourcesEditCostInformation.png differ
diff --git a/build/html/_images/resourcesEditLicenses.png b/build/html/_images/resourcesEditLicenses.png
new file mode 100644
index 0000000..dbad04e
Binary files /dev/null and b/build/html/_images/resourcesEditLicenses.png differ
diff --git a/build/html/_images/resourcesEditResource.png b/build/html/_images/resourcesEditResource.png
new file mode 100644
index 0000000..3ae9e93
Binary files /dev/null and b/build/html/_images/resourcesEditResource.png differ
diff --git a/build/html/_images/resourcesEditUser.png b/build/html/_images/resourcesEditUser.png
new file mode 100644
index 0000000..f88a3ae
Binary files /dev/null and b/build/html/_images/resourcesEditUser.png differ
diff --git a/build/html/_images/resourcesFileImport.png b/build/html/_images/resourcesFileImport.png
new file mode 100644
index 0000000..239708f
Binary files /dev/null and b/build/html/_images/resourcesFileImport.png differ
diff --git a/build/html/_images/resourcesHome.png b/build/html/_images/resourcesHome.png
new file mode 100644
index 0000000..b01ef5e
Binary files /dev/null and b/build/html/_images/resourcesHome.png differ
diff --git a/build/html/_images/resourcesMyQueue.png b/build/html/_images/resourcesMyQueue.png
new file mode 100644
index 0000000..7dc01b0
Binary files /dev/null and b/build/html/_images/resourcesMyQueue.png differ
diff --git a/build/html/_images/resourcesProduct.png b/build/html/_images/resourcesProduct.png
new file mode 100644
index 0000000..744eff8
Binary files /dev/null and b/build/html/_images/resourcesProduct.png differ
diff --git a/build/html/_images/resourcesRouting.png b/build/html/_images/resourcesRouting.png
new file mode 100644
index 0000000..d353d7a
Binary files /dev/null and b/build/html/_images/resourcesRouting.png differ
diff --git a/build/html/_images/resourcesWorkflowUserGroup.png b/build/html/_images/resourcesWorkflowUserGroup.png
new file mode 100644
index 0000000..19b0f1f
Binary files /dev/null and b/build/html/_images/resourcesWorkflowUserGroup.png differ
diff --git a/build/html/_images/viewicon.png b/build/html/_images/viewicon.png
new file mode 100644
index 0000000..e545871
Binary files /dev/null and b/build/html/_images/viewicon.png differ
diff --git a/build/html/_sources/docstyleguide.txt b/build/html/_sources/docstyleguide.txt
index 3a7f319..51df37b 100644
--- a/build/html/_sources/docstyleguide.txt
+++ b/build/html/_sources/docstyleguide.txt
@@ -8,8 +8,22 @@ The purpose of the style guide is to help keep the documentation consistent in s
### Setting Up ###
The CDP is managed in a repo on GitHub found at [https://github.com/Coral-erm
-](https://github.com/Coral-erm "https://github.com/Coral-erm "). The project uses the [Sphinx Python Documentation Generator](http://www.sphinx-doc.org/en/stable/) and [CommonMark](http://commonmark.org/). The documentation files are edited in a combination of [reStructuredText](https://en.wikipedia.org/wiki/ReStructuredText) and [Markdown](https://en.wikipedia.org/wiki/Markdown), both markup languages supported by GitHub. In addition, [Read the Docs](https://readthedocs.org/) is used for hosting the documentation and providing additional documentation conversion and indexing tools.
+](https://github.com/Coral-erm "https://github.com/Coral-erm "). The project uses the [Sphinx Python Documentation Generator](http://www.sphinx-doc.org/en/stable/) and [ReCommonMark](http://recommonmark.readthedocs.io/en/latest/). The documentation files are edited in a combination of [reStructuredText](https://en.wikipedia.org/wiki/ReStructuredText) and [Markdown](https://en.wikipedia.org/wiki/Markdown), both markup languages supported by GitHub. In addition, [Read the Docs](https://readthedocs.org/) is used for hosting the documentation and providing additional documentation conversion and indexing tools.
-### Documentation Versioning ###
+### File Structure and File Naming Conventions ###
+
+#### Images ####
+
+1) Create a subfolder under /img using the same name as the markdown file in which the images will be used.
+
+For example, the following folder name for organizations.md
+
+ /img/organizations/
+
+
+2) Add images to the subfolder created in step 1. Name the images with a prefix identifying the markdown file they are associated with, separated Uppercase letters with a brief description of the image. Note: The underscore character causes GitHub to incorrectly process the image filenames in Markdown, which leads to problems in building files in the ReadtheDocs.
+
+For example: **organizationsAccountsView.png** for a a screenshot of the Organization's module accounts form.
+
diff --git a/build/html/_sources/gokb.txt b/build/html/_sources/gokb.txt
index 4976958..1062de4 100644
--- a/build/html/_sources/gokb.txt
+++ b/build/html/_sources/gokb.txt
@@ -50,4 +50,6 @@ Resource's identifier of provider*
Package content customization
-You can personalize package content once it is imported. You can also custom package you already got even if it was not imported from GOKb. The "custom screen" display the current package's children. If the checkbox is checked: the resource will be kept, else it will be removed from database when you will click on 'Confirm customization' button.
\ No newline at end of file
+You can personalize package content once it is imported. You can also custom package you already got even if it was not imported from GOKb. The "custom screen" display the current package's children. If the checkbox is checked: the resource will be kept, else it will be removed from database when you will click on 'Confirm customization' button.
+
+This is a test!!!
diff --git a/build/html/_sources/index.txt b/build/html/_sources/index.txt
index 7b6fda4..fc8ba71 100644
--- a/build/html/_sources/index.txt
+++ b/build/html/_sources/index.txt
@@ -16,6 +16,7 @@ CORAL Documentation Project
licensing
organizations
usagestats
+ management
technical
glossary
faq
diff --git a/build/html/_sources/licensing2.txt b/build/html/_sources/licensing2.txt
deleted file mode 100644
index 32a7df2..0000000
--- a/build/html/_sources/licensing2.txt
+++ /dev/null
@@ -1,448 +0,0 @@
-CORAL Licensing User Guide
----------------------------
-
-### About CORAL Licensing ###
-
- A component of Hesburgh Libraries locally developed ERM, CORAL
- Licensing provides a way to store and access digital copies of current
- and expired license agreements and related documents as well as
- associated agreement metadata. The licensing module helps make library
- license agreements more accessible to personnel through select
- searchable metadata fields and assists institutions in tracking and
- using specific pieces of information included in legal agreements.
- CORAL Licensing is a flexible document management system, useful in
- anticipating a variety of agreements and institutional goals for
- managing agreements. The module allows users to identify license
- clauses most important to record and track from an institutional point
- of view. With related features like a clause comparison function, and
- ILL and course pack terms tools that can be implemented to deliver
- terms through other systems such as SFX, the CORAL Licensing module
- provides a way to make better use of permissions included in the
- license agreement.
-
- *Please note that screenshots and text in this document are just
- examples and do not necessarily reflect terms for a particular
- resource.*
-
- ### Component Overview ###
-
- CORAL Licensing has six major components in the primary navigation at
- the top of each page.
-
- • Home
-
- • New License
-
- • Licenses in Progress
-
- • Expression Comparison
-
- • Terms Tool Report
-
- • Admin
-
-### Home ###
-
-
- Search has been placed on the *Home* page as the primary point of
- entry into the license records. The search runs against the fields
- license name, document name, and publisher/provider. The fields are
- defined in the next section as we look at creating a new license
- record.
-
-### New License
-
- Select *New License* from the main navigation to begin adding new
- license records. The link will present the window on the right.
-
- ‘License Name’ is the name of the license record. For example, a
- license record named *Cambridge University Press Journals* would
- contain any and all license documents pertaining to the Cambridge
- University Press journals.
-
- ‘Publisher/Provider’ is the name of the licensing organization. In
- this example Cambridge University Press would be the
- publisher/provider.
-
-‘Consortium’ would be used when the licensed resources are obtained
-through a consortium.
-
- The License Name may seem a bit arbitrary but it makes more sense when
- you think about a license record as a way to group together all
- licenses that are either related to each other or related to the same
- resource. Let us say for example that you have licensed a package of
- electronic journals from Springer and have over the years collected
- several licenses and amendments for that package. You can place all of
- those documents on the same license record and then you need to give
- the license record a name which gives some indication as to the
- documents found on that record. In this example ‘Springer Online
- Journals’ may be a valid license name.
-
- Let us also assume that you have licensed a set of eBooks from
- Springer as well and that the license for the eBook is in no way
- related to the license for the journals. You now have two options for
- loading the eBook license. You can create a new license record called
- *Springer eBooks* and load the license documents there or you can add
- the eBook license to the existing *Springer Online Journals* license.
- If you choose the latter then you could also consider changing the
- license name *Springer Online Journals to* something such as *Springer
- Online Products* to more accurately reflect all the documents
- contained on the record.
-
- *Interoperability note:* The publisher/provider field has an auto-fill
- feature which is populated from the organizations listed in CORAL
- Organizations. CORAL Licensing will manage publisher/provider names on
- its own if you have not installed CORAL Organizations or have disabled
- the interoperability. The publisher/provider names are managed and
- edited in the CORAL Licensing *Admin* area when the interoperability
- is disabled.
-
-### Adding / Editing New License Record
-
- Here is a new license record which has just been created for
- *Cambridge University Press Online Journals*. To the right of the
- license name are the options to remove the license or to edit the
- name, publisher/provider and consortia. The publisher/provider name is
- hyperlinked and will take the user to the Cambridge University Press
- record within CORAL Organizations. Here you can also enter a license
- record status in the ‘License Status’ field to the far right of the
- license name. CORAL Licensing includes the following default statuses.
-
- License Status (definition)
-
- • Awaiting Document (license record created but scanned license not
- yet added)
-
- • Complete (license record is complete, no additional work required)
-
- • Document Only (document loaded with expressions not identified or
- loaded)
-
- • Editing Expressions (document loaded and currently adding license
- terms/expressions)
-
- • NLR (no license required)
-
- License Status values can be edited, added or deleted through the
- *Admin* section detailed later in this document. The default values
- are simply suggestions for how an institution might consider tracking
- agreements and to indicate the purpose of the field.
-
- The license record has four sections located on the left-hand column;
- Documents, Expressions, SFX Links and Attachments
-
-### Documents
-
- The Documents tab contains all the documents for each license record.
- Any document may be uploaded to the system including licenses,
- amendments, order forms, purchase requests, or any other important
- document. Select ‘upload new document’ to begin.
-
-### Adding New Documents
-
- The ‘upload new document’ link opens the window on the right. Here you
- can fill out the initial details of the document and upload the actual
- file. Document Name is the only required field.
-
-‘Effective date’ is the effective date of the agreement, if identified
-and available.
-
-‘Document Type’ identifies what type of document this is (ex. Agreement,
-amendment, order form, etc).
-
-‘Parent’ identifies any parent document (ex. A parent document would be
-assigned when uploading an amendment).
-
-‘Name’ is the title of the document, usually taken directly from the
-license document (ex. Cambridge University Press Site License
-Agreement).
-
- ‘File’- browse and upload a scanned copy of the actual document.
-
- ‘Archived’ is used to identify documents which are no longer current
- or have been superseded by another agreement. Archived documents are
- sorted separate from current documents and are collapsed beneath a
- show/hide link to save screen space. Archiving a document does not
- delete it from the system. It also does not delete any expressions
- attached to that document.
-
- ‘Document Type’ is another customizable field which allows each
- library to set their own terminology. The software comes with the
- following types included.
-
- *Document Type*:
-
- • Agreement
-
- • Amendment
-
- • Countersigned Agreement
-
- • Internal Acknowledgement
-
- • Order Form
-
- • SERU
-
-### Editing Documents
-
- Once added the documents will display on the Documents tab sorted
- first by Document Type (agreements sort together, order forms sort
- together, etc) and then by signature date with most recent first.
- Multiple signatures for both licensee and licensor can be added using
- the ‘add signatures’ link. On the right hand column are the links to
- view, edit, and delete each document. Now that the documents are
- loaded the next step is to begin adding expressions. Please note that
- Expressions are not required. You should however assign an appropriate
- License Status to the record that indicates it is a document only
- record.
-
-### Adding Expressions
-
- The Expressions tab is where the expressions or clauses of the license
- are entered. You may enter any expression type that you wish. The
- software comes with the following expression types already defined but
- again the field is customizable and allows you to enter the types of
- your choice.
-
- Expression Type:
-
- • Authorized Users
-
- • Confidentiality Clause
-
- • Course Packs
-
- • eReserves
-
- • General Notes
-
- • Interlibrary Loan
-
- • Jurisdiction
-
- • Multi-year Term
-
- • Post Cancellation Access
-
- • Third Party Archiving
-
-
-### Adding Expressions
-
- The ‘add new expression’ link opens the window on the right. From this
- window you can add expressions for the documents that have been
- previously loaded.
-
- ‘Document’ is the document name for which you want to add a new
- expression. The drop-down is pre-populated from the existing document
- names in the specific license record. This is a required field.
-
- ‘Expression Type’ is the type of expression you wish to add
- (interlibrary loan terms, course pack rights, etc). This is a required
- field.
-
- ‘Qualifier’ is another customizable field which can be used to qualify
- particular expressions. For example, a qualifier of *Permitted* or
- *Prohibited* may be appropriate for an Interlibrary Loan expression.
- You may choose to ignore this field or choose to use it in a different
- fashion for other expression types.
-
- ‘Document Text’ is for the actual text of the license clause. An
- interlibrary loan expression has been added in the following figure.
-
-### Adding Display Notes
-
- In this example an Interlibrary Loan expression has been added along
- with a snippet of the license text and a qualifier of *Permitted* has
- been added noting that the item does allow for ILL. The
-
- actual legal text can be quite confusing so the next step is to add a
- Display Note which can hold an interpretation of the text of the
- clause that can be used for public display.
-
-### Adding Display / Internal Notes
-
- The ‘add/view display notes’ link opens a window which allows you to
- enter multiple display notes. It also displays the Document Text on
- that same window so that you can refer back to it while adding the
- notes. The sort order of multiple display notes can also be adjusted
- through this same window. The following figure shows a completed
- Display Notes window.
-
- There are two types of expression notes in CORAL licensing; Display
- Notes and Internal Notes. You can set the note type to either Internal
- or Display for each expression type on the ‘Admin’ page detailed later
- in this document. The two note types (internal and display) were added
- so that a distinction could be made between expressions and notes that
- were intended to be displayed outside the module, for instance in one
- of the terms tools, and those that were for internal use only. The
- Display Notes which are intended to be shared have additional
- functionality built in that the Internal Notes lack. In the following
- figure you will see the completed interlibrary loan expression. In
- this example the Interlibrary Loan expression type has been set to use
- Display Notes and as such the expression is presented with an
- additional checkbox to the left of the Document Text. Internal Notes
- do not receive this checkbox. When the licensing librarian or other
- appropriate personnel has finished editing the notes and expression
- he/she can check this box which indicates that the expression is
- finished and it makes the expression available through the *Terms Tool
- Report* page. An email is then generated by the system indicating that
- a new expression has been completed and is ready for display. You can
- edit the recipients of this email in the *Admin* page.
-
- If you choose not to use the *Terms Tool Report* page you may turn it
- off as explained in the technical documentation guide. This will also
- remove the display note checkbox and email functionality. It will also
- remove the SFX Links tab which is explained next.
-
-### Completed Expression
-
- The above figure is the completed expression with document text,
- qualifier and display notes. Qualifier may not be appropriate for
- certain expression types. The intended use of the qualifier is to
- further document permitted/prohibited distinctions such as
- interlibrary loan, course packs and ereserves. You may continue to add
- as many expressions as needed for some or all documents.
-
-### SFX Links
-
- Once the expressions or terms of the license are known, the next
- question to ask is ‘Which journals are covered by these terms?’.
- That’s where the SFX Links tab comes into play. Using this tab it is
- possible to relate a specific license to the covered journals in a
- specific SFX target or package. In this example the Cambridge
- University Press Site License Agreement is being associated with the
- Cambridge Journals Online target in SFX (Cambridge Journals Online is
- the SFX target public name). This SFX – License connection allows for
- the delivery of license terms through the SFX menu as detailed in the
- Terms Tool User Guide. It is true that not every institution uses SFX.
- The SFX Links tab could be renamed and/or repurposed for use with
- other openurl resolvers or journal management systems. This
-
- tab is meant to be used in conjunction with the Terms Tool and can be
- disabled along with the *Terms Tool Report* page for those who do not
- wish to use it.
-
-### Attachments
-
- For any resource there may be documents in addition to the actual
- license that are important to retain. Title lists and email
- correspondence are two that may be the most common. The Attachments
- tab allows you to upload these additional documents to the license
- record. The above figure shows an email that has been uploaded with
- the date and a description of the file. In this case the attachment is
- an email from the publisher detailing additional restrictions on the
- resource. The date field is not automatically entered by the system so
- it does not have to be the date the file was loaded into CORAL
- Licensing. The intention of the date field was to be the date the
- attached document was received but since the date is manually chosen
- it can be any date of your choice. The ‘view attachment 1’ link will
- open the uploaded file.
-
-### Licenses in Progress
-
- The *Licenses in Progress* page will show the licenses that are not
- yet complete. It is intended to be used by the licensing staff as a
- queue of outstanding licenses. It has been coded to show licenses of
- status Awaiting Document or Editing Expressions and will also show new
- licenses which have not yet been given any status. The hyperlinked
- License Name will take you into the license record.
-
-### Expression Comparison
-
- *Expression Comparison* allows the user to see all the instances of a
- specific expression type across all documents in a single screen or
- view. The 'Limit by Expression Type' dropdown allows the user to
- select from among all defined expression types. In the figure above
- the display notes and document text have been removed for reasons of
- confidentiality. In place of < Display Notes removed > and <
- Document Text removed > users would see the actual notes and
- document text that were entered. This allows licensing or relevant
- personnel to compare language for each expression type across all
- documents. It could be an immensely powerful tool when attempting to
- come up with recommended language during negotiations. The user may
- also add new display notes, open the license record and open the
- actual document from this page.
-
- *Expression Comparison* is intended for personnel that need quick
- access to all expressions in the system. Other library staff however,
- may only need access to specific types of expressions and this
- particular page may be information overload. The *Terms Tool Report*
- page was developed for these other users.
-
-### Terms Tool Report
-
- Once again the notes and document text have been removed from the
- screenshot. *Terms Tool Report* provides access to only the
- expressions using display notes and which have been identified as
- being complete by the licensing librarian using the terms tool
- checkbox mentioned earlier. As such it will not display unfinished
- expressions which the licensing librarian may still be working on.
- Another difference between *Terms Tool Report* and *Expression
- Comparison* is that this page does not offer any links for editing the
- record. While similar in function to *Expression Comparison* this page
- was added in order to serve a user group which does not need the full
- access provided by the *Expression Comparison* page.
-
- The main points to remember for this page are that it displays
- expressions which use display notes but only those that have been
- approved for display. It is possible to turn off *Terms Tool Report*
- and hide it from display if you do not wish to use it. Turning off the
- *Terms Tool Report* will also disable the SFX Links tab on the license
- record as well as the terms tool checkbox used to indicate that a
- Display Note has been completed and approved for display. Please see
- the Terms Tool User Guide for more information on how *Terms Tool
- Report* can be used and on how it can be used to push out license
- terms to other systems.
-
-### Admin
-
- The *Admin* page is where you will edit Expression Types, Document
- Types, Signature Types and
-
- License Statuses. Each of these fields can have as many values as
- needed so that the system can better
-
- meet local needs. *Admin* is also where you will edit and manage user
- permissions. CORAL Licensing has been built with the ability to limit
- access to select individuals given the confidential nature of license
- agreements. Users may not access CORAL Licensing until they are first
- set up with an account by an administrator. The following figure shows
- the ‘add new user’ window available from the *Admin* page.
-
- ‘Login ID’ will be the user’s unique ID in your local campus
- authentication system. See the technical documentation for more
- details on authentication.
-
- ‘Privilege’ is the user’s level of access (i.e. read only, etc).
-
- ‘Terms Tool Email’ – Enter email address if you wish the user to
- receive email notification when the terms tool box is checked for a
- given expression. Leave this blank for all others.
-
- The values available in the Privilege field deserve further
- explanation.
-
- Privileges
-
- • Admin users have complete add/edit rights and can remove licenses
- and associated fields.
-
- Access to the *Admin* page, the SFX Links tab on the license record
- and the terms tool checkbox is restricted to users with Admin
- privileges.
-
- • Add/Edit users can add, edit, or remove licenses and associated
- fields.
-
- • View Only users can view all license information and are allowed
- access to the uploaded documents.
-
- • Restricted users can view all license information but are not
- allowed access to the uploaded documents.
-
- Admin, Add/Edit and View Only are the same privileges used in the
- other CORAL modules. Restricted is an extra privilege used only in
- CORAL Licensing in order to restrict access to the actual license
- agreements that have been uploaded to the system.
diff --git a/build/html/_sources/management.txt b/build/html/_sources/management.txt
new file mode 100644
index 0000000..8c44228
--- /dev/null
+++ b/build/html/_sources/management.txt
@@ -0,0 +1,67 @@
+CORAL Management User Guide
+---------------------------------
+
+### About CORAL Management
+
+Developed by Texas A&M University, CORAL Management provides a way to store and access digital copies of documents related to the overall management of electronic resources.
+
+### Component Overview
+
+CORAL Management has three components in the primary navigation at the top of each page.
+
+• Home
+
+• New Document
+
+• Admin
+
+
+### Home
+
+
+
+Document records are listed alphabetically by name and the name field can be searched. Additionally, the records can be filtered by category and document type.
+
+### New Document
+
+Select New Document from the main navigation to begin adding new document records. This will open the New Document pop-up window.
+
+
+
+
+The ‘Name’ is the document name to be uploaded. The Management module only allows one active document per record so a document named Sample Letter to Excess Download Offender would only include a copy of the letter.
+
+The ‘Description’ is a brief explanation of the document, if necessary.
+
+‘Type’ is the type of document. The options listed in the dropdown box may be created from the Admin tab or by using the ‘add type’ link under the dropdown box. In the case of the Sample Letter to Excess Download Offender, the type could be template.
+
+‘Last Document Revision’ is the date the document was last revised. If no date is entered, today’s date is used by default.
+
+‘Categories’ is the group of documents to which the document belongs. A document can be included in more than one category. For example, the document *Retiree Policy Regarding Access to Electronic Resources* could be in both an ‘Access Policy’ category and a ‘Licensing’ category. Categories may be created from the Admin tab or by using the ‘add category’ link under the ‘Categories’ selection box.
+
+Selecting the ‘Browse…’ button opens the navigation pane used to browse and upload the document.
+
+‘Archived’ is used to identify documents that have been superseded by a newer version of the document.
+
+Selecting the ‘Add Optional Note’ link allows notes to be linked to the document by opening up two additional fields.
+
+
+
+‘Note’ provides a space to add any notes about the document.
+
+‘Note Type’ provides a way to categorize the type of note. The options listed in the dropdown box may be created from the Admin tab or by using the ‘add type’ link under the dropdown box.
+
+
+### Editing a Document Record
+
+Once a document record has been created, the document record opens. A document record can also be opened by selecting it from the ‘Home’ screen.
+
+
+
+
+
+The above record is for a License Agreement Checklist. Below the name is the description of the document, the associated categories, the documents creation date and creator, and the date the record was last updated and by whom. In this example, there are two archived versions of the checklist as evidenced by the “2 archive(s) available” note. Selecting ‘show archives’ makes these copies visible and accessible. To add another archived version, select ‘upload archived document’ and fill in the appropriate information. As previously mentioned, there can only be one current/active document. Therefore, to add a new version of a document, the current document must be archived first. Once that happens, an ‘upload new document’ link will display. Select this and complete the necessary information to add the new version.
+
+### Admin
+
+The Admin tab provides for the management of users, document types, note types, and categories.
diff --git a/build/html/_sources/merge.txt b/build/html/_sources/merge.txt
index 0ab94fc..77012a5 100644
--- a/build/html/_sources/merge.txt
+++ b/build/html/_sources/merge.txt
@@ -1,6 +1,8 @@
Merging Repositories
--------------------
+***Test line***
+
Project to merge repositories launched in 2015
This page is a work in progress
diff --git a/build/html/_sources/organizations.txt b/build/html/_sources/organizations.txt
index 99bed18..8271c21 100644
--- a/build/html/_sources/organizations.txt
+++ b/build/html/_sources/organizations.txt
@@ -3,13 +3,13 @@ CORAL Organizations User Guide
### About CORAL Organizations
-CORAL Organizations provides a way to manage contact and account information for variety of organizations customized by the user. Some out-of-the-box organizations include publisher, provider, vendor and consortium.
+CORAL Organizations provides a way to manage contact and account information for variety of organizations customized by the user. Some out-of-the-box organizations include publishers, providers, vendors and consortia.
CORAL TIP: New installations pre-populate the Organizations module with numerous organization names.
### Component Overview
-CORAL Organizations has three major components in the primary navigation at the top of each page.
+CORAL Organizations has three major components in the main navigation at the top of each page.
• Home
@@ -21,25 +21,24 @@ CORAL Organizations has three major components in the primary navigation at the
The home screen contains a search on the left and a list of organizations on the right. The up and down arrows in the table header can be used to sort the organizations by name, alias, parent, or role.
-
+
-There are four facets for search:
+There are four facets for search. These facets can be used in conjunction.
-* **Name (contains): **Searches against organization name and alias. For example, searching with AIP will retrieve the American Institute of Physics when AIP has been designated as an alias for this publisher.
+**Name (contains):** Searches against organization name and alias. For example, searching with AIP will retrieve the American Institute of Physics when AIP has been designated as an alias for this publisher.
-* **Role: **Provides the option to limit a search by an organization’s role (ex. publisher, provider, library, consortium, etc)
+**Role:** Provides the option to limit a search by an organization’s role (ex. publisher, provider, library, consortium, etc)
-* **Contact Name (contains)**: Search for the name of a known contact (ex. Jane Smith) instead of searching for the name of the organization.
+**Contact Name (contains):** Search for the name of a known contact (ex. Jane Smith) instead of searching for the name of the organization.
+
+**Starts with:** Browse all the entries alphabetically by the first letter.
-* **Starts with: **this A-to-Z browsing list can be used to browse all the entries alphabetically by the first letter.
-These facets can be used in conjunction.
### New Organization
-Organization Name?
+
-image of Add New Organization screen
Select New Organization from the main navigation to begin adding new organization records.
@@ -47,93 +46,101 @@ Select New Organization from the main navigation to begin adding new organizatio
* **Parent:** Name of the parent organization (i.e. Proquest as parent of Chadwyck-Healey). The purpose of the ‘Parent’ field is to relate multiple organizations together and to create an organization hierarchy. The field includes an auto-fill populated by existing organization records. The parent organization must already have an existing organization record in order for it to be assigned. Each organization may have only one parent assigned but multiple organizations may have the same parent thereby creating a useful parent-child hierarchy.
-* **Company URL:** Intendedmeant to be the url of the organization’s homepage.
+* **Company URL:** The URL of the organization’s homepage.
-* **Role(s): **the organization’s role. The values for this field can be customized through the [Admin](#bookmark=id.26in1rg)[ ](#bookmark=id.26in1rg)page.
+* **Role(s):** The organization’s role. The values for this field can be customized through the [Admin](#bookmark=id.26in1rg)[ ](#bookmark=id.26in1rg)page.
-* **Account Details: **Account numbers or general descriptive info about a library’s account with the organization.
+* **Account Details:** Account numbers or general descriptive info about a library’s account with the organization.
* **Notes:** General notes.
### The Organization Record
-
+
-Here is an organization record for Cambridge Scientific Abstracts. The information on the record is split among five tabs. The sixth tab labeled Licenses appears when the CORAL Licensing module is installed and enabled.
+Here is an organization record for Cambridge Scientific Abstracts. The information on the record is split among six tabs.
-* **Organization: **Displays the information found on the New Organizations screen explained on the previous page.
+* **Organization:** Displays the information found on the New Organizations screen explained on the previous page.
* **Aliases:** Alternate names and acronyms so that the record can be retrieved using various names.
* **Contacts:** Includes contact information for the organization (ex. Email, phone numbers for sales reps).
-* **Accounts: **Logins for managing administrator accounts (ex. Username/password logins for usage statistics collection).
+* **Accounts:** Logins for managing administrator accounts (ex. Username/password logins for usage statistics collection).
-* **Issues: **Recording major incidents with the organization and/or its resources (ex. Publisher changed servers and access was lost for several days).
+* **Issues:** Information about an organization that may be valuable over time such as notes about frequent breaks in access or an oddity in an organization's invoicing process.
-* **Licenses:** Links to the records in CORAL Licensing for all licenses from the organization. This is an interoperability feature which can be activated when both CORAL Licensing and CORAL Organizations are installed.
+* **Licenses:** Links to the records in CORAL Licensing for all licenses from the organization.
#### Organization
The figure above shows the organization tab for Cambridge Scientific Abstracts. Notice that this screenshot does not display the ‘Account Details’, ‘Notes’ or ‘Company URL’ fields that were found on the New Organization window on the previous page. These three fields are not displayed because no data was entered into those fields when the record was added.
-The ‘edit organization details’ link will open up a window that allows you to edit the information originally entered in the New Organization’s window.
+The ‘edit organization details’ link , will open up a window that allows you to edit the information originally entered in the New Organization’s window.
-In this example Cambridge Scientific Abstracts has been assigned ProQuest as the parent organization. The ‘view’ link next to ProQuest LLC will open the ProQuest organization record.
+In this example Cambridge Scientific Abstracts has been assigned ProQuest as the parent organization. The ‘view’ link
+ next to ProQuest LLC will open the ProQuest organization record.
#### Aliases
-
+
The Aliases tab allows the user to add multiple aliases for the organization. The default alias types are Alternative Name, Name Change, and Acronym. These fields can be customized using the [Admin](#bookmark=id.26in1rg)[ ](#bookmark=id.26in1rg)page
#### Contacts
-
+
The Contacts tab allows the user to add contact information for both specific personnel and general support. None of the fields are required except for Role(s).
-The values for the ‘Role(s)’ field can be customized through the [Admin](#bookmark=id.26in1rg)[ ](#bookmark=id.26in1rg)page. When the contact is no longer accurate, it can either be deleted or archived for historical tracking purposes. Contacts that have the ‘Archived’ box checked are kept in the system but are collapsed beneath a ‘show archived contacts’ link so that all users know that the contact information is out of date.
+The values for the ‘Role(s)’ field can be customized through the [Admin](#bookmark=id.26in1rg)[ ](#bookmark=id.26in1rg)page. When the contact is no longer accurate, it can either be deleted (deletion is restricted to users with admin privileges) or archived for historical tracking purposes. Contacts that have the ‘Archived’ box checked are kept in the system but are collapsed beneath a ‘Show Archived Contacts’ link so that all users know that the contact information is out of date.
-The ability to delete a contact has been restricted to users with admin privileges.
#### Accounts
+
+
The Accounts tab is used for storing login information that library personnel use for site administration, gathering usage statistics, etc.
-Account login information can be entered in either CORAL Organizations or if installed, CORAL Resources. Account login information which is resource specific may be entered in CORAL Resources. Account login information that is not resource specific (ex. A single administrator login for all Gale databases) should be entered here in CORAL Organizations. Information stored at the organization level will be inherited by individual resources within CORAL Resources.
+Account login information can be entered in either CORAL Organizations or CORAL Resources. Account login information which is resource specific may be entered in CORAL Resources. Account login information that is not resource specific (ex. A single administrator login for all Gale databases) should be entered here in CORAL Organizations. Information stored at the organization level will be inherited by individual resources within CORAL Resources.
-Add new login information by selecting the ‘add new external login’ link.
+Add new login information by selecting the ‘Add New External Login’ link.
-
Most of the fields are self-explanatory, with the exception of
-* **Login Type:** Default values are Admin, FTP, Marc, Statistics, Support, Other.
+* **Login Type:** Category of login. Default values are Admin, FTP, Marc, Statistics, Support, Other. You create additional login types using through the [Admin](#bookmark=id.26in1rg)[ ](#bookmark=id.26in1rg)page
-* **Local Account Email: ** The address of the library personnel registered on the account.
+* **Local Account Email:** The address of the library personnel registered on the account.
#### Issues
-
+
-The Issues tab is meant for recording general information about an organization that may be valuable over time. One example would be recording when an organization has frequent breaks in access or significant server downtimes. Another example would be having an organization that is often slow when it comes to sending out renewal invoices. The ‘add new issue’ link opens a new window which includes a date and notes field. It is a simple field but it may come in handy for recording the institutional knowledge that exists among various personnel.
+The Issues tab is meant for recording general information about an organization that may be valuable over time. One example would be recording when an organization has frequent breaks in access or significant server downtimes. Another example would be having an organization that is often slow when it comes to sending out renewal invoices. The ‘add new issue’ link opens a new window which includes a date and notes field. This field can be handy for recording the institutional knowledge that exists among various personnel.
#### Licenses
-The Licenses tab is only available when CORAL Licensing has been installed and the interoperability enabled. This tab will provide links to the license records within CORAL Licensing for all licenses where the organization has been identified as the Publisher/Provider. The hyperlinked license name will open the license record in a new window.
+
+
+The Licenses tab provides links to the license records entered into CORAL Licensing for all licenses where the organization has been identified as the Publisher/Provider. The hyperlinked license name will open the license record in a new window.
#### Admin
-The Admin page is where you can manage user privileges as well as edit the values for organization role, contact role, alias type and external login type. As with the other modules, CORAL Organizations is designed to work with your campus authentication system (see the technical documentation for details). All valid users are given view only access when logged into CORAL Organizations unless they have specifically been granted additional privileges. You only need to add specific user accounts for personnel that need more than view only privileges. The available privileges are ‘view only’, ‘add/edit’ and ‘admin’. The ‘add new user’ link on the Admin page opens the following window where ‘Login ID’ is the user’s campus ID.
+The Admin page is where you can manage the module's user privileges as well as edit the values for organization role, contact role, alias type, external login type, and issue type.
+
+#####Adding New Users####
+The ‘add new user’ link on the Admin page opens the following window.
+
+
+If you utilize your institution's existing authentication system, the ‘Login ID’ would be the user’s campus ID.
-Privileges
-* Admin : provides full add/edit rights including access to the Admin page and the ability to delete contacts.
+All valid users are given view only access when logged into CORAL Organizations unless they have specifically been granted additional privileges. You only need to add specific user accounts for personnel that need more than view only privileges. The available privileges are:
-* Add/edit : provides ability to add/edit organization records and all available fields but does not grant access to Admin page and does not give permission to delete contacts.
+* **Admin:** provides full add/edit rights including access to the Admin page and the ability to delete contacts.
-* View only : provides only the ability to view existing organization records.
+* **Add/edit:** provides ability to add/edit organization records and all available fields but does not grant access to Admin page and does not give permission to delete contacts.
-
+* **View only:** provides only the ability to view existing organization records.
diff --git a/build/html/_sources/organizations2.txt b/build/html/_sources/organizations2.txt
deleted file mode 100644
index bc19083..0000000
--- a/build/html/_sources/organizations2.txt
+++ /dev/null
@@ -1,131 +0,0 @@
-### **Organizations User Guide**
-
-### About CORAL Organizations
-
-A component of Hesburgh Libraries locally developed ERM, CORAL Organizations provides a way to store and manage names, contacts and account information for the many publishers, providers, vendors, etc that libraries interact with on a daily basis all within a single searchable location.
-
-### Component Overview
-
-CORAL Organizations has three major components in the primary navigation at the top of each page.
-
-• Home
-
-• New Organization
-
-• Admin
-
-#### Home
-
-image of main home screen
-
-Search has been placed on the Home page as the primary point of entry into the organization records. There are two keyword searches available. The first keyword search 'Name (contains)' searches against organization name and organization alias. For example, AIP could be retrieved by searching for any or all of the words in American Institute of Physics or by the alias AIP. The second keyword search available is ‘Contact Name (contains)’. This allows the user to search for the name of a known contact (ex. Jane Smith) instead of searching for the name of the organization.
-
-Users also have the ability to search by an organization's role (ex. Publisher, provider, library, etc). And the last search option is more of an AZ browse for the retrieval of organizations by the first letter of the name.
-
-#### New Organization
-
-The purpose of the 'Parent' field is to relate multiple organizations together and to create an organization hierarchy. The field includes an auto-fill populated by existing organization records. The parent organization must already have an existing organization record in order for it to be assigned. Each organization may have only one parent assigned but multiple organizations may have the same parent thereby creating a useful parent-child hierarchy.
-
-image of Add New Organization screen
-
-Select New Organization from the main navigation to begin adding new organization records. The link will present the window on the right.
-
-'Name' is the name of the organization (i.e. MetaPress, Sage Publications, etc). This is the only required field.
-
-'Parent' is the name of the parent organization (i.e. Proquest as parent of Chadwyck-Healey).
-
-'Company URL' is meant to be the url of the organization’s homepage.
-
-'Role(s)' is the organization’s role. The values for this field can be customized through the Admin page.
-
-'Account Details' is meant for account numbers and general descriptive info about a library’s account with the organization. The ‘Notes’ field is for general notes.
-
-#### The Organization Record
-
-image of main Organization Record
-
-Here is an organization record for Cambridge Scientific Abstracts. The information on the record is split among five tabs. The sixth tab labeled Licenses is an interoperability feature with CORAL Licensing.
-
-The Organization Record
-
-* Organization: This tab displays the information found on the New Organizations screen explained on the previous page.
-
-* Aliases: This tab is for adding alternate names and acronyms so that the record can be retrieved using various names.
-
-* Contacts: This tab includes contact information for the organization (ex. Email, phone numbers for sales reps).
-
-* Accounts: This tab is for managing administrator accounts (ex. Username/password logins for usage statistics collection).
-
-* Issues: This tab is intended for recording major incidents with the organization and/or its resources (ex. Publisher changed servers and access was lost for several days).
-
-* Licenses: This tab will display links to the records in CORAL Licensing for all licenses from the organization. This is an interoperability feature which can be activated when both CORAL Licensing and CORAL Organizations are installed.
-
-##### Organization
-
-The figure above shows the organization tab for Cambridge Scientific Abstracts. Notice that this screenshot does not display the 'Account Details', ‘Notes’ or ‘Company URL’ fields that were found on the New Organization window on the previous page. These three fields are not displayed because no data was entered into those fields when the record was added. This was done in order to save space and to create a cleaner design. The ‘edit organization details’ link will open the same window as seen on the previous page so that the user can further edit the organization name, role, etc.
-
-In this example Cambridge Scientific Abstracts has been assigned ProQuest as the parent organization. The 'view' link next to ProQuest LLC will open the ProQuest organization record.
-
-##### Aliases
-
-image of example Alias CSA- Cambridge Scientific Abstracts
-
-The Aliases tab allows the user to add multiple aliases for the organization. In this example, the acronym CSA has been added. Each alias is assigned an alias type. The default values for the 'Alias Type' field are Alternate Name, Name Change and Acronym. These field values can be customized using the Admin page discussed later in this document.
-
-##### Contacts
-
-image of example
-
-The Contacts tab allows the user to add contact information such as phone numbers and email addresses for specific personnel as well as general support. There are two options for adding new contact information; 'add named contact' and ‘add unnamed contact’. These two links open the windows shown on the next page.
-
-Add Named Contact Add Unnamed Contact
-
-side by side images exmaples
-
-The 'add named contact' and ‘add unnamed contact’ links open the two windows above. The only difference between the two is that the unnamed contact has no Name or Title field. Generic contact numbers such as a technical support 1-800 number would be added as an unnamed contact. Specific personnel such as a license manager or sales representative would be added as a named contact.
-
-The values for the 'Role(s)' field can be customized through the Admin page discussed later in this document. Named and unnamed contacts use the same role values. The ‘Archived’ field is likely the only field that needs further explanation. Contacts can either be deleted or archived when the information is no longer accurate. Contacts that have the ‘Archived’ box checked are kept in the system but are collapsed beneath a ‘show archived contacts’ link so that all users know that the contact information is out of date. This was done for historical tracking purposes so that a library can record who their license managers, etc have been over the years. The ability to delete a contact has been restricted to users with admin privileges because of the chance that a contact might be deleted when it should only be archived.
-
-##### Accounts
-
-The Accounts tab is used for storing login information that library personnel use for site administration, gathering usage statistics, etc. Account login information can be entered in either CORAL Organizations or CORAL Resources. Account login information which is resource specific may be entered in CORAL Resources. Account login information that is not resource specific (ex. A single administrator login for all Gale databases) should be entered here in CORAL Organizations. Information stored at the organization level will be inherited by individual resources within CORAL Resources. The resource vs organization specific account information may be confusing but it will make more sense when CORAL Resources is installed along with CORAL Organizations.
-
-The 'add new external login' link opens the following window.
-
-##### Add New External Login
-
-image of Add Login form
-
-'Login Type' values can be customized. Default values are Admin, FTP, Marc, Statistics, Support, Other.
-
-'URL', ‘Username’ and ‘Password’ are self-explanatory.
-
-'Local Account Email' is the address of the library personnel registered on the account.
-
-Once again there is an extra notes field for additional information.
-
-##### Issues
-
-image of Issues tab
-
-The Issues tab is meant for recording general information about an organization that may be valuable over time. This could include anything but one example would be recording when an organization has frequent breaks in access or significant server downtimes. Another example would be having an organization that is often slow when it comes to sending out renewal invoices. The 'add new issue' link opens a new window which includes a date and notes field. It is a simple field but it may come in handy for recording the institutional knowledge that exists among various personnel.
-
-image of the License tab with example
-
-##### Licenses
-
-The Licenses tab is only available when CORAL Licensing has been installed and the interoperability enabled. This tab will provide links to the license records within CORAL Licensing for all licenses where the organization has been identified as the Publisher/Provider. The hyperlinked license name will open the license record in a new window.
-
-#### Admin
-
-The Admin page is where you can manage user privileges as well as edit the values for organization role, contact role, alias type and external login type. As with the other modules, CORAL Organizations is designed to work with your campus authentication system (see the technical documentation for details). All valid users are given view only access when logged into CORAL Organizations unless they have specifically been granted additional privileges. You only need to add specific user accounts for personnel that need more than view only privileges. The available privileges are 'view only', ‘add/edit’ and ‘admin’. The ‘add new user’ link on the Admin page opens the following window where ‘Login ID’ is the user’s campus ID.
-
-Privileges
-
-* Admin : provides full add/edit rights including access to the Admin page and the ability to delete contacts.
-
-* Add/edit : provides ability to add/edit organization records and all available fields but does not grant access to Admin page and does not give permission to delete contacts.
-
-* View only : provides only the ability to view existing organization records.
-
-side image with Add New User form
diff --git a/build/html/_sources/release.txt b/build/html/_sources/release.txt
index bcfbfff..c39ac58 100644
--- a/build/html/_sources/release.txt
+++ b/build/html/_sources/release.txt
@@ -1,7 +1,8 @@
Releasing a New Version of a Module
-----------------------------------
-- Before you release a new version of a CORAL module to the public, consider these tasks:
+Before you release a new version of a CORAL module to the public, consider these tasks:
+
- Download the latest module code from the master branch on github
- Install and test in a fresh location (not on top of a previous version)
- Test the upgrade process (from the previous version to the latest code version)
@@ -10,4 +11,6 @@ Releasing a New Version of a Module
- Make sure all other related documents have been updated (especially installation / upgrade guides)
- Add a tag to preserve this version (this can be by adding a "release" via github, or by adding a tag to a local git repo then pushed to github with: git push --tags)
- Announce new version of module via listserv and website
-- Create new milestone on github for next anticipated version of module (??)
\ No newline at end of file
+- Create new milestone on github for next anticipated version of module (??)
+
+**This is a test!**
\ No newline at end of file
diff --git a/build/html/_sources/resources.txt b/build/html/_sources/resources.txt
index 67c422b..a08b0eb 100644
--- a/build/html/_sources/resources.txt
+++ b/build/html/_sources/resources.txt
@@ -22,12 +22,14 @@ CORAL Resources Module User Guide
• My Queue
+ • File Import
+
• Admin
### Home
========
-{width="6.5in" height="4.0in"}
+
Home provides both search and AZ browse access to the resource records.
The *Name (contains)* field searches against resource name, resource
@@ -37,7 +39,7 @@ results can be exported to a spreadsheet using the excel icon in the
upper right corner. The exported file includes more fields than what are
displayed on the search results page.
-New Resource {width="6.5in" height="3.986111111111111in"}
+
All new resource records are added through this form. The form includes
@@ -69,7 +71,7 @@ another record with the same resource name already exists.
### Product
-\[insert product image here)
+
The resource record contains seven tabs where the information about the
resource is logically grouped. The first tab, *Product*, contains the
@@ -78,7 +80,7 @@ identifies and defines the resource.
### Edit product details
-**\[insert image here\]**
+
The information on the *Product* tab can be edited by following the
edit product details link or by using the edit icon on the tab. The
@@ -110,7 +112,7 @@ a record in CORAL.
### Add new note
-\[insert new note image here}
+
An additional notes feature has been added to the *Product*,
*Acquisitions* and *Access* tab. The note will be visible only on the
@@ -120,14 +122,14 @@ customized through the *Admin* page.
### Acquisitions
-\[insert image here\]
+
The Acquisitions tab contains details of the libraries’ acquisition of
the resource such as order number, cost, fund, license status, etc.
### Edit acquisitions information
-**\[insert image here\]**
+
The acquisitions information can be edited by using the edit
acquisitions information link or the matching edit icon. The
@@ -163,9 +165,13 @@ subscription end date. In order to implement the alerts feature the file
sendAlerts.php will need to be run as a nightly cron. See the technical
documentation and install guide for details.
+### Edit Cost History
+
+
+
### Edit license and status
-**\[insert image here\]**
+
The *Acquisitions* tab includes information about the relevant
license. Use the edit license and status link or the matching icon to
@@ -183,7 +189,7 @@ documentation and install guide for details.
### Access
-\[insert image here\]
+
The *Access* tab includes the information about how the resource is
accessed including things such as IP versus username/password
@@ -193,7 +199,7 @@ link or the matching edit icon.
### Edit access information
-**\[insert image here\]**
+
The values for all fields on the *Access* tab except for username and
password can be customized through the Admin page. The Authorized Site
@@ -220,7 +226,7 @@ link or the matching edit icon.
### Cataloging
- \[insert image here\]
+ 
The *Cataloging* tab includes data and workflow information related to
cataloging the resource, including things such as the URL of where the
@@ -231,6 +237,8 @@ link or the matching edit icon.
### Edit Cataloging Details
+
+
The Cataloging Status and Cataloging Type fields can be customized
through the Admin page. The Identifier is intended for \[I have no
idea\]. The Source URL is intended to be the source of the catalog
@@ -243,7 +251,7 @@ link or the matching edit icon.
### Contacts
-\[insert contacts image here\]
+
The *Contacts* tab is the same as is found on an organization record in
the Organizations Module. It is intended as a directory of contact
@@ -275,7 +283,7 @@ values for Login Type can be edited through the *Admin* page.
### Attachments
-\[insert image here\]
+
Additional documents relevant to the resource can be uploaded and made
available through the *Attachments* tab. The figure above shows a price
@@ -292,7 +300,7 @@ file. Multiple attachments are grouped and sorted by attachment type.
### Routing
-\[insert image here\]
+
The *Routing* tab shows the workflow through which the resource needs to
follow. The workflow and routing rules can be customized through the
@@ -337,7 +345,7 @@ system for record keeping purposes only.
### My Queue
-\[insert my queue image here\]
+
The *My Queue* page shows the user their recent activity and their
outstanding tasks. The page is divided into three tabs; Saved Requests,
@@ -356,9 +364,12 @@ on their association with a workflow group. Resources are removed from
the user’s queue once the outstanding workflow task on the resource’s
*Routing* tab is marked as complete.
+### File Import
+
+
### Admin
-\[insert admin image here\]
+
The *Admin* page is available only to users with admin privileges. It is
the page through which field values are customized and through which
@@ -366,7 +377,7 @@ user privilege and access is set.
### Edit User
-\[insert edit user here\]
+
The first tab on the page is for editing user accounts. There are three
privilege levels for the Resources Module; add/edit, view only, and
@@ -382,7 +393,7 @@ Accounts’ box on
### Workflow / User Group
-\[insert workflow/user group here\]
+
The *Workflow / User Group* tab contains the settings which control the
workflow routing features. The Resources Module allows for the creation
@@ -395,7 +406,7 @@ workflows are added using the add workflow link.
### Edit workflow
- \[insert edit workflow image here\]
+
The above figure shows the form through which workflows are created
and edited. Here again the workflow being edited is for resources
@@ -422,7 +433,7 @@ active once the parent step is marked as complete.
### Edit user group
-\[insert edit user group image here\]
+
Each step or task in a workflow must be assigned to a user group. Enter
a group name and a group email address. An email alert will be sent to
@@ -433,8 +444,6 @@ Queue pages.
### Other Admin Settings
-\[insert other admin settings here\]
-
There are many other fields which can be customized through the *Admin*
page. Select the field you wish to edit in the left hand column and then
follow the ‘add new’ links or the edit and delete icons to customize the
@@ -445,7 +454,7 @@ Settings.
### Alert settings
-\[insert alert settings here\]
+
These alert settings determine the functionality of the alert feature
associated with the subscription period end date on the *Acquisitions*
diff --git a/build/html/_sources/styleguide.txt b/build/html/_sources/styleguide.txt
deleted file mode 100644
index 3a7f319..0000000
--- a/build/html/_sources/styleguide.txt
+++ /dev/null
@@ -1,15 +0,0 @@
-CORAL Documentation Style Guide
--------------------------------
-
-### About the Style Guide ###
-
-The purpose of the style guide is to help keep the documentation consistent in style while at the same time providing tips for contributing to the CORAL Documentation Project (CDP) and other relevant information.
-
-### Setting Up ###
-
-The CDP is managed in a repo on GitHub found at [https://github.com/Coral-erm
-](https://github.com/Coral-erm "https://github.com/Coral-erm "). The project uses the [Sphinx Python Documentation Generator](http://www.sphinx-doc.org/en/stable/) and [CommonMark](http://commonmark.org/). The documentation files are edited in a combination of [reStructuredText](https://en.wikipedia.org/wiki/ReStructuredText) and [Markdown](https://en.wikipedia.org/wiki/Markdown), both markup languages supported by GitHub. In addition, [Read the Docs](https://readthedocs.org/) is used for hosting the documentation and providing additional documentation conversion and indexing tools.
-
-
-### Documentation Versioning ###
-
diff --git a/build/html/_sources/sushi.txt b/build/html/_sources/sushi.txt
index 36aff2e..5e3b478 100644
--- a/build/html/_sources/sushi.txt
+++ b/build/html/_sources/sushi.txt
@@ -73,4 +73,6 @@ Taylor and Francis
-Please let us know if you have tested and confirmed a working configuration for any other providers.
\ No newline at end of file
+Please let us know if you have tested and confirmed a working configuration for any other providers.
+
+This is a test!!!
diff --git a/build/html/_static/basic.css b/build/html/_static/basic.css
index 2b513f0..0b79414 100644
--- a/build/html/_static/basic.css
+++ b/build/html/_static/basic.css
@@ -494,6 +494,13 @@ pre {
overflow-y: hidden; /* fixes display issues on Chrome browsers */
}
+span.pre {
+ -moz-hyphens: none;
+ -ms-hyphens: none;
+ -webkit-hyphens: none;
+ hyphens: none;
+}
+
td.linenos pre {
padding: 5px 0px;
border: 0;
diff --git a/build/html/_static/searchtools.js b/build/html/_static/searchtools.js
index 066857c..a51e0dc 100644
--- a/build/html/_static/searchtools.js
+++ b/build/html/_static/searchtools.js
@@ -324,7 +324,7 @@ var Search = {
var searchterms = [];
var excluded = [];
var hlterms = [];
- var tmp = query.split(/\s+/);
+ var tmp = query.split(/\W+/);
var objectterms = [];
for (i = 0; i < tmp.length; i++) {
if (tmp[i] !== "") {
diff --git a/build/html/authentication.html b/build/html/authentication.html
index 2c9de93..8d979da 100644
--- a/build/html/authentication.html
+++ b/build/html/authentication.html
@@ -6,7 +6,7 @@
+. The project uses the Sphinx Python Documentation Generator and ReCommonMark. The documentation files are edited in a combination of reStructuredText and Markdown, both markup languages supported by GitHub. In addition, Read the Docs is used for hosting the documentation and providing additional documentation conversion and indexing tools.
+
Create a subfolder under /img using the same name as the markdown file in which the images will be used.
+
+
For example, the following folder name for organizations.md
+
/img/organizations/
+
+
+
+
Add images to the subfolder created in step 1. Name the images with a prefix identifying the markdown file they are associated with, separated Uppercase letters with a brief description of the image. Note: The underscore character causes GitHub to incorrectly process the image filenames in Markdown, which leads to problems in building files in the ReadtheDocs.
+
+
For example: organizationsAccountsView.png for a a screenshot of the Organization’s module accounts form.
You can personalize package content once it is imported. You can also custom package you already got even if it was not imported from GOKb. The “custom screen” display the current package’s children. If the checkbox is checked: the resource will be kept, else it will be removed from database when you will click on ‘Confirm customization’ button.
Search has been placed on the Home page as the primary point of
entry into the license records. The search runs against the fields
license name, document name, and publisher/provider. The fields are
@@ -89,7 +91,7 @@
Select New License from the main navigation to begin adding new
license records. The link will present the window on the
-right.
+right.
License Name: Name of the license record. A license record can group
together all licenses that are either related to each other or related
to the same resource. If you have licensed a package of electronic
@@ -471,7 +473,7 @@
A component of Hesburgh Libraries locally developed ERM, CORAL
-Licensing provides a way to store and access digital copies of current
-and expired license agreements and related documents as well as
-associated agreement metadata. The licensing module helps make library
-license agreements more accessible to personnel through select
-searchable metadata fields and assists institutions in tracking and
-using specific pieces of information included in legal agreements.
-CORAL Licensing is a flexible document management system, useful in
-anticipating a variety of agreements and institutional goals for
-managing agreements. The module allows users to identify license
-clauses most important to record and track from an institutional point
-of view. With related features like a clause comparison function, and
-ILL and course pack terms tools that can be implemented to deliver
-terms through other systems such as SFX, the CORAL Licensing module
-provides a way to make better use of permissions included in the
-license agreement.
-
Please note that screenshots and text in this document are just
-examples and do not necessarily reflect terms for a particular
-resource.
Search has been placed on the Home page as the primary point of
-entry into the license records. The search runs against the fields
-license name, document name, and publisher/provider. The fields are
-defined in the next section as we look at creating a new license
-record.
Select New License from the main navigation to begin adding new
-license records. The link will present the window on the right.
-
‘License Name’ is the name of the license record. For example, a
-license record named Cambridge University Press Journals would
-contain any and all license documents pertaining to the Cambridge
-University Press journals.
-
‘Publisher/Provider’ is the name of the licensing organization. In
-this example Cambridge University Press would be the
-publisher/provider.
-
‘Consortium’ would be used when the licensed resources are obtained
-through a consortium.
-
The License Name may seem a bit arbitrary but it makes more sense when
-you think about a license record as a way to group together all
-licenses that are either related to each other or related to the same
-resource. Let us say for example that you have licensed a package of
-electronic journals from Springer and have over the years collected
-several licenses and amendments for that package. You can place all of
-those documents on the same license record and then you need to give
-the license record a name which gives some indication as to the
-documents found on that record. In this example ‘Springer Online
-Journals’ may be a valid license name.
-
Let us also assume that you have licensed a set of eBooks from
-Springer as well and that the license for the eBook is in no way
-related to the license for the journals. You now have two options for
-loading the eBook license. You can create a new license record called
-Springer eBooks and load the license documents there or you can add
-the eBook license to the existing Springer Online Journals license.
-If you choose the latter then you could also consider changing the
-license name Springer Online Journals to something such as Springer
-Online Products to more accurately reflect all the documents
-contained on the record.
-
Interoperability note: The publisher/provider field has an auto-fill
-feature which is populated from the organizations listed in CORAL
-Organizations. CORAL Licensing will manage publisher/provider names on
-its own if you have not installed CORAL Organizations or have disabled
-the interoperability. The publisher/provider names are managed and
-edited in the CORAL Licensing Admin area when the interoperability
-is disabled.
Here is a new license record which has just been created for
-Cambridge University Press Online Journals. To the right of the
-license name are the options to remove the license or to edit the
-name, publisher/provider and consortia. The publisher/provider name is
-hyperlinked and will take the user to the Cambridge University Press
-record within CORAL Organizations. Here you can also enter a license
-record status in the ‘License Status’ field to the far right of the
-license name. CORAL Licensing includes the following default statuses.
-
License Status (definition)
-
• Awaiting Document (license record created but scanned license not
-yet added)
-
• Complete (license record is complete, no additional work required)
-
• Document Only (document loaded with expressions not identified or
-loaded)
-
• Editing Expressions (document loaded and currently adding license
-terms/expressions)
-
• NLR (no license required)
-
License Status values can be edited, added or deleted through the
-Admin section detailed later in this document. The default values
-are simply suggestions for how an institution might consider tracking
-agreements and to indicate the purpose of the field.
-
The license record has four sections located on the left-hand column;
-Documents, Expressions, SFX Links and Attachments
The Documents tab contains all the documents for each license record.
-Any document may be uploaded to the system including licenses,
-amendments, order forms, purchase requests, or any other important
-document. Select ‘upload new document’ to begin.
The ‘upload new document’ link opens the window on the right. Here you
-can fill out the initial details of the document and upload the actual
-file. Document Name is the only required field.
-
‘Effective date’ is the effective date of the agreement, if identified
-and available.
-
‘Document Type’ identifies what type of document this is (ex. Agreement,
-amendment, order form, etc).
-
‘Parent’ identifies any parent document (ex. A parent document would be
-assigned when uploading an amendment).
-
‘Name’ is the title of the document, usually taken directly from the
-license document (ex. Cambridge University Press Site License
-Agreement).
-
‘File’- browse and upload a scanned copy of the actual document.
-
‘Archived’ is used to identify documents which are no longer current
-or have been superseded by another agreement. Archived documents are
-sorted separate from current documents and are collapsed beneath a
-show/hide link to save screen space. Archiving a document does not
-delete it from the system. It also does not delete any expressions
-attached to that document.
-
‘Document Type’ is another customizable field which allows each
-library to set their own terminology. The software comes with the
-following types included.
Once added the documents will display on the Documents tab sorted
-first by Document Type (agreements sort together, order forms sort
-together, etc) and then by signature date with most recent first.
-Multiple signatures for both licensee and licensor can be added using
-the ‘add signatures’ link. On the right hand column are the links to
-view, edit, and delete each document. Now that the documents are
-loaded the next step is to begin adding expressions. Please note that
-Expressions are not required. You should however assign an appropriate
-License Status to the record that indicates it is a document only
-record.
The Expressions tab is where the expressions or clauses of the license
-are entered. You may enter any expression type that you wish. The
-software comes with the following expression types already defined but
-again the field is customizable and allows you to enter the types of
-your choice.
The ‘add new expression’ link opens the window on the right. From this
-window you can add expressions for the documents that have been
-previously loaded.
-
‘Document’ is the document name for which you want to add a new
-expression. The drop-down is pre-populated from the existing document
-names in the specific license record. This is a required field.
-
‘Expression Type’ is the type of expression you wish to add
-(interlibrary loan terms, course pack rights, etc). This is a required
-field.
-
‘Qualifier’ is another customizable field which can be used to qualify
-particular expressions. For example, a qualifier of Permitted or
-Prohibited may be appropriate for an Interlibrary Loan expression.
-You may choose to ignore this field or choose to use it in a different
-fashion for other expression types.
-
‘Document Text’ is for the actual text of the license clause. An
-interlibrary loan expression has been added in the following figure.
In this example an Interlibrary Loan expression has been added along
-with a snippet of the license text and a qualifier of Permitted has
-been added noting that the item does allow for ILL. The
-
actual legal text can be quite confusing so the next step is to add a
-Display Note which can hold an interpretation of the text of the
-clause that can be used for public display.
The ‘add/view display notes’ link opens a window which allows you to
-enter multiple display notes. It also displays the Document Text on
-that same window so that you can refer back to it while adding the
-notes. The sort order of multiple display notes can also be adjusted
-through this same window. The following figure shows a completed
-Display Notes window.
-
There are two types of expression notes in CORAL licensing; Display
-Notes and Internal Notes. You can set the note type to either Internal
-or Display for each expression type on the ‘Admin’ page detailed later
-in this document. The two note types (internal and display) were added
-so that a distinction could be made between expressions and notes that
-were intended to be displayed outside the module, for instance in one
-of the terms tools, and those that were for internal use only. The
-Display Notes which are intended to be shared have additional
-functionality built in that the Internal Notes lack. In the following
-figure you will see the completed interlibrary loan expression. In
-this example the Interlibrary Loan expression type has been set to use
-Display Notes and as such the expression is presented with an
-additional checkbox to the left of the Document Text. Internal Notes
-do not receive this checkbox. When the licensing librarian or other
-appropriate personnel has finished editing the notes and expression
-he/she can check this box which indicates that the expression is
-finished and it makes the expression available through the Terms Tool
-Report page. An email is then generated by the system indicating that
-a new expression has been completed and is ready for display. You can
-edit the recipients of this email in the Admin page.
-
If you choose not to use the Terms Tool Report page you may turn it
-off as explained in the technical documentation guide. This will also
-remove the display note checkbox and email functionality. It will also
-remove the SFX Links tab which is explained next.
The above figure is the completed expression with document text,
-qualifier and display notes. Qualifier may not be appropriate for
-certain expression types. The intended use of the qualifier is to
-further document permitted/prohibited distinctions such as
-interlibrary loan, course packs and ereserves. You may continue to add
-as many expressions as needed for some or all documents.
Once the expressions or terms of the license are known, the next
-question to ask is ‘Which journals are covered by these terms?’.
-That’s where the SFX Links tab comes into play. Using this tab it is
-possible to relate a specific license to the covered journals in a
-specific SFX target or package. In this example the Cambridge
-University Press Site License Agreement is being associated with the
-Cambridge Journals Online target in SFX (Cambridge Journals Online is
-the SFX target public name). This SFX – License connection allows for
-the delivery of license terms through the SFX menu as detailed in the
-Terms Tool User Guide. It is true that not every institution uses SFX.
-The SFX Links tab could be renamed and/or repurposed for use with
-other openurl resolvers or journal management systems. This
-
tab is meant to be used in conjunction with the Terms Tool and can be
-disabled along with the Terms Tool Report page for those who do not
-wish to use it.
For any resource there may be documents in addition to the actual
-license that are important to retain. Title lists and email
-correspondence are two that may be the most common. The Attachments
-tab allows you to upload these additional documents to the license
-record. The above figure shows an email that has been uploaded with
-the date and a description of the file. In this case the attachment is
-an email from the publisher detailing additional restrictions on the
-resource. The date field is not automatically entered by the system so
-it does not have to be the date the file was loaded into CORAL
-Licensing. The intention of the date field was to be the date the
-attached document was received but since the date is manually chosen
-it can be any date of your choice. The ‘view attachment 1’ link will
-open the uploaded file.
The Licenses in Progress page will show the licenses that are not
-yet complete. It is intended to be used by the licensing staff as a
-queue of outstanding licenses. It has been coded to show licenses of
-status Awaiting Document or Editing Expressions and will also show new
-licenses which have not yet been given any status. The hyperlinked
-License Name will take you into the license record.
Expression Comparison allows the user to see all the instances of a
-specific expression type across all documents in a single screen or
-view. The ‘Limit by Expression Type’ dropdown allows the user to
-select from among all defined expression types. In the figure above
-the display notes and document text have been removed for reasons of
-confidentiality. In place of
<
- Display Notes removed
>
- and
<
-
-Document Text removed
>
- users would see the actual notes and
-document text that were entered. This allows licensing or relevant
-personnel to compare language for each expression type across all
-documents. It could be an immensely powerful tool when attempting to
-come up with recommended language during negotiations. The user may
-also add new display notes, open the license record and open the
-actual document from this page.
-
Expression Comparison is intended for personnel that need quick
-access to all expressions in the system. Other library staff however,
-may only need access to specific types of expressions and this
-particular page may be information overload. The Terms Tool Report
-page was developed for these other users.
Once again the notes and document text have been removed from the
-screenshot. Terms Tool Report provides access to only the
-expressions using display notes and which have been identified as
-being complete by the licensing librarian using the terms tool
-checkbox mentioned earlier. As such it will not display unfinished
-expressions which the licensing librarian may still be working on.
-Another difference between Terms Tool Report and Expression
-Comparison is that this page does not offer any links for editing the
-record. While similar in function to Expression Comparison this page
-was added in order to serve a user group which does not need the full
-access provided by the Expression Comparison page.
-
The main points to remember for this page are that it displays
-expressions which use display notes but only those that have been
-approved for display. It is possible to turn off Terms Tool Report
-and hide it from display if you do not wish to use it. Turning off the
-Terms Tool Report will also disable the SFX Links tab on the license
-record as well as the terms tool checkbox used to indicate that a
-Display Note has been completed and approved for display. Please see
-the Terms Tool User Guide for more information on how Terms Tool
-Report can be used and on how it can be used to push out license
-terms to other systems.
The Admin page is where you will edit Expression Types, Document
-Types, Signature Types and
-
License Statuses. Each of these fields can have as many values as
-needed so that the system can better
-
meet local needs. Admin is also where you will edit and manage user
-permissions. CORAL Licensing has been built with the ability to limit
-access to select individuals given the confidential nature of license
-agreements. Users may not access CORAL Licensing until they are first
-set up with an account by an administrator. The following figure shows
-the ‘add new user’ window available from the Admin page.
-
‘Login ID’ will be the user’s unique ID in your local campus
-authentication system. See the technical documentation for more
-details on authentication.
-
‘Privilege’ is the user’s level of access (i.e. read only, etc).
-
‘Terms Tool Email’ – Enter email address if you wish the user to
-receive email notification when the terms tool box is checked for a
-given expression. Leave this blank for all others.
-
The values available in the Privilege field deserve further
-explanation.
-
Privileges
-
• Admin users have complete add/edit rights and can remove licenses
-and associated fields.
-
Access to the Admin page, the SFX Links tab on the license record
-and the terms tool checkbox is restricted to users with Admin
-privileges.
-
• Add/Edit users can add, edit, or remove licenses and associated
-fields.
-
• View Only users can view all license information and are allowed
-access to the uploaded documents.
-
• Restricted users can view all license information but are not
-allowed access to the uploaded documents.
-
Admin, Add/Edit and View Only are the same privileges used in the
-other CORAL modules. Restricted is an extra privilege used only in
-CORAL Licensing in order to restrict access to the actual license
-agreements that have been uploaded to the system.
Developed by Texas A&M University, CORAL Management provides a way to store and access digital copies of documents related to the overall management of electronic resources.
Document records are listed alphabetically by name and the name field can be searched. Additionally, the records can be filtered by category and document type.
Select New Document from the main navigation to begin adding new document records. This will open the New Document pop-up window.
+
+
+
Name: The document name to be uploaded. The Management module only allows one active document per record so a document named Sample Letter to Excess Download Offender would only include a copy of the letter.
+
Description: A brief explanation of the document, if necessary.
+
Type: The type of document. The options listed in the dropdown box may be created from the Admin tab or by using the ‘add type’ link under the dropdown box. In the case of the Sample Letter to Excess Download Offender, the type could be template.
+
Last Document Revision: The date the document was last revised. If no date is entered, today’s date is used by default.
+
Categories: The group of documents to which the document belongs. A document can be included in more than one category. For example, the document License Agreement Checklist could be in both an ‘Processes and Procedures’ category and a ‘Licensing’ category. Categories may be created from the Admin tab or by using the ‘add category’ link under the ‘Categories’ selection box.
+
+
+
File: Selecting the ‘Browse…’ button opens the navigation pane used to browse and upload the document.
+
Archived: Used to identify documents that have been superseded by a newer version of the document.
+
Add Optional Note: Allows notes to be linked to the document by opening up two additional fields.
+
+
+
Note provides a space to add any notes about the document. Note Type provides a way to categorize the type of note. The options listed in the dropdown box may be created from the Admin tab or by using the ‘add type’ link under the dropdown box.
Once a document record has been created, the document record opens. A document record can also be opened by selecting it from the ‘Home’ screen.
+
+
The above record is for a License Agreement Checklist. Below the name is the description of the document, the associated categories, the documents creation date and creator, and the date the record was last updated and by whom.
+
In this example, there are two archived versions of the checklist as evidenced by the “2 archive(s) available” note. Selecting ‘show archives’ makes these copies visible and accessible. To add another archived version, select ‘upload archived document’ and fill in the appropriate information. There can only be one current/active document. To add a new version of a document, the current document must be archived first. Once that happens, an ‘upload new document’ link will display. Select this and complete the necessary information to add the new version.
CORAL Organizations provides a way to manage contact and account information for variety of organizations customized by the user. Some out-of-the-box organizations include publisher, provider, vendor and consortium.
+
CORAL Organizations provides a way to manage contact and account information for variety of organizations customized by the user. Some out-of-the-box organizations include publishers, providers, vendors and consortia.
CORAL TIP: New installations pre-populate the Organizations module with numerous organization names.
The home screen contains a search on the left and a list of organizations on the right. The up and down arrows in the table header can be used to sort the organizations by name, alias, parent, or role.
-
+<<<<<<< HEAD
+
+
There are four facets for search. These facets can be used in conjunction.
+
Name (contains): Searches against organization name and alias. For example, searching with AIP will retrieve the American Institute of Physics when AIP has been designated as an alias for this publisher.
+
Role: Provides the option to limit a search by an organization’s role (ex. publisher, provider, library, consortium, etc)
+
Contact Name (contains): Search for the name of a known contact (ex. Jane Smith) instead of searching for the name of the organization.
+
Starts with: Browse all the entries alphabetically by the first letter.
+=======
+
There are four facets for search:
**Name (contains): **Searches against organization name and alias. For example, searching with AIP will retrieve the American Institute of Physics when AIP has been designated as an alias for this publisher.
@@ -67,82 +77,90 @@
**Starts with: **this A-to-Z browsing list can be used to browse all the entries alphabetically by the first letter.
Select New Organization from the main navigation to begin adding new organization records.
Name: Name of the organization (i.e. MetaPress, Sage Publications, etc). This is the only required field.
Parent: Name of the parent organization (i.e. Proquest as parent of Chadwyck-Healey). The purpose of the ‘Parent’ field is to relate multiple organizations together and to create an organization hierarchy. The field includes an auto-fill populated by existing organization records. The parent organization must already have an existing organization record in order for it to be assigned. Each organization may have only one parent assigned but multiple organizations may have the same parent thereby creating a useful parent-child hierarchy.
-
Company URL: Intendedmeant to be the url of the organization’s homepage.
-
**Role(s): **the organization’s role. The values for this field can be customized through the Adminpage.
-
**Account Details: **Account numbers or general descriptive info about a library’s account with the organization.
+
Company URL: The URL of the organization’s homepage.
+
Role(s): The organization’s role. The values for this field can be customized through the Adminpage.
+
Account Details: Account numbers or general descriptive info about a library’s account with the organization.
Here is an organization record for Cambridge Scientific Abstracts. The information on the record is split among six tabs.
+=======
+
Here is an organization record for Cambridge Scientific Abstracts. The information on the record is split among five tabs. The sixth tab labeled Licenses appears when the CORAL Licensing module is installed and enabled.
+>>>>>>> refs/remotes/scottvieira/master
-
**Organization: **Displays the information found on the New Organizations screen explained on the previous page.
+
Organization: Displays the information found on the New Organizations screen explained on the previous page.
Aliases: Alternate names and acronyms so that the record can be retrieved using various names.
Contacts: Includes contact information for the organization (ex. Email, phone numbers for sales reps).
-
**Accounts: **Logins for managing administrator accounts (ex. Username/password logins for usage statistics collection).
-
**Issues: **Recording major incidents with the organization and/or its resources (ex. Publisher changed servers and access was lost for several days).
-
Licenses: Links to the records in CORAL Licensing for all licenses from the organization. This is an interoperability feature which can be activated when both CORAL Licensing and CORAL Organizations are installed.
+
Accounts: Logins for managing administrator accounts (ex. Username/password logins for usage statistics collection).
+
Issues: Information about an organization that may be valuable over time such as notes about frequent breaks in access or an oddity in an organization’s invoicing process.
+
Licenses: Links to the records in CORAL Licensing for all licenses from the organization.
The figure above shows the organization tab for Cambridge Scientific Abstracts. Notice that this screenshot does not display the ‘Account Details’, ‘Notes’ or ‘Company URL’ fields that were found on the New Organization window on the previous page. These three fields are not displayed because no data was entered into those fields when the record was added.
-
The ‘edit organization details’ link will open up a window that allows you to edit the information originally entered in the New Organization’s window.
-
In this example Cambridge Scientific Abstracts has been assigned ProQuest as the parent organization. The ‘view’ link next to ProQuest LLC will open the ProQuest organization record.
+
The ‘edit organization details’ link , will open up a window that allows you to edit the information originally entered in the New Organization’s window.
+
In this example Cambridge Scientific Abstracts has been assigned ProQuest as the parent organization. The ‘view’ link
+ next to ProQuest LLC will open the ProQuest organization record.
The Aliases tab allows the user to add multiple aliases for the organization. The default alias types are Alternative Name, Name Change, and Acronym. These fields can be customized using the Adminpage
The Contacts tab allows the user to add contact information for both specific personnel and general support. None of the fields are required except for Role(s).
-
The values for the ‘Role(s)’ field can be customized through the Adminpage. When the contact is no longer accurate, it can either be deleted or archived for historical tracking purposes. Contacts that have the ‘Archived’ box checked are kept in the system but are collapsed beneath a ‘show archived contacts’ link so that all users know that the contact information is out of date.
-
The ability to delete a contact has been restricted to users with admin privileges.
+
The values for the ‘Role(s)’ field can be customized through the Adminpage. When the contact is no longer accurate, it can either be deleted (deletion is restricted to users with admin privileges) or archived for historical tracking purposes. Contacts that have the ‘Archived’ box checked are kept in the system but are collapsed beneath a ‘Show Archived Contacts’ link so that all users know that the contact information is out of date.
The Accounts tab is used for storing login information that library personnel use for site administration, gathering usage statistics, etc.
-
Account login information can be entered in either CORAL Organizations or if installed, CORAL Resources. Account login information which is resource specific may be entered in CORAL Resources. Account login information that is not resource specific (ex. A single administrator login for all Gale databases) should be entered here in CORAL Organizations. Information stored at the organization level will be inherited by individual resources within CORAL Resources.
-
Add new login information by selecting the ‘add new external login’ link.
-
+
Account login information can be entered in either CORAL Organizations or CORAL Resources. Account login information which is resource specific may be entered in CORAL Resources. Account login information that is not resource specific (ex. A single administrator login for all Gale databases) should be entered here in CORAL Organizations. Information stored at the organization level will be inherited by individual resources within CORAL Resources.
+
Add new login information by selecting the ‘Add New External Login’ link.
Most of the fields are self-explanatory, with the exception of
**Local Account Email: ** The address of the library personnel registered on the account.
+
Login Type: Category of login. Default values are Admin, FTP, Marc, Statistics, Support, Other. You create additional login types using through the Adminpage
+
Local Account Email: The address of the library personnel registered on the account.
The Issues tab is meant for recording general information about an organization that may be valuable over time. One example would be recording when an organization has frequent breaks in access or significant server downtimes. Another example would be having an organization that is often slow when it comes to sending out renewal invoices. The ‘add new issue’ link opens a new window which includes a date and notes field. It is a simple field but it may come in handy for recording the institutional knowledge that exists among various personnel.
+
+
The Issues tab is meant for recording general information about an organization that may be valuable over time. One example would be recording when an organization has frequent breaks in access or significant server downtimes. Another example would be having an organization that is often slow when it comes to sending out renewal invoices. The ‘add new issue’ link opens a new window which includes a date and notes field. This field can be handy for recording the institutional knowledge that exists among various personnel.
The Licenses tab is only available when CORAL Licensing has been installed and the interoperability enabled. This tab will provide links to the license records within CORAL Licensing for all licenses where the organization has been identified as the Publisher/Provider. The hyperlinked license name will open the license record in a new window.
+
+
The Licenses tab provides links to the license records entered into CORAL Licensing for all licenses where the organization has been identified as the Publisher/Provider. The hyperlinked license name will open the license record in a new window.
The Admin page is where you can manage user privileges as well as edit the values for organization role, contact role, alias type and external login type. As with the other modules, CORAL Organizations is designed to work with your campus authentication system (see the technical documentation for details). All valid users are given view only access when logged into CORAL Organizations unless they have specifically been granted additional privileges. You only need to add specific user accounts for personnel that need more than view only privileges. The available privileges are ‘view only’, ‘add/edit’ and ‘admin’. The ‘add new user’ link on the Admin page opens the following window where ‘Login ID’ is the user’s campus ID.
-
Privileges
+
The Admin page is where you can manage the module’s user privileges as well as edit the values for organization role, contact role, alias type, external login type, and issue type.
+
#####Adding New Users####
+The ‘add new user’ link on the Admin page opens the following window.
+
If you utilize your institution’s existing authentication system, the ‘Login ID’ would be the user’s campus ID.
+
All valid users are given view only access when logged into CORAL Organizations unless they have specifically been granted additional privileges. You only need to add specific user accounts for personnel that need more than view only privileges. The available privileges are:
-
Admin : provides full add/edit rights including access to the Admin page and the ability to delete contacts.
-
Add/edit : provides ability to add/edit organization records and all available fields but does not grant access to Admin page and does not give permission to delete contacts.
-
View only : provides only the ability to view existing organization records.
+
Admin: provides full add/edit rights including access to the Admin page and the ability to delete contacts.
+
Add/edit: provides ability to add/edit organization records and all available fields but does not grant access to Admin page and does not give permission to delete contacts.
+
View only: provides only the ability to view existing organization records.
A component of Hesburgh Libraries locally developed ERM, CORAL Organizations provides a way to store and manage names, contacts and account information for the many publishers, providers, vendors, etc that libraries interact with on a daily basis all within a single searchable location.
Search has been placed on the Home page as the primary point of entry into the organization records. There are two keyword searches available. The first keyword search ‘Name (contains)’ searches against organization name and organization alias. For example, AIP could be retrieved by searching for any or all of the words in American Institute of Physics or by the alias AIP. The second keyword search available is ‘Contact Name (contains)’. This allows the user to search for the name of a known contact (ex. Jane Smith) instead of searching for the name of the organization.
-
Users also have the ability to search by an organization’s role (ex. Publisher, provider, library, etc). And the last search option is more of an AZ browse for the retrieval of organizations by the first letter of the name.
The purpose of the ‘Parent’ field is to relate multiple organizations together and to create an organization hierarchy. The field includes an auto-fill populated by existing organization records. The parent organization must already have an existing organization record in order for it to be assigned. Each organization may have only one parent assigned but multiple organizations may have the same parent thereby creating a useful parent-child hierarchy.
-
image of Add New Organization screen
-
Select New Organization from the main navigation to begin adding new organization records. The link will present the window on the right.
-
‘Name’ is the name of the organization (i.e. MetaPress, Sage Publications, etc). This is the only required field.
-
‘Parent’ is the name of the parent organization (i.e. Proquest as parent of Chadwyck-Healey).
-
‘Company URL’ is meant to be the url of the organization’s homepage.
-
‘Role(s)’ is the organization’s role. The values for this field can be customized through the Admin page.
-
‘Account Details’ is meant for account numbers and general descriptive info about a library’s account with the organization. The ‘Notes’ field is for general notes.
Here is an organization record for Cambridge Scientific Abstracts. The information on the record is split among five tabs. The sixth tab labeled Licenses is an interoperability feature with CORAL Licensing.
-
The Organization Record
-
-
Organization: This tab displays the information found on the New Organizations screen explained on the previous page.
-
Aliases: This tab is for adding alternate names and acronyms so that the record can be retrieved using various names.
-
Contacts: This tab includes contact information for the organization (ex. Email, phone numbers for sales reps).
-
Accounts: This tab is for managing administrator accounts (ex. Username/password logins for usage statistics collection).
-
Issues: This tab is intended for recording major incidents with the organization and/or its resources (ex. Publisher changed servers and access was lost for several days).
-
Licenses: This tab will display links to the records in CORAL Licensing for all licenses from the organization. This is an interoperability feature which can be activated when both CORAL Licensing and CORAL Organizations are installed.
The figure above shows the organization tab for Cambridge Scientific Abstracts. Notice that this screenshot does not display the ‘Account Details’, ‘Notes’ or ‘Company URL’ fields that were found on the New Organization window on the previous page. These three fields are not displayed because no data was entered into those fields when the record was added. This was done in order to save space and to create a cleaner design. The ‘edit organization details’ link will open the same window as seen on the previous page so that the user can further edit the organization name, role, etc.
-
In this example Cambridge Scientific Abstracts has been assigned ProQuest as the parent organization. The ‘view’ link next to ProQuest LLC will open the ProQuest organization record.
image of example Alias CSA- Cambridge Scientific Abstracts
-
The Aliases tab allows the user to add multiple aliases for the organization. In this example, the acronym CSA has been added. Each alias is assigned an alias type. The default values for the ‘Alias Type’ field are Alternate Name, Name Change and Acronym. These field values can be customized using the Admin page discussed later in this document.
The Contacts tab allows the user to add contact information such as phone numbers and email addresses for specific personnel as well as general support. There are two options for adding new contact information; ‘add named contact’ and ‘add unnamed contact’. These two links open the windows shown on the next page.
-
Add Named Contact Add Unnamed Contact
-
side by side images exmaples
-
The ‘add named contact’ and ‘add unnamed contact’ links open the two windows above. The only difference between the two is that the unnamed contact has no Name or Title field. Generic contact numbers such as a technical support 1-800 number would be added as an unnamed contact. Specific personnel such as a license manager or sales representative would be added as a named contact.
-
The values for the ‘Role(s)’ field can be customized through the Admin page discussed later in this document. Named and unnamed contacts use the same role values. The ‘Archived’ field is likely the only field that needs further explanation. Contacts can either be deleted or archived when the information is no longer accurate. Contacts that have the ‘Archived’ box checked are kept in the system but are collapsed beneath a ‘show archived contacts’ link so that all users know that the contact information is out of date. This was done for historical tracking purposes so that a library can record who their license managers, etc have been over the years. The ability to delete a contact has been restricted to users with admin privileges because of the chance that a contact might be deleted when it should only be archived.
The Accounts tab is used for storing login information that library personnel use for site administration, gathering usage statistics, etc. Account login information can be entered in either CORAL Organizations or CORAL Resources. Account login information which is resource specific may be entered in CORAL Resources. Account login information that is not resource specific (ex. A single administrator login for all Gale databases) should be entered here in CORAL Organizations. Information stored at the organization level will be inherited by individual resources within CORAL Resources. The resource vs organization specific account information may be confusing but it will make more sense when CORAL Resources is installed along with CORAL Organizations.
-
The ‘add new external login’ link opens the following window.
The Issues tab is meant for recording general information about an organization that may be valuable over time. This could include anything but one example would be recording when an organization has frequent breaks in access or significant server downtimes. Another example would be having an organization that is often slow when it comes to sending out renewal invoices. The ‘add new issue’ link opens a new window which includes a date and notes field. It is a simple field but it may come in handy for recording the institutional knowledge that exists among various personnel.
The Licenses tab is only available when CORAL Licensing has been installed and the interoperability enabled. This tab will provide links to the license records within CORAL Licensing for all licenses where the organization has been identified as the Publisher/Provider. The hyperlinked license name will open the license record in a new window.
The Admin page is where you can manage user privileges as well as edit the values for organization role, contact role, alias type and external login type. As with the other modules, CORAL Organizations is designed to work with your campus authentication system (see the technical documentation for details). All valid users are given view only access when logged into CORAL Organizations unless they have specifically been granted additional privileges. You only need to add specific user accounts for personnel that need more than view only privileges. The available privileges are ‘view only’, ‘add/edit’ and ‘admin’. The ‘add new user’ link on the Admin page opens the following window where ‘Login ID’ is the user’s campus ID.
-
Privileges
-
-
Admin : provides full add/edit rights including access to the Admin page and the ability to delete contacts.
-
Add/edit : provides ability to add/edit organization records and all available fields but does not grant access to Admin page and does not give permission to delete contacts.
-
View only : provides only the ability to view existing organization records.
Home provides both search and AZ browse access to the resource records.
The Name (contains) field searches against resource name, resource
alias, parent resource name and organization name. Multiple fields can
@@ -73,7 +76,7 @@
results can be exported to a spreadsheet using the excel icon in the
upper right corner. The exported file includes more fields than what are
displayed on the search results page.
-
New Resource {width=”6.5in” height=”3.986111111111111in”}
+
All new resource records are added through this form. The form includes
only select fields which are the most critical for processing new
resource requests. The goal was to provide collection managers with a
@@ -101,7 +104,7 @@
The resource record contains seven tabs where the information about the
resource is logically grouped. The first tab, Product, contains the
descriptive information such as name, alias, issn, publisher, etc which
@@ -109,7 +112,7 @@
The information on the Product tab can be edited by following the
edit product details link or by using the edit icon on the tab. The
Name, Description, URL, Format and Resource Type fields come from the
@@ -138,7 +141,7 @@
An additional notes feature has been added to the Product,
Acquisitions and Access tab. The note will be visible only on the
tab on which it is added. The Note Type field has been included to
@@ -147,13 +150,13 @@
The acquisitions information can be edited by using the edit
acquisitions information link or the matching edit icon. The
information here is meant to provide context to the local acquisitions
@@ -186,9 +189,13 @@
sendAlerts.php will need to be run as a nightly cron. See the technical
documentation and install guide for details.
The Acquisitions tab includes information about the relevant
license. Use the edit license and status link or the matching icon to
update the license information. The values for the Licensing Status
@@ -205,7 +212,7 @@
The Access tab includes the information about how the resource is
accessed including things such as IP versus username/password
authentication, simultaneous user limits, authorized sites, etc. The
@@ -214,7 +221,7 @@
The values for all fields on the Access tab except for username and
password can be customized through the Admin page. The Authorized Site
field is intended to indicate the sites or libraries which are
@@ -238,7 +245,7 @@
The Cataloging tab includes data and workflow information related to
cataloging the resource, including things such as the URL of where the
cataloging records are coming from, cataloging type, cataloging
@@ -248,6 +255,7 @@
The Cataloging Status and Cataloging Type fields can be customized
through the Admin page. The Identifier is intended for [I have no
idea]. The Source URL is intended to be the source of the catalog
@@ -260,7 +268,7 @@
The Contacts tab is the same as is found on an organization record in
the Organizations Module. It is intended as a directory of contact
information for publishers, vendors, etc. Contacts can be added directly
@@ -290,7 +298,7 @@
Additional documents relevant to the resource can be uploaded and made
available through the Attachments tab. The figure above shows a price
quote which was received from the publisher. The arrow to the right of
@@ -305,7 +313,7 @@
The Routing tab shows the workflow through which the resource needs to
follow. The workflow and routing rules can be customized through the
Admin page. That process is described later on in this document.
The My Queue page shows the user their recent activity and their
outstanding tasks. The page is divided into three tabs; Saved Requests,
Outstanding Tasks, and Submitted Requests. The Saved Requests tab
@@ -362,16 +370,20 @@
the user’s queue once the outstanding workflow task on the resource’s
Routing tab is marked as complete.
The Admin page is available only to users with admin privileges. It is
the page through which field values are customized and through which
user privilege and access is set.
The first tab on the page is for editing user accounts. There are three
privilege levels for the Resources Module; add/edit, view only, and
admin. View only is the default privilege for all users who do not have
@@ -385,7 +397,7 @@
The Workflow / User Group tab contains the settings which control the
workflow routing features. The Resources Module allows for the creation
of multiple workflow rules based on resource type. The figure above
@@ -397,7 +409,7 @@
The above figure shows the form through which workflows are created
and edited. Here again the workflow being edited is for resources
where the Acquisitions Type is ‘Paid’ and the Format is ‘Electronic’.
@@ -421,7 +433,7 @@
Each step or task in a workflow must be assigned to a user group. Enter
a group name and a group email address. An email alert will be sent to
this address when a new workflow step assigned to the group becomes
@@ -431,7 +443,6 @@
There are many other fields which can be customized through the Admin
page. Select the field you wish to edit in the left hand column and then
follow the ‘add new’ links or the edit and delete icons to customize the
@@ -442,7 +453,7 @@
These alert settings determine the functionality of the alert feature
associated with the subscription period end date on the Acquisitions
tab of the resource record. Enter the email address to which the alert
@@ -473,6 +484,7 @@
The purpose of the style guide is to help keep the documentation consistent in style while at the same time providing tips for contributing to the CORAL Documentation Project (CDP) and other relevant information.