diff --git a/README.md b/README.md
index f267f0a..a6b9130 100644
--- a/README.md
+++ b/README.md
@@ -32,7 +32,7 @@ This is a simple dropdown menu that allows the user to toggle between XML and JS
 ### GitHub Repo
 This amber button opens up the GitHub repository page for the project (which you are presumably at currently) for easy access to the documentation. This will open the webpage in a new tab of your default browser.
 ## Origin Tab
-The fields present in this tab will not be enabled upton the Enable? checkbox is ticked, indicating that you would like to use this tab. Enabling the tab will allow information to be included on the origin/nature of the digital assets, that is, whether or not they are born digital or digitized resources.
+The fields present in this tab will not be enabled upton the Enable? checkbox is ticked, indicating that you would like to use this tab. Enabling the tab will allow information to be included on the origin/nature of the digital assets, that is, whether or not they are born digital or digitized resources. This assigns the PREMIS event type of *creation* which is drawn from the [Event Type](https://id.loc.gov/vocabulary/preservation/eventType.html) controlled vocabulary.
 ### Born Digital or Digitized
 This dropdown menu allows for four options taken from the Metadata Object Description Schema (MODS), specifically the [<digitalOrigin> subelement](https://www.loc.gov/standards/mods/userguide/physicaldescription.html#digitalorigin) of the <physicalDescription> element, and uses these terms as a controlled vocabulary. The definitions of the terms are:
 + born digital – A resource was created in digital form and is intended to remain in digital form.
@@ -42,15 +42,35 @@ This dropdown menu allows for four options taken from the Metadata Object Descri
 ### Date Created
 The Origin tab is simply a specficially targetted use case of the PREMIS *event* schema (more generalized use of PREMIS events available in the **Actions** tab), in this case the *creation* event. While clicking on the "Date Picker" button will pop up a small calendar utility letting you click on a specific day, this can be whatever you want with whatever desired level of granularity, though ISO 8601 is always recommended. If you don't have a specific day (YYYY-MM-DD) then using YYYY-MM or YYYY is advised. Feel free to use ranges as well (though consistency is always your friend).
 ### Created By
-This creates the PREMIS *agent* associated with the *creation* event and gives them the role of *implementor* as pulled from the [**Event Related Agent Role**](https://id.loc.gov/vocabulary/preservation/eventRelatedAgentRole.html) controlled vocabulary. This need not be an individual person, but the more detail entered here the better. For instance locally we include the name of the person, their title, their department, and the overall organization (e.g. John Dewees, Digital Asset Mangement Lead, Digital Initiatves department, River Campus Libraries, University of Rochester). This can also be an outsourced digitization vendor. I strongly recommend you develop a local controlled vocabulary of agent names to utilize for this field, and other similar ones throughout the utility.
+This creates the PREMIS *agent* associated with the *creation* event and gives them the role of *implementer* as pulled from the [**Event Related Agent Role**](https://id.loc.gov/vocabulary/preservation/eventRelatedAgentRole.html) controlled vocabulary. This need not be an individual person, but the more detail entered here the better. For instance locally we include the name of the person, their title, their department, and the overall organization (e.g. John Dewees, Digital Asset Mangement Lead, Digital Initiatves department, River Campus Libraries, University of Rochester). This can also be an outsourced digitization vendor. I strongly recommend you develop a local controlled vocabulary of agent names to utilize for this field, and other similar ones throughout the utility.
 ## Rights Tab
 The fields present in this tab will not be enabled upton the Enable? checkbox is ticked, indicating that you would like to use this tab. Enabling the tab will allow information related to the rights status (meaning the copyright) of the digital asset/intellectual property. This is one of the areas of the utility that is likely to grow over time as more rights-related situations make themselves apparent based on user feedback.
 ### Rights Basis
 There are four situations that can be encoded in PREMIS metadata records using this tool. The *rights basis* is directly drawn from the PREMIS data dictionary, specificically semantic unit **4.1.2 rightsBasis** which utilizes [**Rights Basis**](https://id.loc.gov/vocabulary/preservation/rightsBasis.html) controlled vocabulary. The bulleted list below contains the values you will see in the dropdown menu and parenthetically what controlled vocabulary term they map to.
-+ Under Copyright (copyright)
-+ Public Domain (copyright)
-+ Fair Use (statute)
-+ License Agreement (license)
++ Under Copyright (copyright) - Use of this option indicates that the intellecutal property represented in the digital assets are currently protected by copyright in the United States and the metadata record will include a link to the [In Copyright RightsStatement](http://rightsstatements.org/vocab/InC/1.0/).
++ Public Domain (copyright) - Use of this option indicates that the intellectual property represented in the digital assets has either fallen into the public domain in the United States after copyright protection has lapsed, or been dedicated to the public domain via a [CC0 Public Domain Dedication](https://creativecommons.org/publicdomain/zero/1.0/). A link to the [No Copyright - United States RightsStatement](http://rightsstatements.org/vocab/NoC-US/1.0) is included in the metadata record.
++ Fair Use (statute) - Use of this option indicates that the intellectual property represented in the digital assets are currently protected by copyright, but they are in some way being shared or copied in a fashion not otherwise enshrined as an exception in the Copyright Act and as such a fair use justification is being utilized. The metadata record will include a link to the [In Copyright RightsStatement](http://rightsstatements.org/vocab/InC/1.0/)
++ License Agreement (license) - Use of this option indicates that the intellectual property is still protected by copyright, but the custodial organization has a licensed or contractual right to preserve, share, or otherwise work with the digital assets. The metadata record will include a link to the [In Copyright RightsStatement](http://rightsstatements.org/vocab/InC/1.0/)
+### Date Determined
+This field allows the inclusion of a specific or approximate date on which the copyright status of the intellectual content was determined. While clicking on the "Date Picker" button will pop up a small calendar utility letting you click on a specific day, this can be whatever you want with whatever desired level of granularity, though ISO 8601 is always recommended. If you don't have a specific day (YYYY-MM-DD) then using YYYY-MM or YYYY is advised. Feel free to use ranges as well (though consistency is always your friend). This field is not used for the *License Agreement* Rights Basis.
+### Terms
+This field is only used with the *License Agreement* Rights Basis. A summary of the associated license or contract should be included here to provide a broad understanding of why the resources are in the organization's custody and what they are permitted to do with them.
+### Notes
+This field can be used with all the Rights Bases, and should at a minimum link out to more robust documentation that can discuss the copyright status of a work. This might include a reference to the research completed to determine that a work is still under copyright or in the public domain, to the license agreement, and to the fair use calcuation. This is a bit of a kludge in the case of linking out to the license agreement. Technically speaking the metadata field being used to link out to the *In Copyright* RightsStatement is being repurposed and should link out to the license documentation and its associated identifier. Instead we recommend keeping this information in the Notes field. Real metadata librarians out there, feel free to @ me to let me know how I can do this better.
+### Determined By
+This creates the PREMIS *agent* associated with the person specifically doing this copyright evaluation and work. If you have a copyright librarian at your org, *their* name should be used here if it is different than the person mashing the **Generate PREMIS Records** in this utility. It gives them the role of *implementer* as pulled from the [**Event Related Agent Role**](https://id.loc.gov/vocabulary/preservation/eventRelatedAgentRole.html) controlled vocabulary. This need not be an individual person, but the more detail entered here the better. For instance locally we include the name of the person, their title, their department, and the overall organization (e.g. John Dewees, Digital Asset Mangement Lead, Digital Initiatves department, River Campus Libraries, University of Rochester). This could also link out to a department for instance. I strongly recommend you develop a local controlled vocabulary of agent names to utilize for this field, and other similar ones throughout the utility.
+## Actions Tab
+The fields present in this tab will not be enabled upton the Enable? checkbox is ticked, indicating that you would like to use this tab. Enabling the tab will allow information related to any preservation actions that are happening outside your preservation software/platform/environment and thus will not be captured in automated histories or logs.
+### Event Type
+This is a very long list of possible preservation activities starting with *accession* and ending with *virus check* that is drawn from the [Event Type](https://id.loc.gov/vocabulary/preservation/eventType.html) controlled vocabulary. The only option omitted is *creation* as that has its own dedicated tab in the PREMIS utility.
+### Notes
+This is where as much information about the preservation activity as the user wants can be entered. This might include virtualization environments, software/hardware specifications, reasoning for why the action didn't take place in the relevant preservation system, and any other narrative information that will help preservationists in the future.
+### Date Executed
+This field allows the inclusion of a specific or approximate date on which the preservation action was taken. While clicking on the "Date Picker" button will pop up a small calendar utility letting you click on a specific day, this can be whatever you want with whatever desired level of granularity, though ISO 8601 is always recommended. If you don't have a specific day (YYYY-MM-DD) then using YYYY-MM or YYYY is advised. Feel free to use ranges as well (though consistency is always your friend).
+### Executed By
+This creates the PREMIS *agent* associated with the person specifically doing the preservation action. This need not be an individual person, but the more detail entered here the better. For instance locally we include the name of the person, their title, their department, and the overall organization (e.g. John Dewees, Digital Asset Mangement Lead, Digital Initiatves department, River Campus Libraries, University of Rochester). This could also link out to a department for instance. I strongly recommend you develop a local controlled vocabulary of agent names to utilize for this field, and other similar ones throughout the utility.
+### Role
+This allows greater specification in who or what executed the preservation action. The options are drawn from the [**Event Related Agent Role**](https://id.loc.gov/vocabulary/preservation/eventRelatedAgentRole.html) controlled vocabulary. Whereas all the other agents in the previous tabs are assumed to be *implementers* this allows for the options of an *authorizer*, *executing program*, or *validator* as well. When in doubt, go with *implementer*.
 # Known Issues
 When hitting the Close Window/"X" button in the top right of the screen, the following error is displayed:
 ```