...

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:

1. Create a (reasonably) complete Agreement
2. Have a License attached to a (reasonably) complete Agreement
3. Have an Organization attached to that Agreement
4. Have a Database or Resource attached to that Agreement, when appropriate

Instructions to complete each of these steps are described below. Completing the steps above requires work in a different order than that shown above. 

1. Create

   a (reasonably) complete Agreement
   1. This is, actually, x
   Create

   or locate an Organization

   1. The Organization is sometimes called the "Vendor", but a Vendor is one to whom we pay money. 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. In some cases, we'll identify an individual Organization as having multiple roles, so one Org 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. 

1. Create or locate Organization - whoever is providing the content
   1. Click Organizations to open the Organizations app; check to see if the vendor you're interested in exists in there.
   2. If they don't, create them now.
      1. If we pay money to them, select the 'Vendor' checkbox
      2. But for now we're also creating a separate entry for the same vendor if they are also the content provider. 
   3. question: how do we delete a duplicate vendor? How do we choose which is the one to keep? Also, what about name changes in organizations? We currently have two entries for ASABE: "American Society of Agricultural and Biological Engineers" and "ASABE (American Society of Agricultural and Biological Engineers)". And it used to be ASAE - but we don't have that in FOLIO Orgs. May not need it at the moment, but there will be a need for name changes.
2. Create Agreement - all the other data parts hang from the agreement. "Agreement" is the overarching resource from which everything else hangs. Agreements are part of the terms of the license that govern more day-to-day info, but we need to confirm with the bigger FOLIO groups to define this accurately.
   1. Agreement steps
      1. figure out how many agreements you need for the provider (ex subscription vs perpetual access) to help craft the one you are 
      2. agreements will describe more than one resource
      3. we will have a line for each resource covered by an agreement (?? doublecheck this statement)
      4. open up a blank agreement and fill in fields:
         1. Name: provider name
         2. Description
         3. Status
         4. Reason for closure
         5. renewal priority
         6. one more field
         7. Agreement periods
         8. Agreement line - add an agreement line for each product purchased
         9. Internal contact: often this is blank; use this for LTS person who is the official maintainer; selector contact
         10. Agreement line
         11. License information
         12. external licenses - like a NERL license, signed by a different institution
         13. organizations
         14. supplementary information
         15. usage data
         16. related agreements
   2. NB: In Agreement Periods, you can put in fake dates, like "2020-11-31". That should be fixed.
   3. Content, licenses, contacts will be attached to the agreement
   4. plenty of spaces for notes in the Agreements part
   5. Under "Organizations", click "Add organization to agreement" and find the org you'd created. 
3. Create License
   1. Connect Organization to license
   2. Core documents - we can attach a license here, and see how it works
   3. Define the terms of the license - 
      1. "Definition of authorised user" - these should have a picklist? so we are using terms correctly, and limiting spelling errors?
      2. "Number of concurrent users allowed" - this requires an integer, so what do we choose here, to represent "unlimited"?
      3. "Walk-in access permitted?" and next question seem a repeat of "Definition of authorised users"

Editing Organizations

You can save or view passwords by going to the entry for the Organization, then to Interface. Multiple "Interfaces" appear; they could include a place where you get usage reports, or where an individual access the database, or where you access admin features. 

...

1. 1. 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, at least for the time being, 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. 

      Image Added

   2.  If you have a username and password that can be added for this resource, now is a great time to do that. 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".

      Note
      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.

      Note

      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.

   3. sdf

      
      

   4. some more steps, if needed

      
      

2. 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. Or should we be attaching organizations to licenses at this step? - only if the org is with whom we have the licesning 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. 
      

   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. 
      Image Added
      
       
   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.
      Image Added
      
      
      
   4. If this doesn't work, then, as always, the best plan of action is to ask Liisa. 
      
      
   5. complete this section, re connecting a core doc to a license
      
      
      

3. Create a (reasonably) complete Agreement

1. We're not currently creating 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.

2. Agreement periods are required for each Agreement. You might be able to find this on the license itself; 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 some identifier for when we don't know the Agreement start date. 

   2. 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.?

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. 
   
   

4. Attach Resources or Databases from eHoldings to the Agreement

   1. add this stuff here

E-HOLDINGS

Once an agreement has been created, it can be added to a resource through e-holdings.  

...