ckanext-facet_scheming

ckanext-facet_scheming provides functions and templates that have been specially developed to extend the search functionality in CKAN for custom schemas. It uses the fields defined in a scheming file to provide a set of tools to use these fields for scheming, and a way to include icons in their labels when displaying them.

Requirements

Warning
This extension needs custom GeoDCAT-AP ckanext-scheming extension to work.

facet_scheming is designed to provide templates and functions to be used by other extensions over it. It uses the fields defined in a scheming file to provide a set of tools to use those fields for scheming, and a way to include icons in its labels when displaying them.

Compatibility with core CKAN versions:

CKAN version	Compatible?
2.8 and earlier	not tested
2.9	yes
2.10	not yet

Suggested values:

"yes"
"not tested" - I can't think of a reason why it wouldn't work
"not yet" - there is an intention to get it working
"no"

Installation

To install ckanext-facet_scheming:

Activate your CKAN virtual environment, for example:

. /usr/lib/ckan/default/bin/activate

Clone the source and install it on the virtualenv

git clone https://github.com/dsanjurj/ckanext-facet_scheming.git
cd ckanext-facet_scheming
pip install -e .
pip install -r requirements.txt

Add facet_scheming to the ckan.plugins setting in your CKAN config file (by default the config file is located at /etc/ckan/default/ckan.ini).
Clear the index in solr:

ckan -c [route to your .ini ckan config file] search-index clear

Modify the schema file on Solr (schema or managed schema) to add the multivalued fields added in the scheming extension used for faceting. You can add any field defined in the schema file used in the ckanext-scheming extension that you want to use for faceting. You must define each field with these parameters:

type: string - to avoid split the text in tokens, each individually "faceted".
uninvertible: false - as recomended by solr´s documentation
docValues: true - to ease recovering faceted resources
indexed: true - to let ckan recover resources under this facet
stored: true - to let the value to be recovered by queries
multiValued: well... it depends on if it is a multivalued field (several values for one resource) or a regular field (just one value). Use "true" or "false" respectively.

By now iepnb extension are ready to use these multivalued fields. You have to add this configuration fragment to solr schema in order to use them:

<!-- IEPNB extra fields -->
  <field name="tag_uri" type="string" uninvertible="false" docValues="true" indexed="true" stored="true" multiValued="true"/>
  <field name="conforms_to" type="string" uninvertible="false" docValues="true" indexed="true" stored="true" multiValued="true"/>
  <field name="lineage_source" type="string" uninvertible="false" docValues="true" indexed="true" stored="true" multiValued="true"/>
  <field name="lineage_process_steps" type="string" uninvertible="false" docValues="true" indexed="true" stored="true" multiValued="true"/>
  <field name="reference" type="string" uninvertible="false" docValues="true" indexed="true" stored="true" multiValued="true"/>
  <field name="theme" type="string" uninvertible="false" docValues="true" indexed="true" stored="true" multiValued="true"/>
  <field name="theme_es" type="string" uninvertible="false" docValues="true" multiValued="true" indexed="true" stored="true"/>
  <field name="metadata_profile" type="string" uninvertible="false" docValues="true" multiValued="true" indexed="true" stored="true"/>
  <field name="resource_relation" type="string" uninvertible="false" docValues="true" indexed="true" stored="true" multiValued="true"/>

Note
You can ommit any field you're not going to use for faceting, but the best policy could be to add all values at the beginning.

Be sure to restart Solr after modify the schema.

Restart CKAN. For example if you've deployed CKAN with Apache on Ubuntu:

sudo service apache2 reload
Reindex solr index:

ckan -c [route to your .ini ckan config file] search-index rebuild

Sometimes solr can issue an error while reindexing. In that case I'd try to restart solr, delete index ("search-index clear"), restart solr, rebuild index, and restart solr again.

Ckan needs to "fix" multivalued fields to be able to recover values correctly for faceting, so this step must be done in order to use faceting with multivalued fields.

Helpers

facet_scheming provides a set of useful helpers to be used in templates

fscheming_default_facet_search_operator(): Returns the default facet search operator: AND/OR (string)
fscheming_decode_json( json_text ): Converts a JSON formatted text in a python object using ckan.common.json
fscheming_organization_name( id ): Returns the name of the organization given its id. Returns None if not found
fscheming_get_facet_label( facet ): Returns the label of a facet as defined in the scheming file
fscheming_get_facet_items_dict( facet, search_facets=None, limit=None, exclude_active=False, scheming_choices=None): Returns the list of unselected facet items (objects) for the given facet, sorted by the field indicated in the request. Arguments:
- facet -- the name of the facet to filter.
- search_facets -- dict with search facets. Taken from c.search_facets if not defined
- limit -- the max. number of facet items to return. Taken from c.search_facets_limits if not defined
- exclude_active -- only return unselected facets.
- scheming_choices -- scheming choices to use to get labels from values. If not provided takes display\_name field provided by Solr
fscheming_new_order_url(name, concept): Returns a url with the order parameter for the given facet and concept to use.
Based in the actual order it rotates ciclically from [no order]->[direct order]->[inverse order] for the given concept (name or count)
fscheming_schema_get_icons_dir(field): Gets the icons' directory for the given field. It can be obtained (in order of preference) from the icons_dir property for the given field in the scheming file, from the facet_scheming.icons_dir value given in CKAN configuration file, plus the name of the field, or from the directory named after the field name in images/icons dir.
fscheming_schema_get_default_icon(field): Gets the default icon for the given field, defined in the schemig file, o None if not defined.
fscheming_schema_icon(choice, dir=None): Search for the icon path for the especified choice beside the given dir (if any). If the scheming file include a icon setting for the choice, this is returned (beside the given dir). If not, it takes the last fragment of the value url for the icon name, and the next two fragments of the url as two steps from dir to the icon file.
It locates the file searching for svg, png, jpeg or gif extensions in all the public dirs of the ckan configured extensions. If the file could be located, it returns the relative url. If not, it returns None.
fscheming_get_choice_dic(field, value): Gets the choice item for the given value in field of the scheming file.

Templates

Also a set of useful templates and snippets are provided

fscheming_facet_list.html Extending ckan original facet list snippet, provides a way to show facet labels instead of values (which is what Solr provides), prepending an icon if provided. To call you must extend the template package/search.html.
fscheming_facet_search_operator Gives the control to select the operator used to combine facets.
multiple_choice_icon Display snippet to use instead the original multiple_choice snippet provided by the scheming extension. It adds an icon before the label of the value.
select_icon Display snippet to use instead the original select snippet provided by the scheming extension. It adds an icon before the label of the value.
multiple_select-icon Form snipet to use instead the original multiple_select to show icons in multiple options fileds when adding or editing a resource

Config settings

Config (.ini) file

There are not mandatory sets in the config file for this extension. You can use the following sets:

facet_scheming.facet_list: [list of fields]      # List of fields in scheming file to use to faceting. Use ckan defaults if not provided.
facet_scheming.default_facet_operator: [AND|OR]  # OR if not defined
facet_scheming.icons_dir: (dir)                  # images/icons if not defined

As an example for facet list, we could suggest:

facet_scheming.facet_list = "theme groups theme_es dcat_type owner_org res_format publisher_name publisher_type frequency tags tag_uri conforms_to spatial_uri"

The same custom fields for faceting can be used when browsing organizations and groups data:

facet_scheming.organization_custom_facets = true
facet_scheming.group_custom_facets = true

This two last settings are not mandatory. You can omit one or both (or set them to 'false'), and the default fields for faceting will be used instead.

Icons

Icons' location for each field option in the scheming file can be set in multiple ways:

You can set a root directory path for icons for each field using the "icons_dir" key in the scheming file.
If you don´t define this key, the directory path are guessed starting from the value provided for the "facet_scheming.icons_dir" parameter ("images/icons" by default if not provided) in CKAN config file, adding the name of the field (field_name) as a additional step to the path.

Having the root path for the icons used by the values for the options of a field, you must define where the icons for each option must be, or know where the extension will search for them by default

For each option you can use a "icon" setting to provide the last steps of the icon path (from the field icons´ root path defined before). This value may be just a file name, or include a path to add to the icon´s root directory (some_name.jpg or some_dir_name/some_name.jpg).
If you don't use this setting, a directory and file name are guessed from the option´s value:
- If the value is a url, the last two steps of the url are used to guess were the icon is. The first is added to the icons' dir path guessed or defined in the previous step as a subdirectory. The second are used to guess the icon's name, adding and testing "svg","png","jpg" or "gif" as possible extensions.
- If the value is not a url, it is taken as the name of the icon (testing the extensions named before) in the icons root directory for this field.

Icons files are tested for existence when using fscheming_schema_icon function to get them. If the file doesn't exist, the function returns None. Icons can be provided by any ckan extension, in its public directory.

You can set a default icon for a field using the default_icon setting in the scheming file. You can get it using fscheming_schema_get_default_icon function, and is your duty do decide when and where get and use it in a template.

Examples:

We have set facet\_scheming.icons\_dir: images/icons in .ini CKAN config file (or not set this parameter at all, because this is the default value)

Defining icons in a schema file:

- field_name: strange_field
...
  icons_dir: icons/for/strange/field
...
  choices:
  - value: http://some_domain.fake/level1/level2/strange_value
    label:
      en: Strange Value
      es: Valor Extraño
    description:
      en: ''
      es: 'Valor extraño para un campo extraño'
    icon: strange_value_icon.gif
    ...

Icons file for "strange_field" field will be searched in public/icons/for/strange/field directory in all CKAN extensions. Url will be icons/for/strange/field/strange_value_icon.gif if file was found in any extension.

The value provided in facet_scheming.icons_dir (images/icons) will NOT be used to compose the url, because you have provided icons_dir in the scheming file for this field.

Using icons not defined in the schema file:

- field_name: strange_field
...
  choices:
  - value: http://some_domain.fake/level1/level2/strange_value
    label:
      en: Strange Value
      es: Valor Extraño
    description:
      en: ''
      es: 'Valor extraño para un campo extraño'
    ...

Directory for icons will be taken from facet_scheming.icons_dir, bacause you not provide a

Url for this option will be images/icons/strange_field/level2/strange_value.[ext], beeing [ext] any extension in svg, png, jpg or gif (searched in this order).

Developer installation

To install ckanext-facet_scheming for development, activate your CKAN virtualenv and do:

git clone https://github.com/dsanjurj/ckanext-facet_scheming.git
cd ckanext-facet_scheming
python setup.py develop
pip install -r dev-requirements.txt

Tests

To run the tests, do:

pytest --ckan-ini=test.ini

Releasing a new version of ckanext-facet_scheming

If ckanext-facet_scheming should be available on PyPI you can follow these steps to publish a new version:

Update the version number in the setup.py file. See PEP 440 for how to choose version numbers.
Make sure you have the latest version of necessary packages:

pip install --upgrade setuptools wheel twine
Create a source and binary distributions of the new version:
```
python setup.py sdist bdist_wheel && twine check dist/*
```
Fix any errors you get.
Upload the source distribution to PyPI:
```
twine upload dist/*
```
Commit any outstanding changes:
```
git commit -a
git push
```
Tag the new release of the project on GitHub with the version number from the setup.py file. For example if the version number in setup.py is 0.0.1 then do:
```
git tag 0.0.1
git push --tags
```

License

AGPL

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

README.md

README.md

ckanext-facet_scheming

Requirements

Installation

Helpers

Templates

Config settings

Config (.ini) file

Icons

Developer installation

Tests

Releasing a new version of ckanext-facet_scheming

License

Files

README.md

Latest commit

History

README.md

File metadata and controls

ckanext-facet_scheming

Requirements

Installation

Helpers

Templates

Config settings

Config (.ini) file

Icons

Developer installation

Tests

Releasing a new version of ckanext-facet_scheming

License