Firefighting Capabilities and Performance of the Bureau of Fire Protection-Marinduque in Responding to Fire Incidence: Basis for Service Delivery Framework

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":"This descriptive study assessed Marinduque's fire incidence from 2018 to 2022 and the firefighting capabilities and performance of the Bureau of Fire Protection (BFP)-Marinduque, aiming to propose a service delivery framework. Data were gathered from BFP documentation records and survey questionnaires, analyzed using frequency count, percentage calculations, ranking, and Pearson correlation coefficient. Marinduque experienced 58 fire events, with open flames or unsupervised cooking being the leading cause in Mogpog. The BFP's overall capability in tools, PPE, and firetrucks was 74.49% (\"adequate\"), and manpower capability was 62.06% (\"adequate\"). Staff possessed hard, professional, and specialized skills. Facilities and infrastructure adequacy had a mean of 3.25, and sufficiency a mean of 3.06. BFP Marinduque maintained a 100% budget utilization rate for five fiscal years. Performance ratings for fire prevention activities ranged from 4.08 to 4.69, indicating \"Very Satisfactory\" to \"Outstanding\" performance. A significant relationship was found between firefighting capabilities and BFP-Marinduque personnel performance, leading to the rejection of the null hypothesis.","abstract_source":"gemini_shortened","authors":["Felix Echavaria","Junn Quirk Espiritu"],"date":"2024-03-19","doi":"10.5281/zenodo.10838874","id":2680,"issue":1,"journal":{"issn":"2822-4353","name":"Psychology and Education: A Multidisciplinary Journal"},"pdf_sha256":"efbe811ac44295549ee36e66656ea8cbb9d5d02a9230f1c3691257e1f005d0fc","schema":"scimatic-article/1","title":"Firefighting Capabilities and Performance of the Bureau of Fire Protection-Marinduque in Responding to Fire Incidence: Basis for Service Delivery Framework","volume":18}

Check it yourself

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

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

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

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

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