Satisfied Nor Dissatisfied: The Flexible Delivery of Student Affairs and Services Programs During Pandemic

Allocation at minting

The anchored record

Canonical JSON (keys sorted, no spaces, UTF-8). Its SHA-256 is the hash on chain.

{"abstract":"This descriptive-survey study examined the level of satisfaction on the delivery of student affairs and services programs during pandemic. The researchers conducted a survey to the two hundred (211) students of NORSU Mabinay campus from the eight (8) programs: BS Agriculture, BS Criminology, BS Business Administration, BS Industrial Technology, BS Computer Science, BS Hospitality Management, Bachelor of Elementary Education, and Bachelor of Secondary Education across year levels. Data were analyzed through frequency and percentage distribution, mean, and Pearson R using SPSS. Results revealed that the students are neither satisfied nor dissatisfied on the flexible delivery of the Student Services Programs as stipulated in CMO no. 08, series of 2021. Moreover, there is no significant relationship between the students’ level of satisfaction on SAS programs and their demographic profile in terms sex, course program, year level, disability, membership to indigenous group, and modality of leaning. Hence, regardless of profile, satisfaction level cannot be measured fully since not all services are fully implemented at the time of pandemic. Finally, the researchers establish a modified continuity plan to enhance the delivery of the student affairs and services programs to provide equitable support for learning opportunities.","abstract_source":"original","authors":["Lister Cabonilas"],"date":"2023-07-19","doi":"10.5281/zenodo.8164991","id":1640,"issue":9,"journal":{"issn":"2822-4353","name":"Psychology and Education: A Multidisciplinary Journal"},"pdf_sha256":"2d387dda8c6ba6ca4312f931135542072005e0eefae852c75d3949e5ed6822f6","schema":"scimatic-article/1","title":"Satisfied Nor Dissatisfied: The Flexible Delivery of Student Affairs and Services Programs During Pandemic","volume":10}

Check it yourself

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

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

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

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

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