Merge remote-tracking branch 'origin/main' into psskb

.github/workflows/new_prefix_pr.yml

@@ -39,7 +39,10 @@ jobs:
       - name: Update
         id: update
         if: steps.check_labels.outputs.hasRequiredLabels == 'true'
-        run: python -m bioregistry.gh.new_prefix --github
+        run: |
+          issue_url="${{ github.event.issue.html_url }}"
+          issue_number=$(echo "$issue_url" | grep -oE '[0-9]+$')
+          python -m bioregistry.gh.new_prefix --github --issue=$issue_number
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
       - name: Create Branch

.github/workflows/paper_ranking.yml

@@ -2,7 +2,7 @@ name: Run Paper Ranking Script and Update Issue
 
 on:
   schedule:
-    - cron: '0 0 1 * *' # runs on the first day of every month
+    - cron: '0 5 1 * *' # runs on the first day of every month
   workflow_dispatch:
 
 permissions:
@@ -31,8 +31,8 @@ jobs:
     - name: Set Date Variables
       id: set-date-variables
       run: |
-        end_date=$(date +'%Y-%m-%d')
-        start_date=$(date -d "$end_date - 30 days" +'%Y-%m-%d')
+        start_date=$(date -d "$(date +'%Y-%m-01') -1 month" +'%Y-%m-01')
+        end_date=$(date -d "$start_date +1 month -1 day" +'%Y-%m-%d')
         echo "START_DATE=$start_date" >> $GITHUB_ENV
         echo "END_DATE=$end_date" >> $GITHUB_ENV
     

docs/CONTRIBUTING.md

@@ -101,6 +101,8 @@ https://github.com/biopragmatics/bioregistry/issues/158.
 6. New prefixes should not end with "ID" as a way to signify that the prefix is
    used for identifiers, like in `doid` for the Disease Ontology or `caid` for
    ClinGen Canonical Allele identifier.
+7. New prefixes should be singular instead of plural. For example `hgnc.genes`
+   would be bad while `hgnc.gene` would be better.
 
 These policies were developed in parallel with the OBO Foundry policy on
 choosing a prefix (i.e., IDSPACE) at http://obofoundry.org/id-policy.html.
@@ -221,6 +223,45 @@ https://github.com/biopragmatics/bioregistry/issues/359.
 Original discussion about prefix parking can be found at
 https://github.com/biopragmatics/bioregistry/issues/365.
 
+#### Contact and Attribution
+
+The Bioregistry collects the name, email, and optionally, the GitHub username
+and ORCID identifier for individuals in several places:
+
+1. As the primary responsible contact person for the semantic space associated
+   with a prefix.
+2. As the creator, contributor, or reviewer of record in the Bioregistry
+
+We require in each situation that all fields explicitly correspond to the
+individual with the goal to promote transparency and decrease the diffusion of
+responsibility. This is inspired by and mirrors the OBO Foundry's
+[Principle 11 "Locus of Authority"](https://obofoundry.org/principles/fp-011-locus-of-authority.html).
+
+For the email field, this means that the following kinds of email addresses are
+not acceptable:
+
+1. Mailing lists
+2. Help desks
+3. Group emails
+4. Issue trackers
+5. Email addresses associated with a responsible person's assistant or
+   administration
+
+For the GitHub field, this means that GitHub organizations or GitHub users that
+represent a group, such as a lab, are not acceptable.
+
+For the ORCID field, it understood that an ORCID record should correspond to an
+individual in the same spirit as this policy, and that the ORCID service should
+not be abused to represent any non-individual.
+
+In addition to the primary responsible contact person, the Bioregistry has
+structured fields for additional contact methods, such as:
+
+- `contact_page` for annotating the URL of a web page that has contact
+  information, e.g., containing a contact form. Only curate this field if a
+  direct email is not available, as this is the least transparent option for
+  contact
+
 #### Review of New Prefix Requests
 
 Review of new prefix requests is handled by the Bioregistry Review Team, whose