|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (22)
View Page History{toc}
[Link to Collective access|http://www.collectiveaccess.org/tour]
h1. Introduction
CollectiveAccess is a highly configurable cataloguing tool and web-based application for museums, archives and digital collections. Available free of charge under the GPL open-source license. It supports:
- A variety of metadata standards - It supports most metadata standards through straightforward configuration. Out-of-the-box support is available for several popular standards including DublinCore, PBCore and SPECTRUM. The configuration library contains a variety of user-contributed configurations for common use-cases. You can use a configuration as-is, or as a starting point for a system tailored precisely to your needs.
- External data sources and repositories, as well as most popular media formats. Access the Library of Congress Subject Headings or Getty Art & Architecture Thesaurus (in English or Dutch) for descriptive cataloguing. Or use GoogleMaps, GoogleEarth or GeoNames for geospatial cataloguing. CollectiveAccess can also integrate with external digital repository systems such as Fedora and IRODS.
- A variety of metadata standards - It supports most metadata standards through straightforward configuration. Out-of-the-box support is available for several popular standards including DublinCore, PBCore and SPECTRUM. The configuration library contains a variety of user-contributed configurations for common use-cases. You can use a configuration as-is, or as a starting point for a system tailored precisely to your needs.
- External data sources and repositories, as well as most popular media formats. Access the Library of Congress Subject Headings or Getty Art & Architecture Thesaurus (in English or Dutch) for descriptive cataloguing. Or use GoogleMaps, GoogleEarth or GeoNames for geospatial cataloguing. CollectiveAccess can also integrate with external digital repository systems such as Fedora and IRODS.
- site: [http://www.collectiveaccess.org/]
- users: [http://collectiveaccess.org/about/users]
- tour: [http://www.collectiveaccess.org/tour]
- code: [http://collectiveaccess.org/support/developers]
- developer: Whirl-i-Gig
- PHP, 5M LOC (some part may be cruft, eg ID3 parsers for all sorts of formats)
- documentation: Complete, EN
- license: GNU GPL v.2
- Web based
- (formerly known as OpenCollection)
- Can act as both OAI-PMH client and server
- scope: Collection Management, Information retrieval services, Exhibition Management...
- the same backend (Providence) can be used by a native frontend (Pawtucket), but also custom frontends (eg Omeka)
- "a full-featured collections management and online access application for museums, archives and digital collections. It is designed to handle large, heterogeneous collections that have complex cataloguing requirements and require support for a variety of metadata standards and media formats."
- suports various metadata sets, eg DC, CDWA light, PBcore, EBUcore, VRAcore, SPECTRUM?, LIDO (started), CRM (discussed)...
- highly configurable: supports most metadata standards through straightforward configuration. The configuration library contains a variety of user-contributed configurations for common use-cases. You can use a configuration as-is, or as a starting point for a system tailored precisely to your needs.
- External data sources and repositories, as well as most popular media formats.
- Access the Library of Congress Subject Headings or Getty Art & Architecture Thesaurus (in English or Dutch) for descriptive cataloguing.
- use GoogleMaps, GoogleEarth or GeoNames for geospatial cataloguing.
- integrate with external digital repository systems such as Fedora and IRODS.
- users: [http://collectiveaccess.org/about/users]
- tour: [http://www.collectiveaccess.org/tour]
- code: [http://collectiveaccess.org/support/developers]
- developer: Whirl-i-Gig
- PHP, 5M LOC (some part may be cruft, eg ID3 parsers for all sorts of formats)
- documentation: Complete, EN
- license: GNU GPL v.2
- Web based
- (formerly known as OpenCollection)
- Can act as both OAI-PMH client and server
- scope: Collection Management, Information retrieval services, Exhibition Management...
- the same backend (Providence) can be used by a native frontend (Pawtucket), but also custom frontends (eg Omeka)
- "a full-featured collections management and online access application for museums, archives and digital collections. It is designed to handle large, heterogeneous collections that have complex cataloguing requirements and require support for a variety of metadata standards and media formats."
- suports various metadata sets, eg DC, CDWA light, PBcore, EBUcore, VRAcore, SPECTRUM?, LIDO (started), CRM (discussed)...
- highly configurable: supports most metadata standards through straightforward configuration. The configuration library contains a variety of user-contributed configurations for common use-cases. You can use a configuration as-is, or as a starting point for a system tailored precisely to your needs.
- External data sources and repositories, as well as most popular media formats.
- Access the Library of Congress Subject Headings or Getty Art & Architecture Thesaurus (in English or Dutch) for descriptive cataloguing.
- use GoogleMaps, GoogleEarth or GeoNames for geospatial cataloguing.
- integrate with external digital repository systems such as Fedora and IRODS.
- In addition to multilingual cataloguing facilities, it allows publication of this data in the languages of your choice.
h1. Screenshots
h2. LIDO profile
[mailto:Roxanne.Wyns@libis.kuleuven.be], 21 February 2014: [http://www.collectiveaccess.org/support/forum/index.php?p=/discussion/comment/980]
[mailto:Roxanne.Wyns@libis.kuleuven.be], 21 February 2014: [http://www.collectiveaccess.org/support/forum/index.php?p=/discussion/comment/980]
Here are provided few screen shots from museums' collection spaces, created with Collective Access.
LIBIS created a [LIDO profile|http://www.collectiveaccess.org/support/forum/uploads/FileUpload/ff/33c76ee3c5c52f4d6e78ceef97aff0.zip] in the framework of an European ICT-PSP project called Europeana Inside.
h2. Parrish Collection
In this project LIBIS is using CollectiveAccess as our ECK local repository. ECK stands for Europeana Connection Kit, a tool for managing and sending data to Europeana according to the required Europeana protocols (EDM format, OAI-PMH or SWORD protocol). Within Europeana Inside it was agreed by the partners (mainly coming from the museum domain) that the intermediate format before going to the Europeana Data Model (EDM) would be LIDO. LIBIS is providing content form the Library domain, so we are using MARC, but because we also worked on a LIDO implementation.
[http://parrishart.org/default.asp]
The ECK is still a work in progress and we'll share more about this later. You can find the LIDO profile attached. I've been involved in the the Athena project where the standard was initialized and know it quite well, but the profile might need some review since it was my first CA installation profile and now with the interstitial records possible in CA1.4 it might be possible to refine it further.
12 August 2014: It needs an update, first of all since this was my first trial at creating a CollectiveAccess installation profile and secondly because the new release of 1.4 provides new functionalities, such as:
- inclusion of relationships in container fields
- possibility to create metadata on top of a relationship (called interstitial metadata, used when you want to catalog metadata about a relationship between two records on the relationship.). This is for example very suitable to define the actor role in an ca_objects_x_entities relationship since the role of an actor can change according the object.
- inclusion of relationships in container fields
- possibility to create metadata on top of a relationship (called interstitial metadata, used when you want to catalog metadata about a relationship between two records on the relationship.). This is for example very suitable to define the actor role in an ca_objects_x_entities relationship since the role of an actor can change according the object.
- CollectiveAccess relationships: http://docs.collectiveaccess.org/wiki/Relationships
- installation profiles and interstitial metadata: http://docs.collectiveaccess.org/wiki/Cookbook_Chapter_2:_Installation_Profiles
- installation profiles and interstitial metadata: http://docs.collectiveaccess.org/wiki/Cookbook_Chapter_2:_Installation_Profiles
The people from CollectiveAccess are interested in creating a CIDOC CRM profile.
h1. Screenshots
!CollectiveAccess_scrY.png|border=1!
Here are provided few screen shots from museums' collection spaces, created with Collective Access.
h2. Parrish Collection
[http://parrishart.org/default.asp]
!CollectiveAccess_scrY.png!
!CollectiveAccess_scrZ.png!
[http://parrishart.org/default.asp]
!CollectiveAccess_scrY.png!
!CollectiveAccess_scrZ.png!
!CollectiveAccess_scrZ.png|border=1!
h2. Royal Museum for Central Africa
!CollectiveAccess_scrX..png!
!CollectiveAccess_scrX..png|border=1!