Recently I had a pretty exciting discussion with one of our users, John who ended up asking me to google “the well-behaved document“, which I did, doing so with Dublin Core* and DCMI* as well:
A well-behaved document is an electronic document that is both user friendly and library friendly.
As for the PaperC.com books they filed the following under “User friendly”:
- reading software is readily available (check).
- it is in an open format and does not depend on proprietary (paid) software for display, styles and multimedia content (check)
- searchable (check),
- has bookmarks (check)
- an interactive table of contents (check check check)
- Except for copyrighted material it should not be password protected (check)
- print it out (no)
- and to copy/paste portions of the text (check)
- add bookmarks and comments of his own (check)
That’s 9 out of 10 and as for the printing we’ll implement a third party-service if need is.
Once we opened up fully, there will be even more:
- add links, videos and other resources
- regroup content in an own document within the platform
- implement material in your website or blog via the document API
- use documents in multiple versions collaborative within the “document history”
and many more things. We hope you like it!
The well-behaved document provides benefits for librarians and libraries, too:
Library friendly
is a document that has useful embedded metadata which librarians, digital asset managers and individuals can exploit to classify a document with little or no manual intervention, that is searchable and which can easily be indexed for full-text searching across a collection of documents.
University and public libraries prefer to keep the metadata of all their documents in separate catalogues or data bases for reasons of integrity and maintainability, but since one does not exclude the other, embedding the same metadata or a selection thereof also directly into a digital resource, automatically makes this data available to third parties who download or otherwise obtain access to such resources which they may want to preserve locally in their own knowledge base and/or to consult offline. Notation in attribute/literal pairs is probably adequate for most private or local repositories.”
There is some work to do but we’ll keep all this in mind.
Thank you John for your invaluable feedback and support,
Katja
*The Dublin Core set of standard meta terms or a basic subset thereof in combination with appropriate software is probably the best option to ensure that meta data is applied in a consistent manner and therefore has a better chance to be useful to librarians, content managers and individual users worldwide. They are already in use in many university and national libraries and they support refinements and namespaces (vocabularies) that can be adapted to the needs of organizations and user groups.
http://dublincore.org/workshops/ popularized the idea of “core meta data” for simple and generic resource descriptions. The fifteen-element “Dublin Core” achieved wide dissemination as part of theOpen Archives Initiative Protocol for Metadata Harvesting (OAI-PMH). It is also the default format used by Adobe® Acrobat® in the display of PDF files.



