10.46243/jst.2024.v9.i01.pp116-124 registered
SARCAMNET: EXTENSION OF LEXICON ALGORITHM FOR EMOJI-BASED SARCASM DETECTION FROM TWITTER DATA
Resolves to https://www.jst.org.in/index.php/pub/article/view/32
Held by Longman Publishers (India) · prefix 10.46243 live · DOI address https://doi.org/10.46243/jst.2024.v9.i01.pp116-124
Registered 29 Sep 2026 via crossref · record version 2 · last change 29 Sep 2026, 11:59 PM · record sha256 6609e4ee841830c4…
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
SARCAMNET: EXTENSION OF LEXICON ALGORITHM FOR EMOJI-BASED SARCASM DETECTION FROM TWITTER DATA (PrincipalTitle)
Published 2024-01-25
Part of Journal of Science & Technology · ISSN 2456-5660 · volume 9 · issue 1 · pages 116–124
Agents
- Dr.SUBBA REDDY BORRA Dr.SUBBA REDDY BORRA (author)
- Longman Publishers (publisher)
Identifiers DOI 10.46243/jst.2024.v9.i01.pp116-124
Abstract
Lexicon algorithm is used to determine the sentiment expressed by a textual content. This sentiment might be negative, neutral, or positive. It is possible to be sarcastic using only positive or neutral sentiment textual contents. Hence, lexicon algorithm can be useful but insufficient for sarcasm detection. It is necessary to extend the lexicon algorithm to come up with systems that would be proven efficient for sarcasm detection on neutral and positive sentiment textual contents. In this paper, two sarcasm analysis systems both obtained from the extension of the lexicon algorithm have been proposed for that sake. The first system consists of the combination of a lexicon algorithm and a pure sarcasm analysis algorithm. The second system consists of the combination of a lexicon algorithm and a sentiment prediction algorithm. Finally, naive bayes are used to predict sarcasm detection using pretrained features.
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.2024.v9.i01.pp116-124 | doi |
| Referent Type referentType | Creation | referent |
| Referent Sub-Type referentSubType | JournalArticle — an article in a journal | type |
| Referent Name(s) referentName(s) | SARCAMNET: EXTENSION OF LEXICON ALGORITHM FOR EMOJI-BASED SARCASM DETECTION FROM TWITTER DATA (PrincipalTitle, en) | titles |
| Basic Metadata basicMetadata | author: Dr.SUBBA REDDY BORRA Dr.SUBBA REDDY BORRA publisher: Longman Publishers published: 2024-01-25 part of: Journal of Science & Technology · ISSN 2456-5660 · vol. 9 · no. 1 · pp. 116–124 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) | 106 fields set · sha256 582157c1d1a8… |
| 2 | 29 Sep 2026, 11:59 PM | update record re-read from api.crossref.org | Administrator (admin) | abstract.value: 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.
