Terminology

Creating a new Agreement and/or License

Some initial notes: 

My new motto is "PERFECTION PREVENTS COMPLETION".  We definitely want to be accurate and complete, but we also want to be complete as in done. Generally speaking, to make this happen, I believe we should start with the best balance of largest and easiest collections (of course those often conflict; we need to choose carefully), and then work from there. Leave the most complex and smallest collections for last, as the fewest individuals will be impacted by them.

Overall goals:

For a resource to be "done", as in "good enough to move on to the next one" (Jesse's words, Feb 14, 2020), we must do the following, to the greatest extent reasonably possible:

Access the current FOLIO instance here. 

Instructions to complete each of these steps are described below. 

1. Check to see if we have a current subscription or purchase, first. 

   1. If the agreement isn't active – if we don't have access to the resource, or the agreement has expired, or the resources has disappeared, then set the agreement aside, and we'll work on it at a later date, if at all. 

   2. Question/comment- Before we start, Could we find a way for us all to know who is working on something already, so we don't trip on each other? rmu
      
   3. Question/comment- could we agree upon a series of stop gap measures so we can proceed with our work with what we have and can find, rather than setting the work aside if one thing isn't there? For example- entering a Temp Licence- and clearly demarcating that it is NOT complete, then creating the agreement and attaching all the remaining pieces that ARE in FOLIO, so we have a better chance of finding things, and don't have to recreate the figuring out we have already done when we realize that we lack a piece. rmu

   
   

2. Locate or create an Organization

   1. An Organization is a group that supports our access to the resource in some manner. That may be as a content provider, as a subscription agent, as a vendor, or some other way. A "vendor", generally, is an Organization to whom we pay money. In some cases, we'll identify an individual Organization as having multiple roles, so one Organization may be both a "vendor", if we pay them directly for the service, and a "content provider" if they host the product and provide access to it for us.
      
      

   2. Look for duplicate vendors, and clean them up if necessary. For instructions on this, see here. 
      
      

   3. When you go to edit an Organization for the first time, you'll see that it doesn't have a Provider Code yet, and that these are required. We have agreed that, for the time being, we'll use the pre-existing Serials Solutions provider codes until we find a better, or more definite solution. So drag the PRV* code into the "Code" field, so that you can save the record. NOTE: AS OF MAY 2020, WE WILL USE THE EBSCO CODE; IF NO EBSCO CODE, THEN USE THE SERSOL CODE.  THE EBSCO CODE IS IN COLUMN C ("ProviderCode (vendor code)") IN THIS FILE: https://cornell.app.box.com/file/661387980413 .  LEAVE THE SERSOL CODE IN THE ALIAS FIELD FOR NOW.
      

      

   4. Creating a new Interface: Each Organization can have multiple Interfaces. Each Interface represents a method of accessing various information from the content provider, such as "Admin" (where you might add IP addresses, for instance); "End User"; "Reports" (for usage stats); "Orders"; "Invoices"; and "Other".  If you have a username and password that can be added for this resource, now is a great time to do that. 
      
      

   5. To create an Interface, select the Organization, click the "Edit" icon in the top right corner, and then open the Interface accordion section. Click 'Add Interface'. To create a new one, click "New" and then start adding information. FOLIO supports multiple Interfaces for each Organization. 

      If you're logged into a password manager, you might want to log out before accessing the Interface area, as it can grab and store passwords that are automatically pasted into the fields by the password manager.

       

      Be sure you click "Save & Close" before clicking "Add" anywhere, if it's present at the bottom of the screen when you open up any other windows. If you go to a section in which you can create a new entry, like "Contacts" or "Interface", you won't be able to click on "New" and create a new one, without either losing your changes to the Organization record or needing to go back and save those changes.

       

       

   6. You can add a URL in the "URI" field. This does not need to be proxied, since you'll nearly always be doing the work while at work. 

      
      

   7. The spreadsheet in Box.com, titled Resource_Administrative_Information_COO-2020-01-02.xlsx, has much of this information in it. To add username and password information, create a new interface by clicking on the "Add interface" button under "Interface". 

      
      

   8. Once you have created a new interface, you will need to attach it to the Organization. Select the Organization, click edit, add interface, check the box next to the appropriate interface, and then save. 

      
      

3. Locate the appropriate License  
   

   1. We assume that the license information taken from Intota is sufficiently accurate for our use here. If we find errors over time, we will correct them then. Licenses will generally have a same or similar name to the resource in question.  

   1. Question: Should we be attaching organizations to licenses at this step? - Perhaps only if the org is with whom we have the licensing agreement, as the options here are "Licensee", "Licensor", "Consortium", and "Consortium Administrator". I guess if we know that some portion of the license comes via NERL, WALDO, or another Consortium, we can record that here.

   2. Should we be adding start and end dates to licenses?

   3. Question: What if the package has not been attached to a specific license previously?  For instance, it may have been attached to NO license, or to just a generic license.  Do we need to attach the packages to a generic license, or what??

   2. Add a link to the "core documents". Core documents are the past or current active licenses, terms, and title lists, etc. We should not include negotiation drafts or proposals in this area – only those items that were signed (ideally counter-signed) and are or were active. Most of these are now available in one of several box.com folders. The final home for these is in one of the folders in the "AERLS License Storage" folder. Most of the files waiting to be sorted there are in the "Foreign Vendor Agreements" folder, but from there the documents could be in any of them. There are dozens and dozens of folders, and hundreds of files in a few of the folders. 
      
      
       
   3. You can try searching for the license in question by using the box.com search box, then choosing "Folder Location" and limiting the search to the "Foreign Vendor Agreements" folder, as noted below. You could also limit the Type to PDF, if that would help.
      
      
      
      
   4. If this doesn't work, then, as always, the best plan of action is to ask Liisa. 
      
      
   5. Once you find the appropriate license, copy the URL of the document (or the folder, if you prefer). You'll add that to the License later
      
      
      
   6. Finish additional steps here. 
      
      
      

4. Create a (reasonably) complete Agreement

1. We have not created default agreements, so you'll need to create one. Open the Agreements app, then click "New". Add the Name, Description, Status, etc., as you see fit. 

   1. Question/comment: do we want to define how the "Names" appear? Do they cover the vendor, the product, the platform, or something else? 
      

   2. If it's easy to do, add the bib ID in the "Description" field.  Liisa's note: I am also adding the PO# and other notes
      
      

2. Agreement periods are required for each Agreement. You might be able to find this on the license itself (if you cannot find a Start Date, enter 12-25-2019); it should be a reflection of what we currently are using. You can leave the End Date open if you're not certain of it. If the license or agreement states that it will automatically renew if we do not notify the vendor of cancellation, then add a "Cancellation deadline" to the entry. 

   1. We need a lot more about what an Agreement Period is and how we measure it and such; when do we add additional periods, etc.?  Liisa's note: I am adding a "period note" if we are required to sign a new license or amendment with new or renewed subscriptions.
      
      

3. Add a License to the Agreement by clicking on the eponymous button, then click "Link license". Add the license that was enhanced or created above, and then do the same for the Organization. Click "Save & close", and you've created the Agreement. 
   1. You will need to select the Organization's role. If the Organization plays multiple roles, add it multiple times. For example, if the Organization is both the Content Provider and the Vendor, add it once and select the role "Content Provider," then add it a second time and select "Vendor." 
      
      

5. Attach Resources or Databases from eHoldings to the Agreement

   1. Unlike the other processes, right now you must go to the eHoldings app, and attach an Agreement to an eHoldings file.  WHAT DO I DO IF MY DATABASE IS NOT IN THE EHOLDINGS APP AND NOT SHOWING UP IN EBSCO?  EXAMPLE: BERLINER PHILHARMONIKER DIGITAL CONCERT HALL.  sjl

   2. In addition, the eHoldings app searches differently; it assumes an AND between all terms, so you should use quotes to create phrases, when needed. 
      
      
      
   3. For a resource like this one, where there are many resources that are "not selected" (ie, we don't subscribe to), you can limit the "Selection status" to "Selected" and then locate the collections that we can access. Note that after you select the appropriate resource, the "Selected" option will disappear.
   4. In holdings, edit, scroll down to "Agreements" and click on "Add"  (rmu 3/5/2020)