mirror of
https://github.com/alanorth/cgspace-notes.git
synced 2024-11-25 16:08:19 +01:00
content/post: Fix image links
This commit is contained in:
parent
08f725b92d
commit
f50e2455a4
@ -72,7 +72,7 @@ $ curl -o /dev/null -s -w %{time_total}\\n https://cgspace.cgiar.org/rest/handle
|
||||
- Last week it was an average of 8 seconds... now this is 1/4 of that
|
||||
- CCAFS noticed that one of their items displays only the Atmire statlets: https://cgspace.cgiar.org/handle/10568/42445
|
||||
|
||||
![CCAFS item](../images/2015/12/ccafs-item-no-metadata.png)
|
||||
![CCAFS item](2015/12/ccafs-item-no-metadata.png)
|
||||
|
||||
- The authorizations for the item are all public READ, and I don't see any errors in dspace.log when browsing that item
|
||||
- I filed a ticket on Atmire's issue tracker
|
||||
@ -121,10 +121,10 @@ postgres@linode01:~$ psql -c 'SELECT * from pg_stat_activity;' | grep cgspace |
|
||||
- I have reverted all the pgtune tweaks from the other day, as they didn't fix the stability issues, so I'd rather not have them introducing more variables into the equation
|
||||
- The PostgreSQL stats from Munin all point to something database-related with the DSpace 5 upgrade around mid–late November
|
||||
|
||||
![PostgreSQL bgwriter (year)](../images/2015/12/postgres_bgwriter-year.png)
|
||||
![PostgreSQL cache (year)](../images/2015/12/postgres_cache_cgspace-year.png)
|
||||
![PostgreSQL locks (year)](../images/2015/12/postgres_locks_cgspace-year.png)
|
||||
![PostgreSQL scans (year)](../images/2015/12/postgres_scans_cgspace-year.png)
|
||||
![PostgreSQL bgwriter (year)](2015/12/postgres_bgwriter-year.png)
|
||||
![PostgreSQL cache (year)](2015/12/postgres_cache_cgspace-year.png)
|
||||
![PostgreSQL locks (year)](2015/12/postgres_locks_cgspace-year.png)
|
||||
![PostgreSQL scans (year)](2015/12/postgres_scans_cgspace-year.png)
|
||||
|
||||
## 2015-12-07
|
||||
|
||||
|
@ -64,8 +64,8 @@ image = "../images/bg.jpg"
|
||||
- Add five missing center-specific subjects to XMLUI item view ([#174](https://github.com/ilri/DSpace/issues/174))
|
||||
- This [CCAFS item](https://cgspace.cgiar.org/handle/10568/67062) Before:
|
||||
|
||||
![XMLUI subjects before](../images/2016/01/xmlui-subjects-before.png)
|
||||
![XMLUI subjects before](2016/01/xmlui-subjects-before.png)
|
||||
|
||||
- After:
|
||||
|
||||
![XMLUI subjects after](../images/2016/01/xmlui-subjects-after.png)
|
||||
![XMLUI subjects after](2016/01/xmlui-subjects-after.png)
|
||||
|
@ -12,7 +12,7 @@ image = "../images/bg.jpg"
|
||||
- Lots of issues with spaces, newlines, etc causing the import to fail
|
||||
- I noticed we have a very *interesting* list of countries on CGSpace:
|
||||
|
||||
![CGSpace country list](../images/2016/02/cgspace-countries.png)
|
||||
![CGSpace country list](2016/02/cgspace-countries.png)
|
||||
|
||||
- Not only are there 49,000 countries, we have some blanks (25)...
|
||||
- Also, lots of things like "COTE D`LVOIRE" and "COTE D IVOIRE"
|
||||
@ -107,8 +107,8 @@ $ ~/dspace/bin/dspace index-discovery -b
|
||||
- Finish cleaning up and importing ~400 DAGRIS items into CGSpace
|
||||
- Whip up some quick CSS to make the button in the submission workflow use the XMLUI theme's brand colors ([#154](https://github.com/ilri/DSpace/issues/154))
|
||||
|
||||
![ILRI submission buttons](../images/2016/02/submit-button-ilri.png)
|
||||
![Drylands submission buttons](../images/2016/02/submit-button-drylands.png)
|
||||
![ILRI submission buttons](2016/02/submit-button-ilri.png)
|
||||
![Drylands submission buttons](2016/02/submit-button-drylands.png)
|
||||
|
||||
## 2016-02-09
|
||||
|
||||
|
@ -38,7 +38,7 @@ Exception in thread "Lucene Merge Thread #19" org.apache.lucene.index.MergePolic
|
||||
- Start cleaning up the configuration for Atmire's CUA module ([#184](https://github.com/ilri/DSpace/issues/185))
|
||||
- It is very messed up because some labels are incorrect, fields are missing, etc
|
||||
|
||||
![Mixed up label in Atmire CUA](../images/2016/03/cua-label-mixup.png)
|
||||
![Mixed up label in Atmire CUA](2016/03/cua-label-mixup.png)
|
||||
|
||||
- Update documentation for Atmire modules
|
||||
|
||||
@ -57,7 +57,7 @@ Exception in thread "Lucene Merge Thread #19" org.apache.lucene.index.MergePolic
|
||||
- Make titles in Discovery and Browse by more consistent (singular, sentence case, etc) ([#186](https://github.com/ilri/DSpace/issues/186))
|
||||
- Also four or so center-specific subject strings were missing for Discovery
|
||||
|
||||
![Missing XMLUI string](../images/2016/03/missing-xmlui-string.png)
|
||||
![Missing XMLUI string](2016/03/missing-xmlui-string.png)
|
||||
|
||||
## 2016-03-15
|
||||
|
||||
@ -105,11 +105,11 @@ Exception in thread "Lucene Merge Thread #19" org.apache.lucene.index.MergePolic
|
||||
- Discuss thumbnails with Francesca from Bioversity
|
||||
- Some of their items end up with thumbnails that have a big white border around them:
|
||||
|
||||
![Excessive whitespace in thumbnail](../images/2016/03/bioversity-thumbnail-bad.jpg)
|
||||
![Excessive whitespace in thumbnail](2016/03/bioversity-thumbnail-bad.jpg)
|
||||
|
||||
- Turns out we can add `-trim` to the GraphicsMagick options to trim the whitespace
|
||||
|
||||
![Trimmed thumbnail](../images/2016/03/bioversity-thumbnail-good.jpg)
|
||||
![Trimmed thumbnail](2016/03/bioversity-thumbnail-good.jpg)
|
||||
|
||||
- Command used:
|
||||
|
||||
@ -135,14 +135,14 @@ $ gm convert -trim -quality 82 -thumbnail x300 -flatten Descriptor\ for\ Butia_E
|
||||
- Google says the first time it saw this particular error was September 29, 2015... so maybe it accidentally saw it somehow...
|
||||
- On a related note, we have 51,000 items indexed from the sitemap, but 500,000 items in the Google index, so we DEFINITELY have a problem with duplicate content
|
||||
|
||||
![CGSpace pages in Google index](../images/2016/03/google-index.png)
|
||||
![CGSpace pages in Google index](2016/03/google-index.png)
|
||||
|
||||
- Turns out this is a problem with DSpace's `robots.txt`, and there's a Jira ticket since December, 2015: https://jira.duraspace.org/browse/DS-2962
|
||||
- I am not sure if I want to apply it yet
|
||||
- For now I've just set a bunch of these dynamic pages to not appear in search results by using the URL Parameters tool in Webmaster Tools
|
||||
|
||||
![URL parameters cause millions of dynamic pages](../images/2016/03/url-parameters.png)
|
||||
![Setting pages with the filter_0 param not to show in search results](../images/2016/03/url-parameters2.png)
|
||||
![URL parameters cause millions of dynamic pages](2016/03/url-parameters.png)
|
||||
![Setting pages with the filter_0 param not to show in search results](2016/03/url-parameters2.png)
|
||||
|
||||
- Move AVCD collection to new community and update `move_collection.sh` script: https://gist.github.com/alanorth/392c4660e8b022d99dfa
|
||||
- It seems Feedburner can do HTTPS now, so we might be able to update our feeds and simplify the nginx configs
|
||||
|
@ -32,7 +32,7 @@ GET /rest/handle/10568/NaN?expand=parentCommunityList,metadata HTTP/1.1
|
||||
- Update nginx to 1.10.x branch on CGSpace
|
||||
- Fix a reference to `dc.type.output` in Discovery that I had missed when we migrated to `dc.type` last month ([#223](https://github.com/ilri/DSpace/pull/223))
|
||||
|
||||
![Item type in Discovery results](../images/2016/05/discovery-types.png)
|
||||
![Item type in Discovery results](2016/05/discovery-types.png)
|
||||
|
||||
## 2016-05-06
|
||||
|
||||
|
@ -269,7 +269,7 @@ $ ./delete-metadata-values.py -f dc.contributor.corporate -i Corporate-Authors-D
|
||||
- Re-deploy CGSpace and DSpace Test with latest June changes
|
||||
- Now the sharing and Altmetric bits are more prominent:
|
||||
|
||||
![DSpace 5.1 XMLUI With Altmetric Badge](../images/2016/06/xmlui-altmetric-sharing.png)
|
||||
![DSpace 5.1 XMLUI With Altmetric Badge](2016/06/xmlui-altmetric-sharing.png)
|
||||
|
||||
- Run all system updates on the servers and reboot
|
||||
- Start working on config changes for phase three of the metadata migrations
|
||||
|
@ -190,7 +190,7 @@ index.authority.ignore-variants=true
|
||||
- No changes to Discovery after reindexing... hmm.
|
||||
- Integrate and massively clean up About page ([#256](https://github.com/ilri/DSpace/pull/256))
|
||||
|
||||
![About page](../images/2016/07/cgspace-about-page.png)
|
||||
![About page](2016/07/cgspace-about-page.png)
|
||||
|
||||
- The DSpace source code mentions the configuration key `discovery.index.authority.ignore-prefered.*` (with prefix of discovery, despite the docs saying otherwise), so I'm trying the following on DSpace Test:
|
||||
|
||||
|
@ -103,7 +103,7 @@ $ ln -sv ~/dspace/webapps/solr /opt/brew/Cellar/tomcat/8.5.4/libexec/webapps/sol
|
||||
|
||||
- Finally got DSpace (5.5) running on Ubuntu 16.04, Tomcat 7, Java 8, PostgreSQL 9.5 via the updated Ansible stuff
|
||||
|
||||
![DSpace 5.5 on Ubuntu 16.04, Tomcat 7, Java 8, PostgreSQL 9.5](../images/2016/08/dspace55-ubuntu16.04.png)
|
||||
![DSpace 5.5 on Ubuntu 16.04, Tomcat 7, Java 8, PostgreSQL 9.5](2016/08/dspace55-ubuntu16.04.png)
|
||||
|
||||
## 2016-08-14
|
||||
|
||||
@ -113,7 +113,7 @@ $ ln -sv ~/dspace/webapps/solr /opt/brew/Cellar/tomcat/8.5.4/libexec/webapps/sol
|
||||
|
||||
- Notes on NodeJS + nginx + systemd: https://gist.github.com/alanorth/51acd476891c67dfe27725848cf5ace1
|
||||
|
||||
![ExpressJS running behind nginx](../images/2016/08/nodejs-nginx.png)
|
||||
![ExpressJS running behind nginx](2016/08/nodejs-nginx.png)
|
||||
|
||||
## 2016-08-16
|
||||
|
||||
|
@ -26,7 +26,7 @@ distinguishedName: CN=Last\, First (ILRI),OU=ILRI Ethiopia Employees,OU=ILRI Eth
|
||||
|
||||
- Changing the DSpace LDAP config to use `OU=ILRIHUB` seems to work:
|
||||
|
||||
![DSpace groups based on LDAP DN](../images/2016/09/ilri-ldap-users.png)
|
||||
![DSpace groups based on LDAP DN](2016/09/ilri-ldap-users.png)
|
||||
|
||||
- Notes for local PostgreSQL database recreation from production snapshot:
|
||||
|
||||
@ -326,9 +326,9 @@ Exception in thread "http-bio-127.0.0.1-8081-exec-25" java.lang.OutOfMemoryError
|
||||
|
||||
- Perhaps these particular issues *are* memory issues, the munin graphs definitely show some weird purging/allocating behavior starting this week
|
||||
|
||||
![Tomcat JVM usage day](../images/2016/09/tomcat_jvm-day.png)
|
||||
![Tomcat JVM usage week](../images/2016/09/tomcat_jvm-week.png)
|
||||
![Tomcat JVM usage month](../images/2016/09/tomcat_jvm-month.png)
|
||||
![Tomcat JVM usage day](2016/09/tomcat_jvm-day.png)
|
||||
![Tomcat JVM usage week](2016/09/tomcat_jvm-week.png)
|
||||
![Tomcat JVM usage month](2016/09/tomcat_jvm-month.png)
|
||||
|
||||
- And really, we did reduce the memory of CGSpace in late 2015, so maybe we should just increase it again, now that our usage is higher and we are having memory errors in the logs
|
||||
- Oh great, the configuration on the actual server is different than in configuration management!
|
||||
@ -345,7 +345,7 @@ JAVA_OPTS="-Djava.awt.headless=true -Xms3584m -Xmx3584m -XX:MaxPermSize=256m -XX
|
||||
|
||||
- Looking at Google Webmaster Tools again, it seems the work I did on URL query parameters and blocking via the `X-Robots-Tag` HTTP header in March, 2016 seem to have had a positive effect on Google's index for CGSpace
|
||||
|
||||
![Google Webmaster Tools for CGSpace](../images/2016/09/google-webmaster-tools-index.png)
|
||||
![Google Webmaster Tools for CGSpace](2016/09/google-webmaster-tools-index.png)
|
||||
|
||||
## 2016-09-16
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user