Understanding browsing facets to FILTER BY

carlosTF

Hi,

I'm trying to get may way around FILTER BY and facets, and I think it will help me to understand the following.
I copied

		type_facet = {
			type = fieldList,
			field = type_id,
			
			group_mode = none,

			label_singular = _("Object Type"),
			label_plural = _("Object Types"),
			description = _("Find objects according to the Types defined in your collection profile."),
		},

in ca_objects from app/conf/browse.conf and FILTER BY finally showed in the browse page.
My question is: where does type_id come from? The two elements I'm offered to filter by are Artworks and Works, the latter added by me in Object Type (object_types).
I just can't find type_id in the List/Vocabulary terms.
Shouldn't it be field = object_types or switched to element_code = object_types?
Confused. I've read all previous post on this matter and didn't help.
Thanks.

monica

You should read the documentation on browse.conf https://manual.collectiveaccess.org/providence/user/configuration/mainConfiguration/browse.html

The fieldlist browse type is for intrinsic fields that get a value from a list. The intrinsic field here is type_id on the table ca_objects. This field gets its values from the list object_types. It’s like any metadata element that is a list type… the code of the element doesn’t need to match the code of the list it gets its values from.

If the table you were creating a facet for was ca_collections, then type_id gets the values from collection_type list.

See intrinsic fields here https://manual.collectiveaccess.org/providence/user/dataModelling/primaryTables.html

carlosTF

monica Will do, thank you.

darrigan

Intrinsic fields are probably the first difficulty I encountered when I discovered CA! Because I couldn't find them in the metadata list (administration). Besides, I think that we could gain by having these metadata appear in the metadata list (without being editable nor deletable by the user of course), but just to show what they are with their codes.😉

behindicebergs

darrigan I agree completely with this statement!

seth

Ok we can do that. Create a GitHub issue please?

yelto

I've created issue #1801 with @darrigan 's proposal to keep the ball rolling. Thanks all.