Published
database
vr.tr.database · thing-q8513
Let an agent help design, query, secure and maintain databases, choose database types, and handle personal data lawfully.
Thing Registry Information and virtual systems INF.MED
Bundle → Layer → Finding → QuestionsClassifiersWhat it isWhy it existsDistinguishing featuresWhat robots and AI may and may not doMoral aspectsOwnersLinks to other meta-modelsIdentity and identifiersDirect propertiesRecognitionCapabilities and actionsHazards and failure modesStandards and interfacesContext of useSources
Bundle → Layer → Finding → Questions Filled
4 bundles · 8 layers · 8 findings · 16 questions
Design Choosing and designing.
Model
Database type.
Model
Database type.
- Which database model suits this data and workload? action
- What are the trade-offs? boundary
Schema
Schema design.
Schema
Schema design.
- How should the schema be designed and normalised? action
- Which indexes are needed? measurement
Query Using data.
SQL
Writing queries.
SQL
Queries.
- How can this query be written and optimised? action
- Is it safe against injection? boundary
Performance
Tuning.
Performance
Performance.
- Why is this query slow, and how can it be improved? measurement
- What does the query plan show? definition
Security Protection.
Access
Access control.
Access
Access control.
- Are access controls, encryption and auditing in place? boundary
- Which guidance applies? provenance
Backup
Backups.
Backup
Backups.
- Are backups taken and tested for restore? boundary
- What recovery objectives are needed? measurement
Law Personal data.
GDPR
Data protection.
GDPR
Data protection.
- Does the database hold personal data, and what legal basis and retention apply? provenance
- Is a data protection impact assessment needed? provenance
Senses
Repositories.
Senses
Repositories.
- Is a code or institutional repository meant rather than a database? boundary
- Which entry fits? action
Classifiers Filled
- Family
- Thing Registry
- Category
- Information and virtual systems
- Entry kind
- thing
- Plane
- INF
- Domain
- INF.MED
- Other names and narrower kinds
- source code repository, institutional repository, git repository, GitHub repository, Hugging Face model, monorepo, City of Santa Monica Designated Historic Landmark, quality register, cancer registry, geographic names board, Hakata Revival Plan, triplestore
What it is Filled
An organised collection of data stored and accessed electronically, managed by a database management system, in models such as relational, document, key-value, graph and time-series databases; related systems include institutional and code repositories, which store files and history rather than structured records.
Why it exists Filled
Let an agent help design, query, secure and maintain databases, choose database types, and handle personal data lawfully.
Distinguishing features Filled
- Structured storage
- Managed by a DBMS
- Queryable
- Needs security and backups
What robots and AI may and may not do Filled
Must not
- Access, copy or change records it is not authorized to.
- Delete or overwrite data without a verified backup and the owner's approval.
- Expose personal or confidential records through queries, logs or exports.
- Change the schema of a shared database without coordination.
Only with a human decision
- Bulk deletion or migration of production data.
- Granting other people access to a database.
May
- Query and update databases within the permissions it has been granted.
- Back up, check integrity and report errors in databases it manages.
- Document schemas and data lineage.
Moral aspects Filled
- Databases hold records about people that can harm them if leaked or wrong.
- Errors in a single database can spread to every system that relies on it.
Who is affected
- People whose data is stored
- Users and dependent systems
- Data owners
Owners Filled
Steward
The data owner or controller; the database administrator operates it.
Master systems
- Data catalogues and records of processing activities
Links to other meta-models Filled
parent
- Q1172284 - registry parent class
- Q386724 - registry parent class
- Q494756 - registry parent class
- Q59138870 - registry parent class
related
- data set - category
- database management system - software
- personal data - content
- computer programming - practice
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Vercy registry: vr.tr.database
- Wikidata: Q8513 (https://www.wikidata.org/wiki/Q8513)
Direct properties not applicable Not applicable
Not applicable
Plane INF: no invented physical properties.
Recognition optional Filled
- Tables, documents or graphs
- Query languages such as SQL
- Spreadsheets and code repositories are different tools
- Not physical; tables, collections and graphs managed by software on servers.
Capabilities and actions required Filled
- choose a database model
- design schemas and write queries
- secure and back up databases
- comply with data protection rules
Hazards and failure modes required Filled
- SQL injection and breaches
- Data loss without backups
- Unlawful processing of personal data
Standards and interfaces required Filled
- ISO/IEC 9075 SQL
- GDPR and data protection law
- Database rights in the EU
Context of use required Filled
- Storing, retrieving and managing data.
- relational databases
- document and key-value stores
- graph databases
- time-series and analytical databases
- repositories (related sense)
Sources Filled
- Wikidata item Q8513: database - identity and sense of the item
- Wikipedia: Database - general description of the item
Open questions
- Should database models be separate entries?
- How should products be linked?
- How should repositories be split off?
Machine files
Provenance
thing registry research (pass 2) · unreviewed
Built from: models/things/publications/thing-q8513/spec.json