Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Welcome to the CollectiveAccess support forum! Here the developers and community answer questions related to use of the software. Please include the following information in every new issue posted here:

  1. Version of the software that is used, along with browser and version

  2. If the issue pertains to Providence, Pawtucket or both

  3. What steps you’ve taken to try to resolve the issue

  4. Screenshots demonstrating the issue

  5. The relevant sections of your installation profile or configuration including the codes and settings defined for your local elements.


If your question pertains to data import or export, please also include:

  1. Data sample

  2. Your mapping


Answers may be delayed for posts that do not include sufficient information.

A profile for a collection related to money

edited May 2015 in Installation
I am preparing an installation profile for a collection which would comprise tokens, coins, paper money, archival records, manuscripts, prints, drawings and mechanical devices. Can you suggest any of the  existing profiles? I was tempted for a moment to try the LIDO profile by LIBIS but it seems rather sketchy at the moment. Theoretically it would be great to have all the data in LIDO from the start, but then every project using LIDO usually has to make their own LIDO flavour anyway, so maybe it's not such a great idea as it seems. So I guess any profile tested in production covering similar field would be useful.

Piotr

Comments

  • Hi Piotr,

    If you want to move away from LIDO then ISAD(G) may make sense.  Here's the profile: https://github.com/collectiveaccess/providence/blob/master/install/profiles/xml/isad_g.xml


  • Hello Julia,

    Many thanks for the suggestion. I will take a look at it.

  • I tried to install isad_g profile but did not succeed. Two errors were reported:
    • Invalid table specified for restriction r7 in element description
    • Invalid type ca_object_events for UI code standard_object_event_ui

    I am using Apache 2.4 but that should not be a problem I think.

  • Where did you get the profile? The one that Julia linked shouldn't have that reference anymore.
  • Sorry, my fault. Copied an old file lying around in my system.
  • Of, course. The right one installed without a problem.
  • edited February 19

    Hi all!

    Piotr Kopszak, do you think LIDO still looks rather sketchy? Why?

    What do you mean by "every project using LIDO usually has to make their own LIDO flavor anyway"?

    For museums starting from scratch (just some Excel spreadsheets for example) is there any reason not to use LIDO? Why? If not, what else?

    Does anyone know any remarkable museum using LIDO to describe their collection? I'm not sure if in this cases they describe with LIDO or just expose records after mapping.

    Being CA used so much by museums I wonder why there isn't a LIDO profile.

  • edited February 19

    You ask lots of questions :) To begin with valid minimal LIDO record is very, very small and in most situations not terribly useful.

  • That's because I'm full of doubts :) Basically I wan't to start off on the right foot. Using the right metadata schemes seems an important question while using CA.
    LIDO mandatory elements are just a few. My background is on software engineering but LIDO specification seems pretty extensive. Don't you think so?

    If not LIDO, what else? SPECTRUM, VRA Core, CDWA-Lite, museumdat... all seems deprecated after LIDO.

  • edited February 19
  • I don't want to discourage you but quite often it turns out that one size does not fit all. That's why there are so many application profiles shipped with CA. When you start seriously working with LIDO you will also need a profile for your content. And besides LIDO was only conceived as data migration format and was not meant as a data model for databases. I don't think LIDO deprecates anything. In my opinion the closer you get to CIDOC the better but it's a long shot.

Sign In or Register to comment.