Accessibility changes for the Policies section

pages/policies/accessibility.md

@@ -9,5 +9,5 @@ In response to ADA regulations and university policy, CCR is completing the foll
 - [CCR Help Portal](https://ubuffalo.teamdynamix.com/TDClient/55/Portal/Home/): This is managed by UBIT and TeamDynamix and is compliant.  We will review to ensure links are using best practices for screen readers by the deadline.  
 - [Open OnDemand](https://ondemand.ccr.buffalo.edu): This software is developed by the Ohio Supercomputer Center who has committed to full compliance by mid-April.  CCR is working on testing an upgrade path from it's current version to the new version.  This service will be upgraded during the May 26 downtime.  
 - [CCR IDM Portal](https://idm.ccr.buffalo.edu): We are currently verifying accessibility for this site.  If you require assistance in using this portal, please [contact us](../help.md) and we will work with you to ensure all account management needs are met quickly.
-- [ColdFront](https://coldfront.ccr.buffalo.edu): We are currently verifying accessibility for this site.  If you require assistance in using this portal, please [contact us](../help.md) and we will work with you to ensure all project and allocation management needs are met quickly.
+- [ColdFront](https://coldfront.ccr.buffalo.edu): We are currently verifying accessibility for this site.  If you require assistance in using this portal, please [contact CCR](../help.md) and we will work with you to ensure all project and allocation management needs are met quickly.
 

pages/policies/accounts.md

@@ -4,12 +4,11 @@ This page includes information about account policies, including maintaining acc
 
 ## Accounts and Data Retention Policy
 
-CCR accounts are available to UB faculty, their collaborators and students either working with them or in a class that requires access to CCR.  Account requirements and application info can be found [here](../getting-access.md#requirements-for-accessing-ccrs-resources).
+CCR accounts are available to UB faculty, their collaborators and students either working with them or in a class that requires access to CCR.  Account requirements and application information can be found in the [CCR accounts documentation](../getting-access.md#requirements-for-accessing-ccrs-resources).
 
 ### Allocations to Resources
 
-All access to CCR resources (clusters, servers, research cloud, project storage, software licenses)  is granted and revoked via allocations.  Allocations are managed by PIs in ColdFront
-(https://coldfront.ccr.buffalo.edu).  Users should login to ColdFront to see what allocations they have access to and when they expire.  Faculty should renew allocations before expiration.  If an allocation expires, any user on that allocation will be no longer be able to access that resource.  Expired allocations can't be renewed.  A new allocation request must be submitted to gain access to the resource again.  More details can be found in the ColdFront documentation.
+All access to CCR resources (clusters, servers, research cloud, project storage, software licenses)  is granted and revoked via allocations.  Allocations are managed by Primary Investigators (PIs) in [ColdFront](https://coldfront.ccr.buffalo.edu).  Users should login to [ColdFront](https://coldfront.ccr.buffalo.edu) to see what allocations they have access to and when they expire.  Faculty should renew allocations before expiration.  If an allocation expires, any user on that allocation will be no longer be able to access that resource.  Expired allocations can't be renewed.  A new allocation request must be submitted to gain access to the resource again.  More details can be found in the ColdFront documentation.
 
 
 ### Yearly Project Review
@@ -35,7 +34,7 @@ Data – All data owned by your account on our systems will be deleted within 30
 
 **Class Accounts**
 
-Account – Accounts provided for class work are valid for the semester that the class is offered in and automatically terminated at the end of the semester.  If a student requires additional time to complete coursework, the professor teaching the course must [contact CCR help](../help.md) to request an extension on the account.  Student accounts that are also sponsored by a faculty member remain active after the course ends, subject to the policies in the “faculty sponsored accounts” section below.
+Account – Accounts provided for class work are valid for the semester that the class is offered in and automatically terminated at the end of the semester.  If a student requires additional time to complete coursework, the professor teaching the course must contact [CCR help](../help.md) to request an extension on the account.  Student accounts that are also sponsored by a faculty member remain active after the course ends, subject to the policies in the “faculty sponsored accounts” section below.
 
 Data – Data in a student’s home directory created for a class account is deleted 30 days after account termination.  This includes data on CCR’s network attached storage systems (user & course project directories), local compute node and global scratch directories, and cloud instances and storage (if applicable).
 
@@ -150,7 +149,7 @@ iquota -p /projects/academic/[YourGroupName]
 **Requesting a data restore**  
 Every effort will be made to retrieve requested data files from the backups, however we do not guarantee that the data can be recovered.  As stated above, we strongly recommend you keep copies of your important data on your personal machine, external disk, or cloud service.  
 
-To request a file or directory be restored from backup tape, please [contact CCR help](../help.md) providing the following information:  
+To request a file or directory be restored from backup tape, please contact [CCR help](../help.md) providing the following information:  
 
 - Full file location to be restored,  
 - Name of file(s)/directory(ies) to be restored  
@@ -161,7 +160,7 @@ To request a file or directory be restored from backup tape, please [contact CCR
 
 ## Password Policies
 
-CCR maintains the same password policy as the University at Buffalo.  The [full policy can be found here](https://www.buffalo.edu/administrative-services/policy1/ub-policy-lib/ubit-password.html).  We want to specifically point out these parts:  
+CCR maintains the same password policy as the University at Buffalo.  This full policy is documented on the [UB password policy page](https://www.buffalo.edu/administrative-services/policy1/ub-policy-lib/ubit-password.html).  We want to specifically point out these parts:  
 
 **Individual Accountability**  
 All users of university systems are individually assigned a user-id (e.g., UBITName) and password for the purpose of accessing UB online systems.  In accordance with UB “acceptable use policies,” users are individually accountable for activities performed with their user-ids and passwords.  Passwords may not be shared with anyone, including with administrative assistants or secretaries.  UB passwords are considered to be regulated, private data.  
@@ -192,10 +191,10 @@ User and system passwords shall be constructed with strength and complexity that
 
 ## Two Factor Authentication Reset Policy  
 
-If a CCR user has lost access to the app they used to generate the time-based one-time passwords they will not be able to login to their CCR account or modify the two-factor authentication settings.  Users must contact CCR help to request the removal of this security feature.  In order to verify the account owner's identity, the user will be directed to present photo identification to a CCR staff member.  Details will be provided once you initiate [contact with CCR help](../help.md).  
+If a CCR user has lost access to the app they used to generate the time-based one-time passwords they will not be able to login to their CCR account or modify the two-factor authentication settings.  Users must contact CCR help to request the removal of this security feature.  In order to verify the account owner's identity, the user will be directed to present photo identification to a CCR staff member.  Details will be provided once you initiate contact with [CCR help](../help.md).  
 
 Once we receive this information, we will remove the two-factor authentication setting from your account and you'll be able to login with your password.
 
 ## Preferred Name  
 
-If you wish to change the name on your CCR account, please contact [CCR Help](../help.md).  No reason for the change is necessary.  The username for the account will remain the same.  CCR does not store pronouns in our account systems at this time.  TeamDynamix currently doesn't store this information either.If you include your pronouns in your ticket details, we will gladly use them when replying to your help tickets.  For additional information on the University at Buffalo's preferred name policy, please see [here](https://www.buffalo.edu/administrative-services/policy1/ub-policy-lib/student-preferred-name.html)  
+If you wish to change the name on your CCR account, please contact [CCR Help](../help.md).  No reason for the change is necessary.  The username for the account will remain the same.  CCR does not store pronouns in our account systems at this time.  TeamDynamix currently doesn't store this information either.If you include your pronouns in your ticket details, we will gladly use them when replying to your help tickets.  For additional information on the University at Buffalo's preferred name policy, please see [UB's preferred name policy documentation](https://www.buffalo.edu/administrative-services/policy1/ub-policy-lib/student-preferred-name.html)  

pages/policies/email.md

@@ -12,9 +12,10 @@ We commit to notify all active CCR users through email before we make significan
 We occasionally send a newsletter with information about CCR.  This comes from Mailchimp.  We automatically add all active CCR users to this list but you are welcome to unsubscribe from that if you no longer want to receive these newsletters.  We will not re-subscribe you to this list (or at least not purposely).  
 
 ### ColdFront allocation notifications  
-The ColdFront resource and allocations management portal will send notifications to users when allocations are coming up for renewal.  PIs and managers on the ColdFront project may not turn off notifications; however, users can disable these.  Login to ColdFront - [https://coldfront.ccr.buffalo.edu](https://coldfront.ccr.buffalo.edu) - click on the project name and then click to uncheck the box next to your name to turn off notifications.   
+The ColdFront resource and allocations management portal will send notifications to users when allocations are coming up for renewal.  PIs and managers on the ColdFront project may not turn off notifications; however, users can disable these.  Login to [ColdFront](https://coldfront.ccr.buffalo.edu) - click on the project name and then click to uncheck the box next to your name to turn off notifications.   
 
 ### Additional places you can get CCR information
-[Downtime schedule and planned tasks](https://ubccr.freshdesk.com/support/discussions/forums/5000296650)  
-[Emergency or important alerts are posted here](https://ubccr.freshdesk.com/support/discussions/forums/5000120071) and on [Twitter](https://twitter.com/UBCCR)  
-[Event notices are posted here](https://ubccr.freshdesk.com/support/discussions/forums/13000000490)  
+[Downtime schedule and planned tasks](../changelogs/downtime-schedule.md)  
+[Emergency or important alerts](https://ubuffalo.teamdynamix.com/TDClient/55/Portal/Home/) and on [Twitter](https://twitter.com/UBCCR)  
+[Latest news](https://www.buffalo.edu/ccr/about-us/news-events/latest_news.html)  
+[Event notices](https://www.buffalo.edu/ccr/about-us/news-events/upcoming_events.html)  

pages/policies/misuse.md

@@ -33,7 +33,7 @@ CCR offers project storage space for groups to securely share data and can work
 The clusters' batch queuing system is designed to give everyone a fair shot at the highest level of throughput for their jobs.  Attempting to circumvent the queue or fairshare system (i.e. cut to the front of the line) is strictly prohibited and will result in your account being deactivated and potential disciplinary action by the University at Buffalo IT security office. See below for more information on this policy.  
 
 **Scratch Scrubber Policy**  
-CCR provides free, high throughput scratch storage space for use when running your jobs.  However, this is TEMPORARY storage space intended for transient storage while jobs are running.  Users are expected to move their data from `/vscratch` to their home or project directory when their job is complete.  Any data over 60 days old is deleted automatically nightly.  Any efforts to modify file dates to purposely subvert this policy are prohibited.  We have sophisticated scripts that monitor for attempts to subvert the system.  Users violating this policy risk ALL of their data in `/vscratch` being deleted without notice and account deactivation. [See below](##) for more information on this policy.  
+CCR provides free, high throughput scratch storage space for use when running your jobs.  However, this is TEMPORARY storage space intended for transient storage while jobs are running.  Users are expected to move their data from `/vscratch` to their home or project directory when their job is complete.  Any data over 60 days old is deleted automatically nightly.  Any efforts to modify file dates to purposely subvert this policy are prohibited.  We have sophisticated scripts that monitor for attempts to subvert the system.  Users violating this policy risk ALL of their data in `/vscratch` being deleted without notice and account deactivation. [Refer to the scratch policy](#touch) for more information on file date or access time manipulation.   
 
 
 !!! Warning
@@ -62,7 +62,7 @@ What you need to know about global scratch space:
 - Groups have a 10 TB default quota for their global scratch directory  
 - Groups are also subject to a quota of 200 million files  
 - We set these group quotas for the total number of files in accordance with our system size and projected usage.  Users generating more than a million files per job could affect the performance of the system for everyone.  If you feel your research requires this, we’d like to engage with you to determine if there is an alternate approach  
-
+<a id="touch"></a>
 **Automatic Deletion of Files in Global Scratch**  
 - The allowed lifespan of files in global scratch is 60 days from the last file access date.  This is based on the file’s last access timestamp ("atime") on the file servers.  
 - CCR runs an automated cleanup process daily on the filesystem to delete files whose “atime” has reached the maximum lifespan.  
@@ -71,7 +71,7 @@ What you need to know about global scratch space:
 ==**Your user account privileges will be revoked if you attempt to get around this rule (i.e. scripting the touching of files to keep them current).**==  
 
 !!! Note "Be a good citizen"
-    Global scratch is a shared resource and policies are set to benefit the entire CCR user community.  If you have any questions about the use of these scratch spaces, please [contact CCR Help](../help.md).
+    Global scratch is a shared resource and policies are set to benefit the entire CCR user community.  If you have any questions about the use of these scratch spaces, please contact [CCR Help](../help.md).
 
 ## Batch Scheduler Policy
 
@@ -112,7 +112,7 @@ A small number of nodes are set aside in the debug partition of the ub-hpc clust
 There are scavenger partitions on all CCR clusters.  These partitions provide a way for academic users to access idle nodes.  Jobs submitted to the scavenger partitions will run when there are no other pending or running jobs to run on these idle nodes.  Once a user with access to that partition submits a job requesting resources, jobs in the scavenger partition are stopped and re-queued.  This means if you're running a job in the scavenger partition on an industry node and an industry user submits a job requiring the resources you're consuming, your job will be stopped.  Use of the scavenger partition requires advanced setup and knowledge and is a privilege.  If your jobs are determined to cause problems on any of the private cluster nodes and we receive complaints from the owners of those nodes, your access to the scavenger partitions will be removed.
 
 **Fairshare Limits**  
-To keep any one user or group from monopolizing the system when others need the same resources, the scheduler imposes what are known as fairshare limits. If a user or group uses large amounts of computing resources over a period of a month, any new jobs they submit during that period will have reduced priority.  More details on fairshare calculations can be [found here](../hpc/jobs.md)  
+To keep any one user or group from monopolizing the system when others need the same resources, the scheduler imposes what are known as fairshare limits. If a user or group uses large amounts of computing resources over a period of a month, any new jobs they submit during that period will have reduced priority.  More details on fairshare calculations can be found in [CCR's job documentation](../hpc/jobs.md)  
 
 **Priority**  
-The priority of a job is influenced by many factors, including the processor count requested, the length of time the job has been waiting, how much other computing has been done by the user and their group over the last month (fairshare), and if the group has access to a QOS that provides a priority boost. However, having the highest priority does not necessarily mean that a job will run immediately, as there must also be enough processors and memory available to run it.  See our documentation on the [job scheduler](../hpc/jobs.md) for more info on how priority is calculated and how to check the priority of your pending job(s)  
+The priority of a job is influenced by many factors, including the processor count requested, the length of time the job has been waiting, how much other computing has been done by the user and their group over the last month (fairshare), and if the group has access to a QOS that provides a priority boost. However, having the highest priority does not necessarily mean that a job will run immediately, as there must also be enough processors and memory available to run it.  See our documentation on the [Slurm job scheduler](../hpc/jobs.md) for more information on how priority is calculated and how to check the priority of your pending job(s)