Milestone search issue

I may be misunderstanding the Milestone search, but I am trying to find all resources that have a specific liturgical date milestone.

For example, a search of {Milestone <ApostolicFathers = II Clement>} returns what I expect: all resources with data type "ApostolicFathers" and reference "II Clement".

So I would expect a search of {Milestone <CatholicCalendar = Advent 1 Sun A>} to return all resources with data type "CatholicCalendar" and reference "Advent 1 Sun A". However, this returns 0 results, despite having several resources with this reference such as "Catholic Lectionary".

Am I misunderstanding the Milestone search or a syntax issue? (I certainly wouldn't put either past me!)

As a side note, I am a bit confused about the references. In say the Catholic Lectionary, when I perform a right-click search on, say, the reference for the First Sunday of Advent, a search window with "<CatholicCalendar = Advent 1 Sun A>" pops up. (Notice Advent is spelled out in the reference.)

But in the same section, when I "copy location as wiki", i get "[[Advent, Week 1, Sunday, Year A >> logosres:cathlect;ref=CatholicCalendar.Adv_1_Sun_A]]" and looking at the reference, it now has "Adv" instead of "Advent". Why two different references?

Find more posts tagged with

Comments

Mark Barnes

But in the same section, when I "copy location as wiki", i get "[[Advent, Week 1, Sunday, Year A >> logosres:cathlect;ref=CatholicCalendar.Adv_1_Sun_A]]" and looking at the reference, it now has "Adv" instead of "Advent". Why two different references?

Lots of Logos referencing system have short and long versions, so that shouldn't matter.

It looks to me as though there's a resource or indexing problem with the lectionary, or more likely all lectionaries. A search for {Milestone <CatholicCalendar ~ Advent>} in all resources returns results from only the Roman Missal, which is a monograph. In other words, I don't think you're doing anything wrong, I think it's a bug.

MJ. Smith

https://community.logos.com/discussion/comment/688726#Comment_688726

The coding for liturgical dates is new. Lou was still working when L6 released so it currently works on very few resources.

There is clearly a bug

Louis St. Hilaire

https://community.logos.com/discussion/comment/688738#Comment_688738

We've pushed out a metadata update that should fix this. (You may need to restart the application and/or wait for the library catalog metadata to update.)

MJ. Smith

https://community.logos.com/discussion/comment/688751#Comment_688751

Thanks - that's what I call fast fixes.

Chris

https://community.logos.com/discussion/comment/688751#Comment_688751

Okay, thanks! My search for {Milestone <CatholicCalendar ~ Advent>} now yields results in the Catholic Lectionary. But that is the only resource that shows results! From MJ's screen shot, I see results from the Roman Missal (English) and Word of Life, both of which are resources in my library, but they are not showing up under this search for me.

A metadata update for the Catholic Lectionary fixed the search for datatype CatholicCalendar. Could my metadata be somehow corrupted/missing for other resources? Rebuilding just the index for the Roman Missal did not fix it.

This also prompts the question: When a Milestone search is made, is it that Logos is not actually searching the entire library of resources, just the resources that have been appropriately tagged in the metadata?

I played around with personal books here too. And when I use the CatholicCalendar datatype in those, they are correctly showing up under "Your Books" in the search.

Thanks for all the help!

Mark Barnes

https://community.logos.com/discussion/comment/688897#Comment_688897

When a Milestone search is made, is it that Logos is not actually searching the entire library of resources, just the resources that have been appropriately tagged in the metadata?

Each resource has a number of 'traits', which mark them as supporting particular datatypes. It seems as though someone forgot to mark the Catholic lectionary as requiring the relevant trait (which presumably is something like supports-catholic-calendar).

There's no obvious reason I can see why the Roman Missal isn't returning results for you. It's possible that an early metadata update was missed. Try hiding then unhiding the resource(s).

Chris

https://community.logos.com/discussion/comment/688937#Comment_688937

There's no obvious reason I can see why the Roman Missal isn't returning results for you. It's possible that an early metadata update was missed. Try hiding then unhiding the resource(s).

I tried this with the Roman Missal, and it now displays in the results. Thanks!

Each resource has a number of 'traits', which mark them as supporting particular datatypes.

When I go to the resource information page for resources like the Catholic Lectionary, the Roman Missal, and the Word of Life devotional mentioned above, I see that "Catholic Liturgical Calendar" is listed in the indexes section. I am guessing that this means that the datatype CatholicCalendar is present in those resources. I can easily enough hide/unhide those resources since my library is not terribly large.

However, it seems like a manual "trait" route of determining which resources to search for a given datatype is fraught with the possibility of an oversight in adding the trait to the metadata for the resource, like what apparently happened with the Catholic Lectionary. Especially when, at least for this particular datatype, the resource page already seems to know that "Catholic Liturgical Calendar" is an index and hence the resource would have the CatholicCalendar datatype present. Is there perhaps a way to have Logos look at that instead of a resource trait that may or may not be present in the metadata? Or is there way to have Logos programmatically go through each resource in the individual's library, identify the datatypes actually present in the resource, and then set the appropriate traits so the searches are returning all possible resources with the datatype and not just the ones that have the trait in the metadata?

Thanks again for all of the help!

Mark Barnes

https://community.logos.com/discussion/comment/688952#Comment_688952

When I go to the resource information page for resources like the Catholic Lectionary, the Roman Missal, and the Word of Life devotional mentioned above, I see that "Catholic Liturgical Calendar" is listed in the indexes section. I am guessing that this means that the datatype CatholicCalendar is present in those resources. I can easily enough hide/unhide those resources since my library is not terribly large.

Correct.

However, it seems like a manual "trait" route of determining which resources to search for a given datatype is fraught with the possibility of an oversight in adding the trait to the metadata for the resource, like what apparently happened with the Catholic Lectionary.

We don't really know how this process works inside Logos, whether traits are added manually or automatically, and what went wrong this time.

It's pretty rare to have metadata problems like the one you're experiencing, so I think the system is generally reliable. At least this way it can be fixed quickly, without needing a program update.

MJ. Smith

https://community.logos.com/discussion/comment/689058#Comment_689058

Chris, I don't know what went wrong for you but I didn't do any manual work. It just "happened". Sometimes it takes the forums to discover something went wrong on your particular installation.

Eli Evans (Logos)

https://community.logos.com/discussion/comment/689058#Comment_689058

We don't really know how this process works inside Logos, whether traits are added manually or automatically, and what went wrong this time.

Traits that can be added automatically are added by the compiler, and the rest are added manually when we enter the metadata. Now you know. [:)]

Mark Barnes

https://community.logos.com/discussion/comment/689079#Comment_689079

Traits that can be added automatically are added by the compiler, and the rest are added manually when we enter the metadata. Now you know.

Thanks Eli.