Refine
Keywords
- Koha (7)
- Kulturerbe (7)
- Lokales Bibliothekssystem (7)
- Open Source (7)
- Bibliotheksinformationssystem (6)
- Thesaurus (6)
- Inhaltserschließung (5)
- Metadaten (5)
- cultural heritage (5)
- BAM-Portal (4)
Language
- English (37) (remove)
Has Fulltext
- yes (37)
Summary:
- RDF is a simple, graph-based data model for metadata on the web
- RDF has an XML syntax for:
- Exchanging RDF Models
- Embedding RDF Models into web pages
- Advantages over XML
- Data model is agnostic to syntactic variations
- Information from different models and locations can easily be linked
- Some important operations are trivial (i.e. merging two models)
- RDF Schema defines special resources and predicates for defining vocabularies
- Vokabular: Class, SubClassOf, domain, range
- Implicit information can be derived using simple derivation rules
- There is no clear separation between model and schema, schema elements can be part of an RDF model
BAM, the joint portal for Libraries, Archives and Museums in Germany, considers itself to be a digital memory institution. Currently the portal holds more than 40 million records from a wide range of cultural institutions, some 37 million data sets from six libraries or union catalogs, 2.9 million data sets from eleven archives, 300.000 data sets from twenty museums and 800.000 data sets from other institutions.
These significant differences in numbers of data sets are not only due to the size of the holdings of the participating institutions but also to “cultural differences” between libraries, archives, and museums in creating records and collaborating in union catalogs.
The paper describes those differences from the perspective of the BSZ, the hosting organization of BAM, and a major contributor to BAM, the Foundation Prussian Cultural Heritage (Stiftung Preußischer Kulturbesitz), Berlin. The point of view is specific for the situation in Germany and might differ from the situation in other countries. There are certainly other important issues that are not mentioned here as we chose to take a perspective specific for BAM.
Same same, but different? Challenges and solutions in the opening process of the GND authority control for cultural institutions.
The growing online presence of cultural heritage institutions such as museums, archives, libraries and other research institutions requires efficient ways to interlink the collections of our cultural treasures in web portals like Europeana or the German Digital Library (DDB). One precondition for interlinking datasets is the shared use of authority files and controlled vocabularies. The Integrated Authority File (GND) is a widely recognized vocabulary for description and information retrieval in German speaking library communities. It is a tool to guarantee true disambiguation of persons, corporations, geographica, subject headings, works etc. being referred to in all media types. Published as linked open data, the GND fosters semantic interoperability and re-use of data. Objects kept in different collections can be retrieved, and cross-disciplinary research is facilitated. However, authority control for the Semantic Web goes beyond the needs of librarians. In order to open the GND for interdisciplinary use, it needs to be adapted and actively transformed by the communities.
The opening process of the GND is accompanied by the project "GND for cultural data" (GND4C) funded by the German Research Foundation (DFG). Together with the German National Library and the DDB, four project partners of the museum, archive and cultural heritage domain define their specific needs on the organisational structure, the data model and application profiles, the technical infrastructure and the community network beyond the library community. We like to focus on the challenge how to create an environment for true cross-domain authority control beyond shared vocabularies.
How to keep the bugs out
(2018)
As a community we have established a multi-step development process that requires a lot of testing, both human and automated, for patches to make their way into Koha. This can look overly complicated and time consuming from the outside, but makes a lot of sense if you take a closer look. This presentation will explain how the process works, the purpose of the various steps, what testers and QA are looking out for and how it comes all together in the release of a new Koha version.
Part 1: Community
- What is BSZ?
- BSZ
- Koha Installations
- History
- HLT
- Koha - the name
- International Community
- Communication
Part 2: Development
- Release Cycle
- Release Team
- Development Workflow
- Development
- Releases
- Highlights
- Release
- In progress
- Development
- Tools
- Ways to help out
- How to get code into Koha
- Links
After moving to Germany nearly two years ago, I
discovered that the German library landscape, which is based on centralised
union catalogues, was quite different to what I was used to in the UK.
This presentation will look at the setup of the union catalogues
(Verbundsystem), introduce how libraries in Germany use centralised
cataloguing to manage their data and explore what that means for libraries
working with Koha.
Since several years it has been observed that information offered by different know-ledge producing institutions on the internet is more and more interlinked. This tendency will increase, because the fragmented information offers on the internet make the retrieval of information difficult or even impossible. At the same time the quantity of information offered on the internet grows exponentially in Europe – and elsewhere - due to many digitization projects. Inasfar as funding institutions base the acceptance of projects on the observation of certain documentation standards the knowledge created will be retrievable and will remain so for a long time. Otherwise the retrieval of information will become a matter of chance due to the limits of fragmented, knowledge producing social groups.