Awareness and Satisfaction of the Registered Bookkeepers on the Online Registration and Update System (ORUS) of the Bureau of Internal Revenue

Allocation at minting

The anchored record

Canonical JSON (keys sorted, no spaces, UTF-8). Its SHA-256 is the hash on chain. The abstract here is gemini shortened, not the author's own text.

{"abstract":"The Online Registration and Update System (ORUS) was developed by the Bureau of Internal Revenue to enable taxpayers to register, update, and transact registration-related activities online. This study aimed to determine the level of awareness and satisfaction of registered bookkeepers with ORUS and their relationship with identified variables. A descriptive method was used with 146 registered bookkeepers from Revenue District 78 Binalbagan as of December 2022. Findings showed that respondents were predominantly female, aged 23-30 years, and had 1-5 years of practice. Registered bookkeepers demonstrated high awareness of ORUS, with those aged 23-30 years having a mean score of 3.75, males a mean score of 3.70, and those with 11-15 years of practice a mean score of 3.69. In terms of satisfaction, bookkeepers aged 63-70 years displayed the highest mean score of 3.77, male respondents a mean score of 3.65, and those with 11-15 years of practice a mean score of 3.64. No significant differences were found in awareness or satisfaction when grouped by age, sex, and years of practice, with p-values ranging from 0.306 to 0.740 for awareness and 0.539 to 0.997 for satisfaction.","abstract_source":"gemini_shortened","authors":["Jonah Palanog","Joyce Decendario"],"date":"2025-03-08","doi":"10.70838/pemj.330209","id":4655,"issue":2,"journal":{"issn":"2822-4353","name":"Psychology and Education: A Multidisciplinary Journal"},"pdf_sha256":"44825091a60acf444b2360bc8ec38e5693827eee856e0c7fd2d20a534180dc81","schema":"scimatic-article/1","title":"Awareness and Satisfaction of the Registered Bookkeepers on the Online Registration and Update System (ORUS) of the Bureau of Internal Revenue","volume":33}

Check it yourself

1. The record, from the token's own metadata:

printf '%s' "$(curl -s https://scimatic.org/nft/articles/4655.json | jq -r .canonical_record)" | sha256sum

2. The hash stored on chain (contentHash(4655)):

curl -s https://rpc.scimatic.net -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_call","params":[{"to":"0x0E596B4bb924937aA35D9b342A90347ed6F05eF8","data":"0xf3e0c290000000000000000000000000000000000000000000000000000000000000122f"},"latest"]}'

The two must be equal (the second with a 0x in front).