10.46243/jst.2022.v7.i10.pp72-85 registered
Teaching Computer Science Students to Communicate Scientific Findings More
Resolves to https://www.jst.org.in/index.php/pub/article/view/897
Held by Longman Publishers (India) · prefix 10.46243 live · DOI address https://doi.org/10.46243/jst.2022.v7.i10.pp72-85
Registered 29 Sep 2026 via crossref · record version 2 · last change 29 Sep 2026, 11:59 PM · record sha256 dd7d9d4ecec2eb94…
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
Teaching Computer Science Students to Communicate Scientific Findings More (PrincipalTitle)
Published 2022-12-21
Part of Journal of Science & Technology · ISSN 2456-5660 · volume 7 · issue 10 · pages 72–85
Agents
- G Shobha G Shobha (author)
- Longman Publishers (publisher)
Identifiers DOI 10.46243/jst.2022.v7.i10.pp72-85
Abstract
Communicate Scientific Security is a part of the Information Security framework and is specifically applied to the components that affect Communicate Scientific that include Computer Security, Data security and other wider realms of the Information Security framework. Communicate Scientific security has its own particular nuances and is one of the highest visible security components that affect the end user through their daily payment interaction with business. Communicate Scientific security is the protection of Communicate Scientific assets from unauthorized access, use, alteration, or destruction. Dimensions of Communicate Scientific security-Integrity, Non-repudiation, Authenticity, Confidentiality, Privacy, Availability. E- Commerce offers the banking industry great opportunity, but also creates a set of new risks and vulnerability such as security threats. Information security, therefore, is an essential management and technical requirement for any efficient and effective Payment transaction activities over the internet. Still, its definition is a complex Endeavour due to the constant technological and business change and requires a coordinated match of algorithm and technical solutions. In this paper we discussed with Overview of Communicate Scientific security, Understand the Online Shopping Steps to place an order, Purpose of Security in E-commerce, Different security issues in E-commerce, Secure online shopping guidelines
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.i10.pp72-85 | doi |
| Referent Type referentType | Creation | referent |
| Referent Sub-Type referentSubType | JournalArticle — an article in a journal | type |
| Referent Name(s) referentName(s) | Teaching Computer Science Students to Communicate Scientific Findings More (PrincipalTitle, en) | titles |
| Basic Metadata basicMetadata | author: G Shobha G Shobha publisher: Longman Publishers published: 2022-12-21 part of: Journal of Science & Technology · ISSN 2456-5660 · vol. 7 · no. 10 · pp. 72–85 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) | 96 fields set · sha256 70b0019d3cb9… |
| 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.
