10.46243/jst.2020.v5.i4.pp40-53 registered
Codecraft Competition: Learning to Code Through Contests Using Scratch
Resolves to https://www.jst.org.in/index.php/pub/article/view/510
Held by Longman Publishers (India) · prefix 10.46243 live · DOI address https://doi.org/10.46243/jst.2020.v5.i4.pp40-53
Registered 29 Sep 2026 via crossref · record version 2 · last change 29 Sep 2026, 11:59 PM · record sha256 fb927b6ee74a742b…
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
Codecraft Competition: Learning to Code Through Contests Using Scratch (PrincipalTitle)
Published 2020-06-30
Part of Journal of Science & Technology · ISSN 2456-5660 · issue Volume 5 · pages 40–53
Agents
- Longman Publishers (publisher)
Identifiers DOI 10.46243/jst.2020.v5.i4.pp40-53
Abstract
In this article, the design principles that guided the development of the Codecraft competition are discussed together with strategies for making the contest engaging for everyone. A random selection of 30 educators and 30 students who participated in the contests were also interviewed to find out their views about the competition and its impact on their computational thinking and creativity skills. Furthermore, 85 projects made up of codes from the Scratch program and submitted during the final round of the contest during the years 2016 to 2018 were processed using an online analytical tool known as Dr Scratch. To identify the progress made by the students, the different computational thinking concepts were analysed more deeply. The study revealed that over three years of the Codecraft competition, there was a significant improvement regarding the use of programming concepts, logic, and computational practices. Moreover, the average computational thinking (CT) score of the projects increased from 11.8 in 2016 to 14.2 in 2017 and 16.0 in 2018. Learning of computational concepts through an active contestbased approach also highlighted several advantages, such as motivation, fun, commitment, and enthusiasm, showing improvements related to creativity, computational thinking, and computational practices.
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.i4.pp40-53 | doi |
| Referent Type referentType | Creation | referent |
| Referent Sub-Type referentSubType | JournalArticle — an article in a journal | type |
| Referent Name(s) referentName(s) | Codecraft Competition: Learning to Code Through Contests Using Scratch (PrincipalTitle, en) | titles |
| Basic Metadata basicMetadata | publisher: Longman Publishers published: 2020-06-30 part of: Journal of Science & Technology · ISSN 2456-5660 · no. Volume 5 · pp. 40–53 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-06-30 | 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 volume number.
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) | 162 fields set · sha256 66a62734cdc5… |
| 2 | 29 Sep 2026, 11:59 PM | update record re-read from api.crossref.org | Administrator (admin) | container.titles.0.value: titles.0.value: |
Machine-readable: the history as JSON, with the full record after each change.
