Moving files around for package development in publications.

Author: SimonGoring

Proposals/publications/requirements.txt

@@ -36,14 +36,16 @@ For publications the primary concern is that DOIs are unique. This is the nature
 ALTER TABLE ndb.publications ADD CONSTRAINT publications_doi_unique UNIQUE(doi);
 ```
 
+This is ideal, however, there are duplicated publications in Neotoma where we can reasonably expect to find duplicated DOIs. Until this issue is resolved, we cannot implement a unique constraint on the DOIs.
+
 ### Ensuring Proper Metadata
 
 The CrossRef API provides a source of publisher "validated" metadata. We put validated in quotes because the validation is up to the publisher. We have found instances in the past where publishers provide incomplete metadata, or alternate formatting for test strings (for example, failing to capitalize specific epithets). Regardless, the CrossRef metadata form the basis for updating and improving our internal metadata.
 
 In the script `add_bibtex.py` in this folder we see the function `check_crossref()` which calls out using the title string for a paper. By calling the `works` endpoint of the CrossRef API we can either call for a DOI or call with a `title` query. Here we have pulled the title from the citation string and passed it into the `cite_object` variable:
 
 ```py
-def check_crossref(cite_object:str):
+def check_crossref(cite_object:str) -> dict:
     url = 'https://api.crossref.org/works'
     url_call = requests.get(url,
                             headers = {'Accept': 'application/json',