| 000 -LEADER |
|---|
| fixed length control field |
11364nam a2201225Ia 4500 |
| 000 - LEADER |
|---|
| fixed length control field |
09215ntm a2200205 i 4500 |
| 001 - CONTROL NUMBER |
|---|
| control field |
91276 |
| 003 - CONTROL NUMBER IDENTIFIER |
|---|
| control field |
0 |
| 005 - DATE AND TIME OF LATEST TRANSACTION |
|---|
| control field |
20250920173826.0 |
| 008 - FIXED-LENGTH DATA ELEMENTS--GENERAL INFORMATION |
|---|
| fixed length control field |
241029n 000 0 eng d |
| 010 ## - LIBRARY OF CONGRESS CONTROL NUMBER |
|---|
| Canceled/invalid LC control number |
|
| -- |
|
| -- |
|
| LC control number |
|
| NUCMC control number |
|
| 015 ## - NATIONAL BIBLIOGRAPHY NUMBER |
|---|
| Source |
2 |
| National bibliography number |
|
| 016 ## - NATIONAL BIBLIOGRAPHIC AGENCY CONTROL NUMBER |
|---|
| Source |
|
| -- |
|
| Record control number |
|
| Canceled/invalid control number |
|
| 020 ## - INTERNATIONAL STANDARD BOOK NUMBER |
|---|
| -- |
|
| -- |
|
| International Standard Book Number |
|
| -- |
|
| Canceled/invalid ISBN |
|
| Terms of availability |
|
| Qualifying information |
|
| -- |
|
| 022 ## - INTERNATIONAL STANDARD SERIAL NUMBER |
|---|
| Incorrect ISSN |
|
| -- |
|
| ISSN-L |
|
| International Standard Serial Number |
2 |
| 024 ## - OTHER STANDARD IDENTIFIER |
|---|
| Source of number or code |
|
| -- |
|
| Additional codes following the standard number or code |
|
| Terms of availability |
|
| Standard number or code |
|
| Qualifying information |
|
| 028 ## - PUBLISHER OR DISTRIBUTOR NUMBER |
|---|
| Publisher or distributor number |
|
| -- |
|
| Source |
|
| 029 ## - OTHER SYSTEM CONTROL NUMBER (OCLC) |
|---|
| OCLC library identifier |
|
| -- |
|
| System control number |
|
| 032 ## - POSTAL REGISTRATION NUMBER |
|---|
| Postal registration number |
|
| -- |
|
| Source agency assigning number |
|
| 035 ## - SYSTEM CONTROL NUMBER |
|---|
| System control number |
|
| -- |
|
| -- |
|
| Canceled/invalid control number |
|
| -- |
|
| -- |
|
| 037 ## - SOURCE OF ACQUISITION |
|---|
| Note |
|
| -- |
|
| Terms of availability |
|
| Stock number |
|
| Source of stock number/acquisition |
|
| 040 ## - CATALOGING SOURCE |
|---|
| Description conventions |
|
| -- |
rda |
| Original cataloging agency |
|
| Modifying agency |
|
| Language of cataloging |
|
| Transcribing agency |
|
| 041 ## - LANGUAGE CODE |
|---|
| Language code of librettos |
|
| -- |
|
| Language code of text/sound track or separate title |
|
| Language code of summary or abstract |
|
| Language code of accompanying material other than librettos and transcripts |
|
| Language code of original |
|
| Language code of accessible visual language |
|
| 043 ## - GEOGRAPHIC AREA CODE |
|---|
| Geographic area code |
|
| -- |
|
| Local GAC code |
|
| 045 ## - TIME PERIOD OF CONTENT |
|---|
| Formatted 9999 B.C. through C.E. time period |
|
| -- |
|
| Time period code |
|
| 050 ## - LIBRARY OF CONGRESS CALL NUMBER |
|---|
| Classification number |
|
| -- |
|
| Supplementary class number (MU) [OBSOLETE] |
|
| Item number |
2 |
| -- |
0 |
| 051 ## - LIBRARY OF CONGRESS COPY, ISSUE, OFFPRINT STATEMENT |
|---|
| Copy information |
|
| -- |
|
| Classification number |
|
| Item number |
|
| 055 ## - CLASSIFICATION NUMBERS ASSIGNED IN CANADA |
|---|
| Classification number |
|
| -- |
|
| Item number |
|
| 060 ## - NATIONAL LIBRARY OF MEDICINE CALL NUMBER |
|---|
| Classification number |
|
| -- |
|
| Item number |
|
| 070 ## - NATIONAL AGRICULTURAL LIBRARY CALL NUMBER |
|---|
| Classification number |
|
| -- |
|
| Item number |
|
| 072 ## - SUBJECT CATEGORY CODE |
|---|
| Source |
|
| -- |
|
| -- |
|
| Subject category code |
|
| Subject category code subdivision |
|
| 082 ## - DEWEY DECIMAL CLASSIFICATION NUMBER |
|---|
| Classification number |
|
| -- |
|
| -- |
|
| Item number |
2 |
| -- |
|
| 084 ## - OTHER CLASSIFICATION NUMBER |
|---|
| Number source |
|
| -- |
|
| Classification number |
|
| 086 ## - GOVERNMENT DOCUMENT CLASSIFICATION NUMBER |
|---|
| Number source |
|
| -- |
|
| Classification number |
|
| 090 ## - LOCALLY ASSIGNED LC-TYPE CALL NUMBER (OCLC); LOCAL CALL NUMBER (RLIN) |
|---|
| Classification number (OCLC) (R) ; Classification number, CALL (RLIN) (NR) |
|
| -- |
|
| -- |
|
| Local cutter number (OCLC) ; Book number/undivided call number, CALL (RLIN) |
|
| -- |
|
| 092 ## - LOCALLY ASSIGNED DEWEY CALL NUMBER (OCLC) |
|---|
| Filing suffix |
|
| -- |
|
| Classification number |
|
| Item number |
|
| 096 ## - LOCALLY ASSIGNED NLM-TYPE CALL NUMBER (OCLC) |
|---|
| Classification number |
|
| -- |
|
| Item number |
|
| 097 ## - |
|---|
| -- |
|
| -- |
|
| -- |
|
| 100 ## - MAIN ENTRY--PERSONAL NAME |
|---|
| Relator term |
|
| -- |
|
| Personal name |
Aquino, Aaliyah May A. Camus, Jr. Ernesto F. Fisalbon, Niccole D. Isisdro, Chielo Marie P. Naguit, Eingel Marvic Emmanuelle E. opena, Ralph Christopher F. |
| Dates associated with a name |
|
| Numeration |
4 |
| Affiliation |
|
| Titles and words associated with a name |
0 |
| Fuller form of name |
16 |
| 110 ## - MAIN ENTRY--CORPORATE NAME |
|---|
| Relator term |
|
| -- |
|
| Corporate name or jurisdiction name as entry element |
|
| Date of meeting or treaty signing |
|
| Subordinate unit |
|
| Number of part/section/meeting |
|
| Location of meeting |
|
| Form subheading |
|
| 111 ## - MAIN ENTRY--MEETING NAME |
|---|
| Meeting name or jurisdiction name as entry element |
|
| -- |
|
| Date of meeting or treaty signing |
|
| Number [OBSOLETE] |
|
| Number of part/section/meeting |
|
| Location of meeting |
|
| 130 ## - MAIN ENTRY--UNIFORM TITLE |
|---|
| Version |
|
| -- |
|
| Uniform title |
|
| Name of part/section of a work |
|
| Date of a work |
|
| Language of a work |
|
| Form subheading |
|
| 210 ## - ABBREVIATED TITLE |
|---|
| Abbreviated title |
|
| -- |
|
| Qualifying information |
|
| 222 ## - KEY TITLE |
|---|
| Key title |
|
| -- |
|
| Qualifying information |
|
| 240 ## - UNIFORM TITLE |
|---|
| Version |
|
| -- |
|
| Uniform title |
|
| Medium of performance for music |
|
| Miscellaneous information |
|
| Number of part/section of a work |
|
| Date of a work |
|
| Language of a work |
|
| Arranged statement for music |
|
| Name of part/section of a work |
|
| Form subheading |
|
| 245 #0 - TITLE STATEMENT |
|---|
| Title |
|
| -- |
PortPulse: a cloud-based real-time tracking system for enhanced luggage management. |
| Designation of section section/part/series: (SE) [OBSOLETE] |
|
| Remainder of title |
|
| Number of part/section of a work |
|
| Statement of responsibility, etc. |
|
| Medium |
6 |
| Name of part/section of a work |
|
| 246 ## - VARYING FORM OF TITLE |
|---|
| Title proper/short title |
|
| -- |
|
| Remainder of title |
|
| Number of part/section of a work |
|
| Display text |
|
| Date or sequential designation |
6 |
| Name of part/section of a work |
|
| 249 ## - |
|---|
| -- |
|
| -- |
|
| -- |
|
| 250 ## - EDITION STATEMENT |
|---|
| Linkage |
|
| -- |
|
| Edition statement |
|
| Remainder of edition statement |
|
| 260 ## - PUBLICATION, DISTRIBUTION, ETC. |
|---|
| Place of manufacture |
|
| -- |
|
| Place of publication, distribution, etc. |
|
| Name of publisher, distributor, etc. |
|
| Manufacturer |
|
| Date of publication, distribution, etc. |
|
| Date of manufacture |
|
| 264 ## - PRODUCTION, PUBLICATION, DISTRIBUTION, MANUFACTURE, AND COPYRIGHT NOTICE |
|---|
| Materials specified |
|
| -- |
|
| Place of production, publication, distribution, manufacture |
|
| -- |
|
| Name of producer, publisher, distributor, manufacturer |
|
| Date of production, publication, distribution, manufacture, or copyright notice |
4541346 |
| 300 ## - PHYSICAL DESCRIPTION |
|---|
| Accompanying material |
|
| -- |
|
| Dimensions |
28 cm. |
| Extent |
92 pp. |
| Other physical details |
|
| 310 ## - CURRENT PUBLICATION FREQUENCY |
|---|
| Current publication frequency |
|
| -- |
|
| Date of current publication frequency |
|
| 321 ## - FORMER PUBLICATION FREQUENCY |
|---|
| Former publication frequency |
|
| -- |
|
| Dates of former publication frequency |
|
| 336 ## - CONTENT TYPE |
|---|
| Content type code |
|
| Content type term |
text |
| Source |
rdacontent |
| 337 ## - MEDIA TYPE |
|---|
| Materials specified |
|
| -- |
0 |
| Media type code |
|
| Media type term |
unmediated |
| Source |
rdamedia |
| 338 ## - CARRIER TYPE |
|---|
| Materials specified |
|
| -- |
0 |
| Carrier type code |
|
| Carrier type term |
volume |
| Source |
rdacarrier |
| 340 ## - PHYSICAL MEDIUM |
|---|
| Source |
|
| -- |
0 |
| Color content |
|
| Font size |
|
| 344 ## - SOUND CHARACTERISTICS |
|---|
| Source |
|
| -- |
|
| Type of recording |
0 |
| Recording medium |
|
| 347 ## - DIGITAL FILE CHARACTERISTICS |
|---|
| Source |
|
| -- |
|
| File type |
0 |
| 362 ## - DATES OF PUBLICATION AND/OR SEQUENTIAL DESIGNATION |
|---|
| Dates of publication and/or sequential designation |
|
| -- |
|
| -- |
|
| 385 ## - AUDIENCE CHARACTERISTICS |
|---|
| Demographic group term |
|
| -- |
|
| Audience term |
2 |
| 410 ## - SERIES STATEMENT/ADDED ENTRY--CORPORATE NAME [OBSOLETE, CAN/MARC], [LOCAL, USA] |
|---|
| Title of a work |
|
| -- |
|
| Subordinate unit |
|
| Corporate name or jurisdiction name as entry element |
|
| Volume number/sequential designation |
|
| 440 ## - SERIES STATEMENT/ADDED ENTRY--TITLE |
|---|
| Name of part/section of a work |
|
| -- |
|
| Title |
|
| International Standard Serial Number |
|
| Volume/sequential designation |
|
| 490 ## - SERIES STATEMENT |
|---|
| Series statement |
|
| -- |
|
| International Standard Serial Number |
|
| Volume/sequential designation |
|
| 500 ## - GENERAL NOTE |
|---|
| General note |
|
| -- |
Undergraduate Thesis : (Bachelor of Science in Computer Engineering) - Pamantasan ng Lungsod ng Maynila, 2024. |
| -- |
|
| -- |
|
| -- |
56 |
| 504 ## - BIBLIOGRAPHY, ETC. NOTE |
|---|
| Bibliography, etc. note |
|
| -- |
|
| -- |
|
| 505 ## - FORMATTED CONTENTS NOTE |
|---|
| Formatted contents note |
|
| -- |
|
| -- |
|
| Title |
|
| Miscellaneous information |
|
| Statement of responsibility |
|
| 506 ## - RESTRICTIONS ON ACCESS NOTE |
|---|
| Terms governing access |
|
| -- |
5 |
| 510 ## - CITATION/REFERENCES NOTE |
|---|
| Name of source |
|
| -- |
|
| International Standard Serial Number |
|
| 520 ## - SUMMARY, ETC. |
|---|
| Expansion of summary note |
|
| -- |
|
| Assigning source |
|
| Summary, etc. |
ABSTRACT: STATEMENT OF THE PROBLEM: Air travel provides fast and convenient global connectivity, but the mishandling of luggage remains a significant concern. In 2022, 26 million bags were mishandled, intensified by the complexities of connecting flights. Such issues often stem from human errors in bustling airports or aircraft constraints, leading to passenger anxiety and potential security issues. As technology advances, integrating IoT into airport system emerges as a solution. The PortPulse project utilizes IoT to enhance luggage handling and tracking, aiming to reduce lost luggae incidents and enhance the travel experience. It offers a cloud-based real-time baggage tracking, allowing both travellers to stay updated and authorities to ensure security and efficiency in airport operations. Thus, as we proceed into the design of portPulse, critical questions arise: 1. How can PortPulse utilize IoT technology and Cloud Computing Technology to establish an efficient real-time tracking system, addressing the prevalent challenge of mishandled luggage, particularly during connecting flight transfers? 2. How can the infrastructure be designed toi seamlessly integrate the PortPulse system, ensuring travellers have real-time insights into the whereabouts and status of their luggae, thus providing them with the necessary information and reassurance? 3. What factors contribute to the overall satisfaction of users with the PortPulse system and how can these insights be utilized to enhance the user experience and further optimize luggage tracking efficiency? RESEARCH METHODOLOGY: The procedure outlines the systematic development of PortPulse, a luggage tracking system. Both the hardware and software were planned, built, tested, and analyzed. The objective was to enhance passenger satisfaction by providing real-time luggage tracking, user-friendly interfaces and smoother luggage handling. Various scenarios were tested, and the system was deployed gradually, with continuous improvements based on user feedback to ensure effectiveness in airport environments. For the hardware component, a Microcontroller (Wemos ESP8266 (DI Mini) and GPS technology (Neo 6m) were utilized in a compact keychain-like device. The system was released incrementally, with ongoing enhancements for improved usability. The software development followed a systematic approach, focusing on user requirements, system robustness, and intuitive interface design. Close collaboration between hardware and software teams ensured seamless integration and adherence to security standards. User testing, compliance checks, and pilot deployments at select airports contributed to continuous refinement based on user input, establishing PortPulse as a reliable luggage tracking solution. `Data gathering involves simulating and testing the device around Intramuros, Manila and the use of Google Forms to gather feedback on passenger satisfaction, luggage issues, and interest in PortPulse. Surveys were refined based on trial runs and shared via social media platforms like Facebook and Messenger. System integration into airline infrastructures emphasized modular architecture and standardized communication protocols to ensure compatibility. Security measures such as access controls and encryption were prioritized to safeguard data integrity and privacy. SUMMARY OF FINDINGS: The primary aim of this study is to develop an integrated system that will enhance the experience of airline customers by reducing the possibility of luggage loss. The researchers technology, PortPulse, combines hardware that transmit the data (coordinates of the luggage pieces) from a satellite to the database with software designed to allow customers to follow their luggage in real-time. As a result, the cucial issues raised in Chapter I of the research served as the foundation for the success measures. This is a concise summary of the findings that highlights important information: From a functional perspective, PortPulse operates as a cohesive unit where the software interface serves as the primnary point of interaction for end-users while the hardware device delivers the information of the luggage coordinates to the database. Additionally, the software interface provides an easy-to-use monitoring tool that lets passengers know exactly where their luggage is at all times, giving them a sense of security and peace of mind when they're travelling. Moreso, the accuracy, usability, and user satisfaction of the PortPulse system were all considered during testing and validated accordingly in order to confirm the system's effectiveness. In the simulation, comparative results against Google Maps showed that PortPulse outperformed in terms of consistency and regularly reported position accuracy. Although it was noted that complete accuracy cannot be determined from this, it shows the efficacy of the system. Furthermore, the results of surveys leans towards the consensus that the system has an easy-to-use interface that is accessible to all users, regardless of their level of technological proficiency. All things considered, the implementation of PortPulse shows that the research and technical efforts undertaken in this project were successful in developing an integrated system that tracks and reports location instantaneously. By developing a device with a GPS tracker that sends real-time coordinates to the database, the researchers were able to combine IoT with cloud computing. PortPulse is sufficiently scalable that it has the potential to be integrated into actual airline systems, even through the technology was only evaluated in simulations. Finally evaluations of its usability, user flow, and user satisfaction demonstrate its potential to improve user experience by lowering the possibility of misplaced or improperly handled luggage. CONCLUSION: In summary, the research findings suggest that the PortPulse system has promising potential for improving luggage tracking in air transportation. Although it has some limits, like focusing only on checked-in luggage and testing in simulated environments, it shows potential for accurately tracking luggage in real-time. Even though there are small changes in GPS data, the PortPulse tracker stays pretty steady in showing where luggage is. Also, its easy-to-use interface and connection to cloud technology could help passengers keep track of their luggage better, possibly reducing lost or mishandled bags and making travel experiences better. But, more testing and improvements might be needed to fix any issues and make it work even better. RECOMMENDATIONS: Based on the finaly analysis of the result and discussion, the following are the recommendations to further enhance PortPulse for future research: . QR C ode Technology: Adding QR codes alongside device IDs can improve security and streamline processes. This was tested on the server by the researchers but not deployed due to time and compatibility issues. It could enhance security and user experience. . Better GPS Tracker: The current GPS module, Neo 6m, is accurate but lacks communication with cellular towers. Considering other GPS modules with this feature could improve reliability, especially as the system scales. . Battery-Powered Trackers: Exploring battery-powered GPS trackers would add flexibility. Currently, PortPulse device relies on an external power source due to microcontroller limitations, but redesigning for battery power could offer convenience. . Data filtering and Validation: Implementing filters and improving data validation in the web application can enhance usability for operators. This includes filtering by flight and adjusting charts and tables for better viewing . . Track Feature Search: Simplifying the luggage tracking process for passengers by adding a search component can improve user experience. . Alert Notifications: Incorporating alert notifications, such as SMS or email, when luggage passes certain checkpoints, can increase passenger awareness of luggage location. . API Structures: Optimizing the Google API calls in the web application can improve the real-time tracking feature. Adjusting intervals between calls could lead to better performance although it may incur additional costs. |
| Uniform Resource Identifier |
<a href=""></a> |
| 521 ## - TARGET AUDIENCE NOTE |
|---|
| Target audience note |
|
| -- |
|
| Source |
|
| 533 ## - REPRODUCTION NOTE |
|---|
| Physical description of reproduction |
|
| -- |
|
| Type of reproduction |
|
| Date of reproduction |
|
| Place of reproduction |
|
| Note about reproduction |
|
| Agency responsible for reproduction |
|
| 540 ## - TERMS GOVERNING USE AND REPRODUCTION NOTE |
|---|
| Authorization |
|
| -- |
|
| Terms governing use and reproduction |
5 |
| 542 ## - INFORMATION RELATING TO COPYRIGHT STATUS |
|---|
| Copyright date |
|
| -- |
|
| Copyright statement |
|
| 546 ## - LANGUAGE NOTE |
|---|
| Language note |
|
| -- |
|
| Information code or alphabet |
|
| 583 ## - ACTION NOTE |
|---|
| Institution to which field applies |
|
| -- |
|
| Action agent |
|
| Time/date of action |
|
| Action |
|
| Action identification |
|
| 590 ## - LOCAL NOTE (RLIN) |
|---|
| Local note |
|
| -- |
|
| Provenance (VM) [OBSOLETE] |
|
| 600 ## - SUBJECT ADDED ENTRY--PERSONAL NAME |
|---|
| Numeration |
|
| -- |
|
| Form subdivision |
|
| Title of a work |
|
| Titles and other words associated with a name |
2 |
| Fuller form of name |
|
| Personal name |
|
| General subdivision |
0 |
| Geographic subdivision |
|
| Dates associated with a name |
|
| Chronological subdivision |
|
| 610 ## - SUBJECT ADDED ENTRY--CORPORATE NAME |
|---|
| Subordinate unit |
|
| -- |
|
| Form subdivision |
|
| Title of a work |
2 |
| General subdivision |
|
| Corporate name or jurisdiction name as entry element |
|
| Form subheading |
0 |
| Name of part/section of a work |
|
| Geographic subdivision |
|
| Date of meeting or treaty signing |
6 |
| Chronological subdivision |
|
| 611 ## - SUBJECT ADDED ENTRY--MEETING NAME |
|---|
| Meeting name or jurisdiction name as entry element |
|
| -- |
|
| Date of meeting or treaty signing |
|
| Number of part/section/meeting |
2 |
| Location of meeting |
0 |
| Form subdivision |
|
| 630 ## - SUBJECT ADDED ENTRY--UNIFORM TITLE |
|---|
| General subdivision |
|
| -- |
|
| Uniform title |
|
| Date of treaty signing |
|
| Name of part/section of a work |
20 |
| Form subdivision |
|
| 648 ## - SUBJECT ADDED ENTRY--CHRONOLOGICAL TERM |
|---|
| Source of heading or term |
|
| -- |
|
| Chronological term |
|
| 650 ## - SUBJECT ADDED ENTRY--TOPICAL TERM |
|---|
| General subdivision |
|
| -- |
|
| Topical term or geographic name entry element |
|
| Active dates |
|
| Topical term following geographic name entry element |
|
| Geographic subdivision |
|
| Chronological subdivision |
20 |
| Form subdivision |
|
| 651 ## - SUBJECT ADDED ENTRY--GEOGRAPHIC NAME |
|---|
| General subdivision |
|
| -- |
|
| Geographic name |
|
| Chronological subdivision |
20 |
| Form subdivision |
|
| Geographic subdivision |
|
| 655 ## - INDEX TERM--GENRE/FORM |
|---|
| Authority record control number or standard number |
|
| -- |
|
| Genre/form data or focus term |
|
| Chronological subdivision |
2 |
| Geographic subdivision |
|
| 700 ## - ADDED ENTRY--PERSONAL NAME |
|---|
| Relationship information |
|
| -- |
|
| Title of a work |
|
| Titles and other words associated with a name |
|
| Numeration |
|
| Version |
1 |
| Fuller form of name |
|
| Date of a work |
|
| Form subheading |
40 |
| Name of part/section of a work |
|
| Dates associated with a name |
|
| Relator term |
|
| Personal name |
|
| Language of a work |
|
| Number of part/section of a work |
6 |
| 710 ## - ADDED ENTRY--CORPORATE NAME |
|---|
| Subordinate unit |
|
| -- |
|
| Title of a work |
|
| Location of meeting |
|
| Relator term |
|
| Date of a work |
|
| Form subheading |
40 |
| Name of part/section of a work |
|
| Date of meeting or treaty signing |
5 |
| Language of a work |
|
| Number of part/section/meeting |
6 |
| Corporate name or jurisdiction name as entry element |
|
| 711 ## - ADDED ENTRY--MEETING NAME |
|---|
| Meeting name or jurisdiction name as entry element |
|
| -- |
|
| Date of meeting or treaty signing |
|
| Number (BK CF MP MU SE VM MX) [OBSOLETE] |
|
| Number of part/section/meeting |
|
| Title of a work |
|
| Location of meeting |
|
| 730 ## - ADDED ENTRY--UNIFORM TITLE |
|---|
| Version |
|
| -- |
|
| Uniform title |
|
| Date of treaty signing |
|
| Number of part/section of a work |
|
| Name of part/section of a work |
|
| Date of a work |
|
| Language of a work |
|
| Form subheading |
|
| 740 ## - ADDED ENTRY--UNCONTROLLED RELATED/ANALYTICAL TITLE |
|---|
| -- |
|
| -- |
|
| Uncontrolled related/analytical title |
|
| -- |
|
| -- |
|
| Number of part/section of a work |
|
| -- |
6 |
| 753 ## - SYSTEM DETAILS ACCESS TO COMPUTER FILES |
|---|
| Operating system |
|
| -- |
|
| Make and model of machine |
|
| 767 ## - TRANSLATION ENTRY |
|---|
| Title |
|
| -- |
|
| Record control number |
|
| 770 ## - SUPPLEMENT/SPECIAL ISSUE ENTRY |
|---|
| Title |
|
| -- |
|
| Record control number |
|
| International Standard Serial Number |
|
| 773 ## - HOST ITEM ENTRY |
|---|
| Main entry heading |
|
| -- |
|
| Place, publisher, and date of publication |
|
| Related parts |
|
| Material-specific details |
|
| Title |
|
| Edition |
|
| -- |
|
| Relationship information |
|
| Abbreviated title |
|
| 775 ## - OTHER EDITION ENTRY |
|---|
| Title |
|
| -- |
|
| Record control number |
|
| International Standard Serial Number |
|
| 776 ## - ADDITIONAL PHYSICAL FORM ENTRY |
|---|
| Uniform title |
|
| -- |
|
| Main entry heading |
|
| Place, publisher, and date of publication |
|
| Edition |
|
| International Standard Book Number |
|
| Relationship information |
|
| Title |
|
| International Standard Serial Number |
|
| Physical description |
|
| Qualifying information |
|
| Record control number |
|
| 780 ## - PRECEDING ENTRY |
|---|
| International Standard Serial Number |
|
| -- |
|
| Main entry heading |
|
| Related parts |
|
| Title |
|
| Record control number |
|
| 785 ## - SUCCEEDING ENTRY |
|---|
| Title |
|
| -- |
|
| Record control number |
|
| Main entry heading |
|
| International Standard Serial Number |
|
| 787 ## - OTHER RELATIONSHIP ENTRY |
|---|
| International Standard Serial Number |
|
| -- |
|
| Place, publisher, and date of publication |
|
| Related parts |
|
| Relationship information |
|
| Title |
|
| Record control number |
|
| 800 ## - SERIES ADDED ENTRY--PERSONAL NAME |
|---|
| Personal name |
|
| -- |
|
| Dates associated with a name |
|
| Language of a work |
|
| Date of a work |
|
| Title of a work |
0 |
| Fuller form of name |
|
| Volume/sequential designation |
|
| 810 ## - SERIES ADDED ENTRY--CORPORATE NAME |
|---|
| Corporate name or jurisdiction name as entry element |
|
| -- |
|
| Subordinate unit |
|
| Date of a work |
|
| Title of a work |
|
| -- |
|
| Volume/sequential designation |
|
| 830 ## - SERIES ADDED ENTRY--UNIFORM TITLE |
|---|
| International Standard Serial Number |
|
| -- |
|
| Uniform title |
|
| Name of part/section of a work |
|
| Number of part/section of a work |
|
| Language of a work |
0 |
| Volume/sequential designation |
|
| 942 ## - ADDED ENTRY ELEMENTS |
|---|
| Institution code [OBSOLETE] |
|
| -- |
lcc |
| Item type |
Book |