10.46243/jst.2022.v7.i01.pp199-206 registered
Towards the Development of Intelligent Transportation Systems
Resolves to https://www.jst.org.in/index.php/pub/article/view/355
Held by Longman Publishers (India) · prefix 10.46243 live · DOI address https://doi.org/10.46243/jst.2022.v7.i01.pp199-206
Registered 29 Sep 2026 via crossref · record version 2 · last change 29 Sep 2026, 11:59 PM · record sha256 325e7c812c048bcc…
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
Towards the Development of Intelligent Transportation Systems (PrincipalTitle)
Published 2023-07-26
Part of Journal of Science & Technology · ISSN 2456-5660 · volume 7 · issue 1 · pages 199–206
Agents
- M.Rambabu M.Rambabu (author)
- Longman Publishers (publisher)
Identifiers DOI 10.46243/jst.2022.v7.i01.pp199-206
Abstract
Science communication forms the bridge between computer science researchers and their target audience. Re- searchers who can effectively draw attention to their research findings and communicate them comprehensibly not only help their target audience to actually learn something, but also benefit themselves from the increased visibility of their work and person. However, the necessary skills for good science communication must also be taught, and this has so far been neglected in thefield of software engineering education. We therefore designed and implemented a science communica- tion seminar for bachelor students of computer science curricula. Students take the position of a researcher who, shortly afterpublication, is faced with having to draw attention to the paper and effectively communicate the contents of the paper to oneor more target audiences. Based on this scenario, each student develops a communication strategy for an already published software engineering research paper and tests the resulting ideas with the other seminar participants. We explain our design decisions for the seminar, and combine our experiences with responses to a participant survey into lessons learned. With this experience report, we intend to motivate and enable other lecturers to offer a similar seminar at their university. Collectively, university lecturers can prepare the next generation of computer science researchers to not only be experts in their field, but also to communicate research findings more effectively.
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.pp199-206 | doi |
| Referent Type referentType | Creation | referent |
| Referent Sub-Type referentSubType | JournalArticle — an article in a journal | type |
| Referent Name(s) referentName(s) | Towards the Development of Intelligent Transportation Systems (PrincipalTitle, en) | titles |
| Basic Metadata basicMetadata | author: M.Rambabu M.Rambabu publisher: Longman Publishers published: 2023-07-26 part of: Journal of Science & Technology · ISSN 2456-5660 · vol. 7 · no. 1 · pp. 199–206 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) | 60 fields set · sha256 44d2be7bd981… |
| 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.
