few questions about 'database' metadata, and versioning
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 82
- Forks
- 21
- Avg merge
- 35m
- Merged PRs (30d)
- 1
Description
Very well done and lovely project! thanks
We thought may be to provide access to datasets you provide via https://github.com/datalad/datalad/ (based on git/git-annex). Here is e.g. a sample git/annex repository http://datasets.datalad.org/test/physionet/eegmmidb/ which accesses data from your website. Before jumping to just crawl the entire website from https://physionet.org/physiobank/database/ I wondered to ask
- is list of database (datasets) is available in some machine readable form?
- per each database, all that information (citations, description) - does it leave solely in html or composed from some centralized DB?
- how do you "version" files? i.e. if authors reupload newer/fixed versions -- do they just replace old copies? or it never happened (yet)?
Thank you in advance!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the PhysioNet database page, the DataLad sample repository, and the questions about machine-readable dataset listings, metadata sources, and file versioning. First determine whether the issue has a concrete implementation target; done would require an agreed scope and documented behavior for dataset metadata and version history.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, html
- Domain
- databases, documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100