https://github.com/centrefordigitalhumanities/edpop

A virtual research environment (VRE) that lets you collect, align and annotate bibliographical and biographical records from several online catalogs.

https://github.com/centrefordigitalhumanities/edpop

Science Score: 26.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • CITATION.cff file
  • codemeta.json file
    Found codemeta.json file
  • .zenodo.json file
    Found .zenodo.json file
  • DOI references
  • Academic publication links
  • Committers with academic emails
  • Institutional organization owner
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (10.0%) to scientific vocabulary

Keywords

annotation-tool bibliographic-data linked-data metadata
Last synced: 5 months ago · JSON representation

Repository

A virtual research environment (VRE) that lets you collect, align and annotate bibliographical and biographical records from several online catalogs.

Basic Info
  • Host: GitHub
  • Owner: CentreForDigitalHumanities
  • License: bsd-3-clause
  • Language: Python
  • Default Branch: develop
  • Homepage:
  • Size: 2.4 MB
Statistics
  • Stars: 1
  • Watchers: 4
  • Forks: 0
  • Open Issues: 54
  • Releases: 0
Topics
annotation-tool bibliographic-data linked-data metadata
Created over 8 years ago · Last pushed 6 months ago
Metadata Files
Readme License

README.md

EDPOP

This web application provides a virtual research environment (VRE) that lets you collect, align and annotate bibliographical and biographical records from several online catalogs.

The VRE consists of separate backend and frontend applications. They are documented in more detail in their respective directories. To run them jointly during development, take the following steps:

With Docker (recommended)

When running with Docker for the first time, you need to take the following steps:

  1. Run docker-compose up -d blazegraph.
  2. Visit the Blazegraph web interface and create the edpop and edpop_testing namespaces, as explained in more detail in the backend README. Note that the URL of the web interface ends in /bigdata when running Docker.

From then on, running the application is just a single command:

shell docker-compose up -d

You can then access the application at localhost:8000. Manually refresh the browser to see code changes reflected.

You can still run all the other commands that are discussed in the backend and frontend READMEs. You just have to prefix them with docker-compose exec $SERVICE in order to execute them within the right container. The services are listed in the docker-compose.yml. For example, to create a Django superuser, run this:

shell docker-compose exec backend python manage.py createsuperuser

Without Docker

  1. Make sure you have taken all preparation steps in the READMEs of both applications. Consult the docker-compose.yml and the Dockerfiles for recommended software versions.
  2. Open a new terminal in the frontend directory and run npm run watch.
  3. Open a new terminal in the backend directory and run python manage.py runserver.
  4. Open localhost:8000.
  5. Manually refresh the browser to see code changes reflected.

Tests of both applications can be run at any time, independently from each other.

Owner

  • Name: Centre for Digital Humanities
  • Login: CentreForDigitalHumanities
  • Kind: organization
  • Email: cdh@uu.nl
  • Location: Netherlands

Interdisciplinary centre for research and education in computational and data-driven methods in the humanities.

GitHub Events

Total
  • Issues event: 62
  • Delete event: 12
  • Issue comment event: 40
  • Member event: 1
  • Push event: 78
  • Pull request review comment event: 23
  • Pull request review event: 30
  • Pull request event: 33
  • Create event: 16
Last Year
  • Issues event: 62
  • Delete event: 12
  • Issue comment event: 40
  • Member event: 1
  • Push event: 78
  • Pull request review comment event: 23
  • Pull request review event: 30
  • Pull request event: 33
  • Create event: 16

Committers

Last synced: 8 months ago

All Time
  • Total Commits: 862
  • Total Committers: 6
  • Avg Commits per committer: 143.667
  • Development Distribution Score (DDS): 0.609
Past Year
  • Commits: 402
  • Committers: 3
  • Avg Commits per committer: 134.0
  • Development Distribution Score (DDS): 0.619
Top Committers
Name Email Commits
Julian Gonggrijp j****p@u****l 337
Tijmen Baarda t****a@g****m 243
Luka van der Plas l****s@m****m 151
BeritJanssen b****n@g****m 116
JelmerVNuss j****s@g****m 13
Sheean s****n@s****l 2
Committer Domains (Top 20 + Academic)

Issues and Pull Requests

Last synced: 6 months ago

All Time
  • Total issues: 59
  • Total pull requests: 24
  • Average time to close issues: over 1 year
  • Average time to close pull requests: 8 days
  • Total issue authors: 5
  • Total pull request authors: 2
  • Average comments per issue: 0.49
  • Average comments per pull request: 0.46
  • Merged pull requests: 21
  • Bot issues: 0
  • Bot pull requests: 0
Past Year
  • Issues: 45
  • Pull requests: 24
  • Average time to close issues: 4 months
  • Average time to close pull requests: 8 days
  • Issue authors: 3
  • Pull request authors: 2
  • Average comments per issue: 0.29
  • Average comments per pull request: 0.46
  • Merged pull requests: 21
  • Bot issues: 0
  • Bot pull requests: 0
Top Authors
Issue Authors
  • tijmenbaarda (23)
  • jgonggrijp (18)
  • BeritJanssen (3)
  • lukavdplas (3)
  • linguistcrg (1)
Pull Request Authors
  • tijmenbaarda (14)
  • jgonggrijp (10)
Top Labels
Issue Labels
enhancement (13) bug (12) quality (5) good first issue (3) wontfix (1) question (1) blocking! (1)
Pull Request Labels