Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
license_violation_procedures [2013/09/03 13:25]
cturner
license_violation_procedures [2023/08/15 13:58] (current)
172.24.102.74 [Databases that DO and DO NOT allow Text & Data Mining]
Line 1: Line 1:
-====== License Violation Procedures ====== +======License Violation Procedures======
-When provided with evidence or notification from publisher that someone is excessively or systematically downloading licensed content through the UMass Amherst network, collect as much information as possible and report it to [[mailto: abuse@oit.umass.edu|abuse@oit.umass.edu]] with the subject line **"​Library proxy abuse."​**+
  
-===== Collecting Information about Systematic Downloading: ===== +Violations are reported by vendors to us via eleres. The IP address and timestamp of violation are often noted. Sometimes a special string is sent by the vendor to the proxy server so you can find the offending time/​IP/​account in the proxy logs. The vendor will let you know what it is in their communication.  
-The violation may be occurring ​from off-campus ​or on. If the incident ​is local (on-campus), report this in your abuse email, as well as the timestamp ​of the incident and the IP address ​where it'​s ​coming ​from.+ 
 +Our proxy server address is 128.119.168.112.  
 + 
 + 
 +  - Identify the compromised account. 
 +  - Temporarily block the IP. 
 +  - Report account to [[mailto: abuse@umass.edu|abuse@umass.edu]] 
 +  - Respond to vendor letting them know you have blocked and reported the account. 
 +  - OIT will respond telling you they have reset the account'​s password. Once you have received this notification lift the block on the account. 
 +  - Move all emails into the Proxy Abuse folder in the eleres email account. ​     
 + 
 +==== Identify compromised account ​==== 
 + 
 +  - Review the proxy logfile.  
 +    - If investigating the abuse on the same day as it occurred, you can simply view the logfile in EZproxy'​s admin for the current day. 
 +      - Search via the IP/time or the code to find the account. 
 +    - If investigating the abuse on a different day you need to  
 +      - To access past UNIX side saved logs: 
 +        - Login and change to logs directory e.g. **cd logs** 
 +        - View available logs e.g. **ls** 
 +        - Saved logs have timestamp of date/time they were saved in filename. 
 +        - Use UNIX commands to search entries in log to find offending username, below is one way using the **more** command 
 +                 * **more filename** opens file 
 +                 * **/​20110605:​02** goes to that text string timestamp forward in the file 
 +                 * **h** will display a help file of commands 
 +                 * **q** will quit you out of the **more** function 
 +        - If using Putty, you can right click on header to copy screen to Clipboard 
 +        - Alternatively use psftp to ftp the entire logfile to your PC 
 + 
 +====Temporarily block IP==== 
 +      * Set up a local file somewhere in your C Drive for the software to use when you edit the text files. 
 +Using a FTP client (preferably WinSCP- Put in a SysHelp Ticket to have it installed on your machine) access the Proxy Server. 
 +      ​* ​The Username and Password can be obtained ​from Scott, Kat, or Jack. 
 +  * Once logged in, Identify the user.txt file in the main directory. 
 +      * There are a couple old files and backups that are not used anymore. Make sure you select the correct one. 
 +  * Drag the  file from the right pane into the left pane (the local folder ​on your C Drive). 
 +      * Allow it to overwrite or change ​the existing version if there is one. 
 +  * Double click on the file in the local folder to open the text editor. ​(For more advanced edits, use Notepad++ ​Put in a SysHelp Ticket to get it on your machine)
 +      * The file has a specific structure. The beginning has administrative informationetc. 
 +        * Different sections are commented out using a # 
 +      * Find the line that begins with #Add user to be blocked.... 
 +        * Add a new line in this format= Netid::​deny 
 +  * Save the local copy. 
 +      * Drag the local file back into the Proxy Server and allow it to overwrite the existing file. 
 +  * Go to the EZProxy Admin and login with the same credentials as the Server. 
 +      * Restart the Server **AFTER** you've updated the file. 
 + 
 + 
 +====Report account to OIT==== 
 + 
 +==EXAMPLE email reporting violations to abuse@umass.edu with the subject line "​Library proxy abuse."​ == 
 + 
 +We have identified a suspected abuse of a UMass NetID (below) going through the library proxy server. **Give some information about the IP addresses**. Can you please force a reset of their password? 
 + 
 +NetID: XXXXXXXX 
 + 
 +==EXAMPLE response ​email to vendor requesting the block be lifted so UMA can regain access to a resource== 
 + 
 +We have identified the offending user id and placed a deny request in our proxy. Our University IT is forcing a reset of their password. Please lift any blocks against our IP address. 
 + 
 +==NOTE: IT needs the following information to identify an on-campus user (when the traffic is coming from an on-campus IP address & not through the proxy server):​== 
 +You will need to ask the vendor for this information, as some vendors do not include all of it in the logs they send. 
 +  * The dates, times the incident ​took place, ​and the timezone of this date & time information. 
 +  * The campus ​IP address ​the mis-use was coming from. 
 +  * The vendor'​s ​IP address and network port of the service that is being mis-used. 
 + 
 +====Lift block on IP==== 
 +Using a FTP client (preferably WinSCP- Put in a SysHelp Ticket to have it installed on your machine) access the Proxy Server. 
 +      * The Username and Password can be obtained ​from Scott, Kat, or Jack. 
 +  * Once logged in, Identify the user.txt file in the main directory. 
 +      * There are a couple old files and backups that are not used anymore. Make sure you select the correct one. 
 +  * Drag the  file from the right pane into the left pane (the local folder on your C Drive). 
 +      * Allow it to overwrite or change the existing version if there is one. 
 +  * Double click on the file in the local folder to open the text editor. (For more advanced edits, use Notepad++ - Put in a SysHelp Ticket to get it on your machine). 
 +      * The file has a specific structure. The beginning has administrative information,​ etc. 
 +        * Different sections are commented out using a # 
 +      * Find the line that begins with #Add user to be blocked.... 
 +        * Remove the line that contains the netid in question. 
 +  * Save the Local copy. 
 +      * Drag the local file back into the Proxy Server and allow it to overwrite the existing file. 
 +  * Go to the EZProxy Admin and login with the same credentials as the Server. 
 +      * Restart the Server **AFTER** you've updated the file.
  
-If the abuse is coming from off-campus, the IP address will be that of the proxy server - 128.119.168.112:​ 
-  * Get the time of the incident from the vendor 
-  * Review the proxy logfile. Logfile is visible in web admin for current day only 
-  * To acces UNIX side saved logs: 
-    - Login and change to logs directory e.g. **cd logs** 
-    - View available logs e.g. **ls** 
-    - Saved logs have timestamp of date/time they were saved in filename. 
-    - Use UNIX commands to search entries in log to find offending username, below is one way using the **more** command 
-               * **more filename** opens file 
-               * **/​20110605:​02** goes to that text string timestamp forward in the file 
-               * **h** will display a help file of commands 
-               * **q** will quit you out of the **more** function 
-    - If using Putty, you can right click on header to copy screen to Clipboard 
-    - Alternatively use psftp to ftp the entire logfile to your PC 
-   * Collect UMass NetID of offender and timestamp from log. 
  
 ===== OIT's Workflow for Abuse Reports (7/20/11): ===== ===== OIT's Workflow for Abuse Reports (7/20/11): =====
Line 26: Line 91:
  
  
---- //[[cturner@library.umass.edu|Primary ​contact: Christine Turner]]//+===== Boilerplate for message to patrons about Text & Data Mining violations ===== 
 + 
 +Hi [name], 
 + 
 +The vendor has suspended our connection to this resource due to excessive use and suspected text & data mining activity. Our license terms with the vendor unfortunately do not allow for text and data mining, and the pattern of your recent use of the database suggests this kind of activity. Please do not perform text and data mining research with [database].  
 + 
 +We are working with the vendor and campus IT to resolve the issue. If you would like to explore ways to use the Libraries'​ resources to accomplish your research goals within the bounds of our contractual obligations with our resource vendors, please [[https://​www.library.umass.edu/​about-the-libraries/​liaisons/​|contact ​your department'​s liaison librarian]]. And please let me know if there is anything else I can assist you with. 
 + 
 +Thanks, [your name & title] 
 + 
 + 
 +===== Databases that DO and DO NOT allow Text & Data Mining ===== 
 +Databases that DO NOT allow TDM: 
 +  * Newsbank (Access World News) 
 +  * APS 
 +  * HeinOnline -- does not allow "​downloading or printing an entire issue or issues of a publication or journal within the database."​ 
 + 
 + 
 + 
 +Resources that DO allow TDM: (For sure, based on CORAL) 
 +  * Adam Matthew 
 +  * Accessible Archives 
 +  * Annual Reviews 
 +  * BioOne 
 +  * Brill Reference 
 +  * CABI 
 +  * China/Asia On Demand 
 +  * Duke eJournals 
 +  * History Makers 
 +  * Institute of Physical (eBooks & Journals) 
 +  * IP.com 
 +  * Microform Academic Publishers (single title resource) 
 +  * Oxford eJournals 
 +  * ProQuest 
 +  * Royal Society eJournals 
 +  * Sage eJournals 
 +  * SpringerNature eJournals
license_violation_procedures.1378214737.txt.gz · Last modified: 2019/01/07 17:20 (external edit)
[unknown link type]Back to top
www.chimeric.de Creative Commons License Valid CSS Driven by DokuWiki do yourself a favour and use a real browser - get firefox!! Recent changes RSS feed Valid XHTML 1.0