README.md: Update DSpace wiki URLs

I didn't realize these LXD containers are not available on AMD64.
Now I understand why the build was so slow: because it was ARM64!

.travis.yml

@@ -4,8 +4,12 @@ python:
   - "3.6"
   - "3.7"
   - "3.8"
+  - "3.8-dev"  # 3.8 development branch
+jobs:
+  allow_failures:
+    - python: "3.8-dev"
 addons:
-  postgresql: "9.6"
+  postgresql: "10"
 before_script:
   - psql --version
   - createuser -U postgres dspacestatistics

CHANGELOG.md

@@ -4,11 +4,18 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.2.1] - 2020-03-02
+### Changed
+- Help text in API docs should reference UUIDs
+- Sample SQL file for tests should use UUIDs
+
 ## [1.2.0] - 2020-03-02
-## Changed
+### Changed
 - Remove Python 3.5 from TravisCI because black requires Python >= 3.6
 - Adapt API for DSpace 6+ UUIDs
-  - This requires droping the statistics database and re-indexing
+  - This requires dropping the statistics database and re-indexing
+
+### Updated
 - Run pipenv update, bringing requests 2.23.0 and pytest 5.3.5
 
 ## [1.1.1] - 2019-11-27

README.md

@@ -1,7 +1,10 @@
 # DSpace Statistics API [![Build Status](https://travis-ci.org/ilri/dspace-statistics-api.svg?branch=master)](https://travis-ci.org/ilri/dspace-statistics-api) [![builds.sr.ht status](https://builds.sr.ht/~alanorth/dspace-statistics-api.svg)](https://builds.sr.ht/~alanorth/dspace-statistics-api?)
-DSpace stores item view and download events in a Solr "statistics" core. This information is available for use in the various DSpace user interfaces, but is not exposed externally via any APIs. The DSpace 4/5 [REST API](https://wiki.duraspace.org/display/DSDOC5x/REST+API), for example, only exposes information about communities, collections, item metadata, and bitstreams.
+DSpace stores item view and download events in a Solr "statistics" core. This information is available for use in the various DSpace user interfaces, but is not exposed externally via any APIs. The DSpace 4/5/6 [REST API](https://wiki.lyrasis.org/display/DSDOC5x/REST+API), for example, only exposes information about communities, collections, item metadata, and bitstreams.
 
-This project contains an indexer and a [Falcon-based](https://falcon.readthedocs.io/) web application to make the statistics available via a simple REST API. You can read more about the Solr queries used to gather the item view and download statistics on the [DSpace wiki](https://wiki.duraspace.org/display/DSPACE/Solr).
+- If your DSpace is version 4 or 5, use [dspace-statistics-api v1.1.1](https://github.com/ilri/dspace-statistics-api/releases/tag/v1.1.1)
+- If your DSpace is version 6+, use [dspace-statistics-api v1.2.0 or greater](https://github.com/ilri/dspace-statistics-api/releases/tag/v1.2.0)
+
+This project contains an indexer and a [Falcon-based](https://falcon.readthedocs.io/) web application to make the statistics available via a simple REST API. You can read more about the Solr queries used to gather the item view and download statistics on the [DSpace wiki](https://wiki.lyrasis.org/display/DSPACE/Solr).
 
 If you use the DSpace Statistics API please cite:
 
@@ -9,9 +12,9 @@ If you use the DSpace Statistics API please cite:
 
 ## Requirements
 
-- Python 3.5+
+- Python 3.6+
 - PostgreSQL version 9.5+ (due to [`UPSERT` support](https://wiki.postgresql.org/wiki/UPSERT))
-- DSpace with [Solr usage statistics enabled](https://wiki.duraspace.org/display/DSDOC5x/SOLR+Statistics) (tested with 5.x)
+- DSpace with [Solr usage statistics enabled](https://wiki.lyrasis.org/display/DSDOC5x/SOLR+Statistics) (tested with 5.x)
 
 ## Installation
 Create a Python virtual environment and install the dependencies:
@@ -78,9 +81,9 @@ The API exposes the following endpoints:
 
   - GET `/` — return a basic API documentation page.
   - GET `/items` — return views and downloads for all items that Solr knows about¹. Accepts `limit` and `page` query parameters for pagination of results (`limit` must be an integer between 1 and 100, and `page` must be an integer greater than or equal to 0).
-  - GET `/item/id` — return views and downloads for a single item (`id` must be a positive integer). Returns HTTP 404 if an item id is not found.
+  - GET `/item/id` — return views and downloads for a single item (`id` must be a UUID). Returns HTTP 404 if an item id is not found.
 
-The item id is the *internal* id for an item. You can get these from the standard DSpace REST API.
+The item id is the *internal* uuid for an item. You can get these from the standard DSpace REST API.
 
 ¹ We are querying the Solr statistics core, which technically only knows about items that have either views or downloads. If an item is not present here you can assume it has zero views and zero downloads, but not necessarily that it does not exist in the repository.
 
@@ -91,8 +94,6 @@ The item id is the *internal* id for an item. You can get these from the standar
 - Use JSON in PostgreSQL
 - Add top items endpoint, perhaps `/top/items` or `/items/top`?
 - Make community and collection stats available
-- Support [DSpace 6 UUIDs](https://jira.duraspace.org/browse/DS-1782)
-- Switch to [Python 3.6+ f-string syntax](https://realpython.com/python-f-strings/)
 - Check IDs in database to see if they are deleted...
 
 ## License

dspace_statistics_api/docs/index.html

@@ -10,10 +10,10 @@
         <ul>
             <li>GET <code>/</code> — return a basic API documentation page.</li>
             <li>GET <code>/items</code> — return views and downloads for all items that Solr knows about¹. Accepts <code>limit</code> and <code>page</code> query parameters for pagination of results (<code>limit</code> must be an integer between 1 and 100, and <code>page</code> must be an integer greater than or equal to 0).</li>
-            <li>GET <code>/item/id</code> — return views and downloads for a single item (<code>id</code> must be a positive integer). Returns HTTP 404 if an item id is not found.</li>
+            <li>GET <code>/item/id</code> — return views and downloads for a single item (<code>id</code> must be a UUID). Returns HTTP 404 if an item id is not found.</li>
         </ul>
 
-        <p>The item id is the <em>internal</em> id for an item. You can get these from the standard DSpace REST API.</p>
+        <p>The item id is the <em>internal</em> uuid for an item. You can get these from the standard DSpace REST API.</p>
 
         <p>¹ We are querying the Solr statistics core, which technically only knows about items that have either views or downloads. If an item is not present here you can assume it has zero views and zero downloads, but not necessarily that it does not exist in the repository.</code>
     </body>