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.

Old bundle naming (v1.7.8) in newly exported profile XML (v1.7.9)?

I've created a "git develop branch" instance twice:

  1. Updating from v1.7.8 installation to v1.7.9 code.
  2. New v1.7.9 installation with profile XML import from v1.7.8.

Something interesting I've noticed (if I'm not mistaken) is that the "old" XML has different bundle naming than the new one. Makes sense since the names seem to have been changed (looks nicer, btw).
But what puzzles me is that the terms in an exported profile XML differ, depending whether the setup was a fresh import, or a DB-update:

  • v1.7.9, but DB-update: old terms.
  • v1.7.9, but fresh import: new terms.

Random examples:

  • ca_attribute_set_item_description = ca_set_items.set_item_description
  • ca_attribute_tour_description = ca_tours.tour_description

Is this on purpose?
I would assume that each CA version exports the XML in its current flavor, regardless where the data came from?

Sign In or Register to comment.