Skip to content

emory-libraries/researchdata

View on GitHub ↗Related repositories →

active 2025-01-092025-04-22 (UTC)

Complete coverage26,495 / 26,495 hourly files (100%) · 2 absent upstream2023-08-152026-08-22 (UTC)
Events
64
Pushes
5
Pull requests
0
Issues
30
Stars
0
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 104 days from 2025-01-09 to 2025-04-22. Pushes: 5 total, peak 3 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 30 total, peak 4 in a day. Comments: 27 total, peak 6 in a day. Stars: 0 total, peak 0 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
eporter23300014
tmiles214002
bwatson7812506
jendoty3003
jcrompton422001
rotated81001

Recent activity

Latest issues, pull requests and releases

  • Issue#24tmiles22025-04-22 19:32
    Establish a retention plan for exported datasets
  • Issue#1tmiles22025-04-22 19:31
    Export copies of Dataverse datasets
  • Issue#4tmiles22025-04-22 19:31
    Communications Plan
  • Issue#2tmiles22025-04-22 19:31
    Update research data repository requirements
  • Issue#26tmiles22025-03-18 19:23
    Document the process for restoring files that have transitioned to Amazon S3 Glacier
  • Issue#26tmiles22025-03-10 13:36
    Document the process for restoring files that have transitioned to Amazon S3 Glacier
  • Issue comment#26jcrompton422025-03-07 19:03
    Document the process for restoring files that have transitioned to Amazon S3 Glacier
  • Issue#26jcrompton422025-03-07 19:03
    Document the process for restoring files that have transitioned to Amazon S3 Glacier
  • Issue comment#24tmiles22025-03-04 21:24
    Establish a retention plan for exported datasets
  • Issue comment#26tmiles22025-03-04 19:59
    Document the process for restoring files that have transitioned to Amazon S3 Glacier
  • Issue#26tmiles22025-03-04 19:24
    Document the process for restoring files that have transitioned to Amazon S3 Glacier
  • Issue#21bwatson782025-02-13 16:43
    Review Technology Support Scenarios
  • Issue comment#21bwatson782025-02-13 16:40
    Review Technology Support Scenarios
  • Issue#11eporter232025-02-04 18:55
    Identify Emory datasets within UNC instance
  • Issue comment#25eporter232025-02-04 18:45
    Test content freeze access (for new dataset deposits)
  • Issue#25eporter232025-02-04 18:45
    Test content freeze access (for new dataset deposits)
  • Issue comment#11eporter232025-02-04 14:21
    Identify Emory datasets within UNC instance
  • Issue comment#19eporter232025-02-04 14:20
    Provide training for S3/AWS access
  • Issue#19eporter232025-02-04 14:20
    Provide training for S3/AWS access
  • Issue comment#21eporter232025-01-30 16:01
    Review Technology Support Scenarios
  • Issue comment#19rotated82025-01-30 15:44
    Provide training for S3/AWS access
  • Issue#25eporter232025-01-30 15:19
    Test content freeze access
  • Issue#11tmiles22025-01-30 15:12
    Identify Emory datasets within UNC instance
  • Issue#17tmiles22025-01-30 15:10
    Return a list of all Emory Dataverse IDs via API
  • Issue#11tmiles22025-01-28 18:55
    Identify Emory datasets within UNC instance

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 0 stars here means stars gained during the window, not the repo's star count.