Tutorial about how to structure data in a relational database system
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- postgresql, sqlite
- Domain
- databases, documentation
Research direction
Start by reviewing the proposed tutorial scope: relational database structure, table and field choices, relationships, and constraints, while excluding SQL and database-engine specifics. Confirm whether scientists need this material and agree on the intended examples and coverage before drafting; done means a complete, published tutorial with that scope.
Written by the indexing model from the issue text.
Description
I've had the chance in the last few years to work in collaboration with biodiversity professionals, and from my IT-oriented perspective there's often a lack of knowledge about how to efficiently organise / structure the data in a relational database systems. To be more precise: there's generally enough knowledge to make something "that works", but a better structured database would be much more future-proof (less data errors, easier to reuse the data in other contexts such as data publication, web portals, ...)
That tutorial would not cover SQL nor the technicalities of a given database engine (SQLite, PostgreSQL, ...), but rather help answering questions such as
- should a given piece of information be placed in a new field or in a new table?
- how should I link tables X, Y and Z so they can be queried to answer a wide range of questions?
- what constraint can I configure early when I create a database so human errors (i.e. typos when entering data) are detected as early as possible (and the database doesn't get messier when it gets more used/bigger)
Is there any demand for this from scientists, or is it just me?
If so, I'd be happy to help contributing to a tutorial (but I think it can be a pretty large task, so I'd like to have an idea of the interest first).
- Dominant language
- HTML
- Stars
- 24
- Forks
- 10
- Avg merge
- 2d 32m
- Merged PRs (30d)
- 2
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
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.
More from inbo/tutorials
-
bug upstream
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
proposal tutorial
Difficulty 3/5 1-2 days Newbie friendliness 42/100
-
invalid question
Difficulty 3/5 1-2 days Newbie friendliness 42/100
-
🌈 enhancement design
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
0 - Backlog Bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
BrighterCommand/Brighter#4444 ·
Maintainers usually reply within 1 day
-
bug good first issue hacktoberfest redis
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
libredb/libredb-studio#1164 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
oracle/langchain-oracle#323 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
meshery/meshery#22114 · 1 comment ·
Maintainers usually reply within 1 day
-
comp-query-execution
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
ClickHouse/ClickHouse#122569 ·
Maintainers usually reply within 1 day