mirror of
https://github.com/alanorth/cgspace-notes.git
synced 2025-01-27 05:49:12 +01:00
Update notes for 2017-10-05
This commit is contained in:
@ -54,3 +54,38 @@ http://library.cgiar.org/browse?value=Intellectual%20Assets%20Reports&type=subje
|
||||
- Help Sisay proof sixty-two IITA records on DSpace Test
|
||||
- Lots of inconsistencies and errors in subjects, dc.format.extent, regions, countries
|
||||
- Merge the Discovery search changes for ISI Journal ([#341](https://github.com/ilri/DSpace/pull/341))
|
||||
|
||||
## 2017-10-05
|
||||
|
||||
- Twice in the past twenty-four hours Linode has warned that CGSpace's outbound traffic rate was exceeding the notification threshold
|
||||
- I had a look at yesterday's OAI and REST logs in `/var/log/nginx` but didn't see anything unusual:
|
||||
|
||||
```
|
||||
# awk '{print $1}' /var/log/nginx/rest.log.1 | sort -n | uniq -c | sort -h | tail -n 10
|
||||
141 157.55.39.240
|
||||
145 40.77.167.85
|
||||
162 66.249.66.92
|
||||
181 66.249.66.95
|
||||
211 66.249.66.91
|
||||
312 66.249.66.94
|
||||
384 66.249.66.90
|
||||
1495 50.116.102.77
|
||||
3904 70.32.83.92
|
||||
9904 45.5.184.196
|
||||
# awk '{print $1}' /var/log/nginx/oai.log.1 | sort -n | uniq -c | sort -h | tail -n 10
|
||||
5 66.249.66.71
|
||||
6 66.249.66.67
|
||||
6 68.180.229.31
|
||||
8 41.84.227.85
|
||||
8 66.249.66.92
|
||||
17 66.249.66.65
|
||||
24 66.249.66.91
|
||||
38 66.249.66.95
|
||||
69 66.249.66.90
|
||||
148 66.249.66.94
|
||||
```
|
||||
|
||||
- Working on the nginx redirects for CGIAR Library
|
||||
- We should start using 301 redirects and also allow for `/sitemap` to work on the library.cgiar.org domain so the CGIAR System Organization people can update their Google Search Console and allow Google to find their content in a structured way
|
||||
- Remove eleven occurrences of `ACP` in IITA's `cg.coverage.region` using the Atmire batch edit module from Discovery
|
||||
- Need to investigate how we can verify the library.cgiar.org using the HTML or DNS methods
|
||||
|
Reference in New Issue
Block a user