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.

Browse configuration, normalizedDates

edited September 2013 in Troubleshooting
Does the normalizedDates facet only work with single-element elements (as the attribute facet)? I don't get any results when applying it on an attribute with sub-elements.

Comments

  • It should work on DateRange elements in containers as well as stand-alone.
  • edited September 2013
    My dateRange element is located two steps down (ie container.container.date-element) and I've tried both "container.sub-element" and "container.container.sub-element" in browse.conf without luck.
  • Don't do the three levels. The namespace for a container is flat no matter how deep sub-containers are nested. container.sub-element should work, container.container2.sub-element will not.

    Send me your profile and we'll take a look
  • Ok. I sent you the profile.
  • Tried to do this again today but can't figure it out. Any ideas?
  • Still haven't figured this out. As soon as I try with a single non nested element it works but when it is further down in the hierarchy it doesn't.
  • Did you ever figure this out? I'm struggling with the same problem 7 years later!

  • Sorry. I can't remember how it worked out then but it works now using 1.7. The element I'm using is nested a couple of containers down and all I do, as stated above, is setting the element_code to container.sub-element (leaving out the containers in between).

Sign In or Register to comment.