Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    katiemartinez
    @katiemartinez
    Hello! It looks like the advanced search date field is pulling in records with broad date ranges (before 1999 will be included in a search for records from the 1970s). This isn't wrong, but I'm wondering if the date field could be a dropdown with decades like the normalizeddate filter?
    CollectiveAccess
    @collectiveaccess
    Yeah, it is doing what it is supposed to be doing. There is not currently an option to return a decades drop-down. It could be added, but it's a bit more complicated than you might think as you have to calculate what decades will return results.
    I guess you could also just configure the range of decades to show by hand, which would be a whole lot simpler to code at least.
    katiemartinez
    @katiemartinez
    We currently have the decades configured as a facet, does that mean it's not already calculated?
    CollectiveAccess
    @collectiveaccess
    The browse generates the list from the database with a query. We'd have to do that in the search forms as well. It's not a static calculation.
    katiemartinez
    @katiemartinez
    How do you recommend configuring the range of decades to show by hand?
    katiemartinez
    @katiemartinez
    I'm guessing you mean this would be new code -- so, moving on.. Thank you for letting us know. We might implement that in the future
    One other question, I'm wondering if our code is incorrect for displaying collection titles on object records because it's currently reading series > collection instead of the other way around -- ?
    <H4>{{{<unit relativeTo="ca_collections" delimiter=" ➔ "><l>^ca_collections.preferred_labels.name</l></unit><ifcount min="1" code="ca_collections"> ➔ </ifcount>}}}{{{ca_objects.preferred_labels.name}}}</H4>
    CollectiveAccess
    @collectiveaccess
    @katiemartinez It would be new code, yet. If you would be content with just setting start and end decades in the search form config, this it's not a lot of coding
    I assume collection and series are in a collection hierarchy?
    This is just going to pull each related collection (whatever it's type), stick and arrow between them and then output the object name
    for objects where both series and collection are directly linked it'll look like a hierarchy, but it isn't
    I'd check the cataloguing
    to be sure it's linked only to the most specific level of the hierarchy that makes sense
    and I'd replace the template with this:
    <H4>{{{<unit relativeTo="ca_collections" delimiter="; "><l>^ca_collections.hierarchy.preferredlabels.name%delimiter=➔_</l></unit><ifcount min="1" code="ca_collections"> ➔ </ifcount>}}}{{{ca_objects.preferred_labels.name}}}</H4>
    katiemartinez
    @katiemartinez
    Thanks so much for answering about this. Right now we have the objects related to the collection and the series so that they'll appear in both of those records below the metadata. See example in our development site: https://dev-digital.archives.newschool.edu/index.php/Detail/collections/KA000601
    If I use the hierarchy reference, the collection and collection > series will appear like so
    (I've added your code and my code above the other to show what is happening
    katiemartinez
    @katiemartinez
    Screen Shot 2021-10-11 at 4.19.54 PM.png
    (I have to remove the code from that link, so here is an image of the title format)
    Joshua Dull
    @dullj
    we've copied things to a new server, updated from 1.7.9 to 1.7.13 (db schema 158), and created a new theme. When use_identifiers_in_urls was set to 0 in the new theme, the URLs resolved correctly. When we changed the value to 1, entities without IDs no longer resolve and the URL encoding seems to not work. We did not have this issue in our past installation. I'm trying to track down where this is happening. Here are examples from the 2 servers old and new.
    Old install: https://digitalarchives.library.newschool.edu/index.php/Detail/people/id%3A4079
    New Install: https://dev-digital.archives.newschool.edu/index.php/Detail/entities/id%3A4079
    CollectiveAccess
    @collectiveaccess
    It might be broken. Please create a github issue for it and we'll take a look
    Joshua Dull
    @dullj
    Thanks will do. also, if you manually replace the '%3A' with the deencoded ':', the URL resolves
    CollectiveAccess
    @collectiveaccess
    We use this in our own projects, so I know it works. But it's the latest 1.8 code. Something may have gotten broken in 1.7
    Joshua Dull
    @dullj
    BTW, is 1.8 released or still in development?
    CollectiveAccess
    @collectiveaccess
    It's not released yet.
    Joshua Dull
    @dullj
    :thumbsup:
    EnekoSC
    @EnekoSC
    Hi everybody
    I am trying to use ElasticSearch to make some queries but I am getting all objects very time when I make a query.
    I've been reading documentation about Lucene also but I can't make it work. I am doing curl requests and in theory, with this sentence:
    curl -XGET 'http://localhost:9200/index1/_search?pretty=true&size=0&ca_objects.idno:50012312'
    I am filtering all objects and searching for the object with idno 50012312, but it returns all objects:
    image.png
    I have ElasticSearch 2.4.2 btw
    CollectiveAccess
    @collectiveaccess
    Are you really running 2.4.2? That a very old version.
    EnekoSC
    @EnekoSC
    i am scared about updating
    0nobody0
    @0nobody0
    testing out elasticsearch 7.15 with the providence and pawtucket develop branch - searches are working regardless of case in providence, but are case-sensitive in pawtucket. any help on making the pawtucket searches case insensitive is greatly appreciated - not sure if i am missing something in the conf files?
    1 reply
    Arunesh Varade
    @FairlyNewHere

    Hello,
    While importing my .xlsx file, I get an error 'Could not insert new record for object: Type must be specified'

    Tried to follow the pathway from below link (and a lot of other things), but the error still persists.
    https://collectiveaccess.org/support/index.php?p=/discussion/300898/import-error-could-not-insert-new-record-for-object-type-must-be-specified

    Kindly help as to how can I resolve this issue.

    teebark
    @teebark
    Show us the input.
    Arunesh Varade
    @FairlyNewHere
    image.png
    here you go
    CollectiveAccess
    @collectiveaccess
    Is column 8 pointing to data with valid type codes?
    And is there an object type with code "image"
    If the latter is true but the former is not, consider removing the column 8 mapping
    If the latter is not true, then remove that setting
    (or at least change it to a valid code)
    Bottom line is if the type codes don't exist you'll get the error you're getting
    Arunesh Varade
    @FairlyNewHere
    column 8 contains entry as "image" with the heading "Type"
    image.png
    What exactly is the valid code for it?
    CollectiveAccess
    @collectiveaccess
    The valid codes are whatever you've configured them to be.