10.46243/jst.2020.v5.i3.pp218-224 registered
Smart Driving License Verification System
Resolves to https://www.jst.org.in/index.php/pub/article/view/471
Held by Longman Publishers (India) · prefix 10.46243 live · DOI address https://doi.org/10.46243/jst.2020.v5.i3.pp218-224
Registered 29 Sep 2026 via crossref · record version 2 · last change 29 Sep 2026, 11:59 PM · record sha256 f237ffc208e2e077…
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
Smart Driving License Verification System (PrincipalTitle)
Published 2020-05-29
Part of Journal of Science & Technology · ISSN 2456-5660 · volume 5 · issue 3 · pages 218–224
Agents
- Longman Publishers (publisher)
Identifiers DOI 10.46243/jst.2020.v5.i3.pp218-224
Abstract
The driving license system is very difficult to monitor via old conventional methods. The conventional verification system involves wastage of time and a chance to lead corruption. This project represents a biometricbased System for driving licensing verification. Biometrics is one of the most critical emerging technologies of the 21st century. From the various biometric features, Finger Print is one of the best. To keep the record of attendance report of students has become a very difficult work because sometimes their attendance may be recorded or missed. To deal with this problem i.e. to get the attendances recorded correctly we are using two different technologies viz. embedded system and biometrics. It is a very useful biometric-based driving license monitoring system that is easy and more suitable to monitor. Fingerprint verification is an important biometric technique for human identification. In this project, we represent a prototype automatic license authentication system. It uses fingerprints to verify the identity of an individual. In this project, we use the Fingerprint authentication scheme which is a non-imitable biometric authentication scheme. Using biometric authentication, we can try to avoid the non-licensed person from driving. While issuing the license, the specific person’s fingerprint is to be stored on the webserver along with its details. So at anywhere, the person should place on his finger on the fingerprint reader
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.2020.v5.i3.pp218-224 | doi |
| Referent Type referentType | Creation | referent |
| Referent Sub-Type referentSubType | JournalArticle — an article in a journal | type |
| Referent Name(s) referentName(s) | Smart Driving License Verification System (PrincipalTitle, en) | titles |
| Basic Metadata basicMetadata | publisher: Longman Publishers published: 2020-05-29 part of: Journal of Science & Technology · ISSN 2456-5660 · vol. 5 · no. 3 · pp. 218–224 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 | 2020-05-29 | 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.
Recommended for a journal article and not in this record: its author(s), editor(s) or corporate author.
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) | 57 fields set · sha256 0b94c2215fdd… |
| 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.
