10.46243/jst.2022.v7.i01.pp166-173 registered
RASPBERRY PI FACE DETECTION DOOR LOCK
Resolves to https://www.jst.org.in/index.php/pub/article/view/262
Held by Longman Publishers (India) · prefix 10.46243 live · DOI address https://doi.org/10.46243/jst.2022.v7.i01.pp166-173
Registered 29 Sep 2026 via crossref · record version 2 · last change 29 Sep 2026, 11:59 PM · record sha256 5967badac105524c…
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
RASPBERRY PI FACE DETECTION DOOR LOCK (PrincipalTitle)
Published 2023-07-26
Part of Journal of Science & Technology · ISSN 2456-5660 · volume 7 · issue 1 · pages 166–173
Agents
- Dr.Syed Abdul Sattar Dr.Syed Abdul Sattar (author)
- Longman Publishers (publisher)
Identifiers DOI 10.46243/jst.2022.v7.i01.pp166-173
Abstract
A home security system is a need in today's world. However, the usage of keys, security cards, passwords or pattern locks to open most doors has recently been outlawed. Yet robbery and identity theft are much more dangerous repercussions of key loss than the actual loss of a key itself Consequently, this has been deemed a severe problem. A door access control system was successfully installed thanks to the usage of the Internet of Things (IoT). As well as serving as the primary controller for face recognition, youth system, and locking system, the Raspberry Pi is employed as a compact computer board that can be programmed. The guy standing in front of the entryway is captured by a ca mera on the wall. Whenever the system fails to recognise a person's face, a warning will be sent. Using the Internet of Things, a user may control who has access to a door (IoT). Facial recognition, Rasberry Pi, Internet of things (IOT), and home security systems are some of the terms we'll be using today
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.2022.v7.i01.pp166-173 | doi |
| Referent Type referentType | Creation | referent |
| Referent Sub-Type referentSubType | JournalArticle — an article in a journal | type |
| Referent Name(s) referentName(s) | RASPBERRY PI FACE DETECTION DOOR LOCK (PrincipalTitle, en) | titles |
| Basic Metadata basicMetadata | author: Dr.Syed Abdul Sattar Dr.Syed Abdul Sattar publisher: Longman Publishers published: 2023-07-26 part of: Journal of Science & Technology · ISSN 2456-5660 · vol. 7 · no. 1 · pp. 166–173 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 | 2024-02-16 | 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) | 85 fields set · sha256 1d5f057b4393… |
| 2 | 29 Sep 2026, 11:59 PM | update record re-read from api.crossref.org | Administrator (admin) | agents.0.name.family: agents.0.name.given: container.titles.0.value: |
Machine-readable: the history as JSON, with the full record after each change.
