<?xml version="1.0" encoding="UTF-8"?>
<mods xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.loc.gov/mods/v3" version="3.1" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-1.xsd">
  <titleInfo>
    <title>Web-based inforamtion mapping at Himlayang Palanyag</title>
    <subTitle>monitoring and renewal tracking system</subTitle>
  </titleInfo>
  <name type="personal">
    <namePart>Saul, Charles Dhevon V.</namePart>
    <role>
      <roleTerm authority="marcrelator" type="text">creator</roleTerm>
    </role>
  </name>
  <name type="personal">
    <namePart>Cruz, Alexandrea Kiana U.</namePart>
  </name>
  <name type="personal">
    <namePart>Masubay, Lenmark I.</namePart>
  </name>
  <typeOfResource>text</typeOfResource>
  <originInfo>
    <place>
      <placeTerm type="code" authority="marccountry">xxu</placeTerm>
    </place>
    <place>
      <placeTerm type="text">ParanÌaque City</placeTerm>
    </place>
    <publisher>Olivarez College.</publisher>
    <dateIssued>2024</dateIssued>
    <issuance>monographic</issuance>
  </originInfo>
  <language>
    <languageTerm authority="iso639-2b" type="code">eng</languageTerm>
  </language>
  <physicalDescription>
    <form authority="marcform">print</form>
  </physicalDescription>
  <abstract>The Himlayang Palanyag Cemetery, formerly the ParanÌaque Public Cemetery, is highly challenged in its operations since it uses traditional paper-based management. This study answers these issues by developing a web-based information mapping monitoring and renewal tracking system tailored to the cemetery{92}s needs. This would make the process significantly more accessible on the user{92}s end while locating graves, accessing the details about burial, and remembering renewal tracking system tailored to the cemetery{92}s needs. This would make the process significantly more accessible on the user{92}s end while locating graves, accessing the details about burial, and remembering renewal dates, so the whole process appears manageable and accessible in general. Other features include renewal payment, automatic reminders on due deadlines for renewal, a map locating dead people in general, and increased efficiency with operations and convenience.           Information was solicited through quantitative surveys targeted at staff administrators and users, and answers were measured using a 5-point Likert scale. The beta testing results revealed that the users were content with the system{92}s ease of use, functionality, and maintenance. Functionality, maintainability, and usability are weighted measures that show broad agreement about the system{92}s efficacy.           In conclusion, the system dramatically improves the management of cemeteries{92} records and offers a modern alternative to manual procedures. This system enhances the user{92}s experience by safely providing remote access to critical data that will help the cemetery administration with unfruitful monitoring and tracking of renewals. Future recommendations include expanding automated alerts, improving usability, and integrating more search capabilities to present an even more intuitive interface.</abstract>
  <note type="statement of responsibility">Charles Dhevon V. Saul, Alexandrea Kiana U. Cruz, and Lenmark I. Masubay</note>
  <note>Undergraduate thesis.</note>
  <subject>
    <topic>Cemetery Management System</topic>
  </subject>
  <subject>
    <topic>Web-Based Information Mapping</topic>
  </subject>
  <subject>
    <topic>Renewal Tracking</topic>
  </subject>
  <subject>
    <topic>ParanÌaque Public Cemetery</topic>
  </subject>
  <subject>
    <topic>Grave Locator Map</topic>
  </subject>
  <subject>
    <topic>Automated Renewal Notifications</topic>
  </subject>
  <subject>
    <topic>Quantitative Survey Analysis</topic>
  </subject>
  <subject>
    <topic>User Satisfaction</topic>
  </subject>
  <subject>
    <topic>System Usability and Functionality</topic>
  </subject>
  <subject>
    <topic>Online Payment for Renewals</topic>
  </subject>
  <classification authority="ddc">T 004 2024 0143</classification>
  <recordInfo>
    <recordContentSource authority="marcorg">OCLRC</recordContentSource>
    <recordCreationDate encoding="marc">250726</recordCreationDate>
    <recordChangeDate encoding="iso8601">20260731013039.0</recordChangeDate>
    <recordIdentifier source="OCLRC">16573</recordIdentifier>
  </recordInfo>
</mods>
