Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
buechereielektrik:unapi:readme [2010-01-13 21:11] – Restructured document. rosenke | buechereielektrik:unapi:readme [2010-02-19 13:18] – Added information about format csv. strols | ||
---|---|---|---|
Line 11: | Line 11: | ||
=== Copyright === | === Copyright === | ||
- | Copyright 2008 2009 Goetz Hatop < | + | Copyright 2008 2009 Goetz Hatop < |
+ | original version can be found at | ||
+ | < | ||
Copyright 2009 2010 Stephan Rosenke < | Copyright 2009 2010 Stephan Rosenke < | ||
- | < | + | < |
=== License === | === License === | ||
Line 38: | Line 41: | ||
Edit unAPI.inc.php and set the user-defineable variables. Put the | Edit unAPI.inc.php and set the user-defineable variables. Put the | ||
script together with unAPI.php on a web server. Your records | script together with unAPI.php on a web server. Your records | ||
- | identified by PPN will then be available via unAPI, for example: | + | identified by PPN (PICA Production Number) |
- | < | + | unAPI, for example: < |
Try out unClient.php to see an example on how to fetch data delivered | Try out unClient.php to see an example on how to fetch data delivered | ||
Line 46: | Line 49: | ||
Copy them to a place on your web server where this can be accomplished. | Copy them to a place on your web server where this can be accomplished. | ||
This need not to be the same server where your unAPI.php script lives. | This need not to be the same server where your unAPI.php script lives. | ||
+ | |||
+ | unAPI.html is a simple form to submit PPNs and format to unAPI.php. | ||
+ | Copy it to the same directory as unAPI.php. | ||
For Bibsonomy.php and Coins.php see below. | For Bibsonomy.php and Coins.php see below. | ||
- | === What is Pica LBS === | + | === What is PICA LBS === |
- | OCLC/Pica distributes an integrated library system (ILS) named LBS | + | OCLC PICA distributes an integrated library system (ILS) named LBS |
which presents its data for human beings in a search interface called | which presents its data for human beings in a search interface called | ||
PSI. For automata, the bibliographic records are not really hidden | PSI. For automata, the bibliographic records are not really hidden | ||
Line 58: | Line 64: | ||
=== About this software | === About this software | ||
- | This PHP script | + | The PHP scripts |
comes with the LBS software to make bibliographic records available | comes with the LBS software to make bibliographic records available | ||
via an unAPI. It formats them as dublin core, in a XML format, BibTeX, | via an unAPI. It formats them as dublin core, in a XML format, BibTeX, | ||
- | JSON or some other formats (for a complete list query the unAPI without | + | JSON or some other formats (for a complete list, query the unAPI |
- | id- and format-parameter). MARC is missed from the list of available | + | without |
- | formats but could be added if someone can figure out how to map pica | + | available |
- | categories to marc records. | + | to map PICA categories to MARC records. |
- | The PICA records are retrieved as categories, and all the art of converting | + | The PICA records are retrieved as categories, and all the art of |
- | them to something like dublin core comes down to figure out the | + | converting |
- | meaning of the categories. | + | out the meaning of the categories. |
- | Internally, PICA+ categories and subfields of the record can be accessed | + | Internally, PICA+ categories and subfields of the record can be |
- | via a multi-dimensional hash (see functions getArray() and getArrayNice() in | + | accessed |
- | unAPI.inc.php). | + | getArrayNice() in unAPI.inc.php). |
- | Mappings in getArrayNice(), | + | Mappings in getArrayNice(), |
- | rules and must possibly be adapted. | + | cataloguing |
- | The program unAPI.php uses php curl - if available - to contact an OPAC | + | The program unAPI.php uses PHP curl - if available - to contact an OPAC |
server and retrieve a bibliographic record identified by a PPN, which | server and retrieve a bibliographic record identified by a PPN, which | ||
is the basic identifier in the PICA world. | is the basic identifier in the PICA world. | ||
Line 90: | Line 96: | ||
or application to enrich the records further. | or application to enrich the records further. | ||
For an example see < | For an example see < | ||
- | < | + | < |
+ | german). | ||
+ | |||
+ | === Format csv === | ||
+ | |||
+ | Following data can be found in the columns: | ||
+ | 1. PPN | ||
+ | 2. Author | ||
+ | 3. Editor | ||
+ | 4. Title | ||
+ | 5. Publisher' | ||
+ | 6. Year | ||
+ | 7. ISBN 10 | ||
+ | 8. ISBN 13 | ||
+ | 9. ISSN | ||
+ | 10. Deutsche Nationalbibliothek number | ||
+ | 11. OCLC number | ||
+ | 12. foreign data identification number | ||
+ | 13. Zentrale Zeitschriften Datenbank ID | ||
+ | 14. Class in Regensburger Verbundsklassifikation | ||
=== Bibsonomy.php and Coins.php === | === Bibsonomy.php and Coins.php === | ||
Line 99: | Line 124: | ||
Bibsonomy uses unAPI classes and functions to redirect an client to | Bibsonomy uses unAPI classes and functions to redirect an client to | ||
Bibsonomy supplying bibliographic data which is identified by a PPN. | Bibsonomy supplying bibliographic data which is identified by a PPN. | ||
- | In the OPAC web interface | + | In the OPAC web interface, only a link with the respective PPN must be |
+ | included. | ||
For example '<a href=" | For example '<a href=" | ||
Line 110: | Line 136: | ||
=== version of this document=== | === version of this document=== | ||
+ | 20100219: Added information about format csv. | ||
+ | 20100208: Added information for unAPI.html. | ||
+ | 20100127: Added link in copyright. | ||
+ | 20100126: Added explanation for PPN, some small corrections. | ||
20100113: Restructured document. | 20100113: Restructured document. | ||
- | |||
</ | </ | ||