10.46243/jst.2021.v6.i04.pp42-46 registered
Privacy Violation Patterns in Non-Relational Databases
Resolves to https://www.jst.org.in/index.php/pub/article/view/763
Held by Longman Publishers (India) · prefix 10.46243 live · DOI address https://doi.org/10.46243/jst.2021.v6.i04.pp42-46
Registered 29 Sep 2026 via crossref · record version 2 · last change 29 Sep 2026, 11:59 PM · record sha256 8084009d9230e45b…
Resolve ⬇ Record (JSON) ⬇ Kernel Metadata Declaration (XML) Compare with Crossref Cite (APA · BibTeX · RIS · CSL)
What the DOI identifies
JournalArticle — an article in a journal · Digital · Visual · en
Privacy Violation Patterns in Non-Relational Databases (PrincipalTitle)
Published 2021-08-16
Part of Journal of Science & Technology · ISSN 2456-5660 · volume 06 · issue 01 · pages 42–46
Agents
- Shubham Dawkhar (author)
- Dr. Shwetambari Chiwhane (author)
- Longman Publishers (publisher)
Identifiers DOI 10.46243/jst.2021.v6.i04.pp42-46
Abstract
In 21st century data became the new oil. Every decision taken by organizations, governments, individuals is influenced by data. With analysis of data, one can predict market behaviour, can forecast weather. With such high value, it is important to manage and access data. Data has been growing exponentially since the late 1990s. there are many databases system used to store this data. Before the 2000’s mainly relational databases were used to store. But managing relational databases is expensive and complicated. To expand the capacity of relational databases hardware and skilled employees are needed. in the 2000s NoSQL databases were introduced. NoSQL database is fast, reliable, efficient, supports low-cost hardware up- gradation, and can store unstructured data. NoSQL databases are one the most preferred options as of today. With great speed and efficiency NoSQL rapidly became popular and widely used. But to achieve this function security is highly compromised. with a lot of security and privacy flaws data became more vulnerable to privacy breaching. many pieces of research have been done in the NoSQL domain to eliminate the flaws but all of them are scattered in this review paper we tried to synthesis the previous literature and compile all the repeating privacy violation patterns into one paper.
System metadata — ISO 26324:2025, Annex B · DOI Handbook 10.1
Each element by the standard's name (Annex B: reference elements, then administrative) and the Handbook's (in grey), read off the record above.
| Element | Value | In the record |
|---|---|---|
| DOI Name DOI name | 10.46243/jst.2021.v6.i04.pp42-46 | doi |
| Referent Type referentType | Creation | referent |
| Referent Sub-Type referentSubType | JournalArticle — an article in a journal | type |
| Referent Name(s) referentName(s) | Privacy Violation Patterns in Non-Relational Databases (PrincipalTitle, en) | titles |
| Basic Metadata basicMetadata | author: Shubham Dawkhar author: Dr. Shwetambari Chiwhane publisher: Longman Publishers published: 2021-08-16 part of: Journal of Science & Technology · ISSN 2456-5660 · vol. 06 · no. 01 · pp. 42–46 language: en form: Digital · Visual · Language | agents, dates, container, language, structural_type, modes, characters |
| Referent Identifier(s) alternateIdentifier(s) | none besides the DOI | identifiers, relations (IsSameAs) |
| Registration Authority registrationAuthorityCode | Crossref — issued by Crossref (member 25296); held here as a copy | record.source_agency (our code, ra_doi_name, for names issued here once appointed) |
| Created Date issueDate | 2026-09-11 | record.registered (when the DOI name was first registered) |
| relatedIdentifiers | none needed — the descriptive metadata is in this record | container, relations (only where the descriptive metadata lives at another identifier) |
complete Every System Metadata element is here, with the basic metadata a journal article needs.
The System Metadata Declaration (JSON) · the Kernel Metadata Declaration (XML) · what each sub-type needs
History — the ledger
Every change to this DOI, in order, as it was recorded. Entries are only ever added, never changed or removed.
| # | When | What | By | Changes |
|---|---|---|---|---|
| 1 | 29 Sep 2026, 10:00 PM | register registered at Crossref; record read from api.crossref.org | Administrator (admin) | 93 fields set · sha256 3b2477c48167… |
| 2 | 29 Sep 2026, 11:59 PM | update record re-read from api.crossref.org | Administrator (admin) | container.titles.0.value: |
Machine-readable: the history as JSON, with the full record after each change.
