Refactoring attributes

[andrixnet]

Currently attributes are implemented using database table for attribute definition. And (at least) some translations. This makes nodes divergent after instalation.

Also there are (old) parts of the code that refer to attributes that no longer exist.
#380

I propose finalizing a reimplementation of the attribute subsystem, perhaps in a similar way to lib\Objects\GeoCache, to allow the following:

• common superset of attributes as part of the code. All nodes are in sync.
  Also solves this Romanian translation for attribute-definitions.xml okapi#402
• individual attributes may be disabled on a certain node, same as forbidden_caches
  Allows nodes to disable supported attributes which they do not desire to feature.
• implement in such way to allow node icon theme personalization in settings
  Also solves this cache related icons and attributes and their translation #97

[andrixnet]

Attributes can also be categorized as following:

INFORMATIONAL

• magnetic
• wherigo cartridge
• available 24/7
• nature preserve
• monument
• etc

RECOMMENDATIONS

• bring your children
• be stealth
• etc

REQUIREMENTS

• need a special tool
• need a shovel / flashlight / UV light
• field puzzle
• access fee
• etc

PERMISSIONS

• dogs allowed
• cars / vehicles forbidden (ie parks)
• open fire forbidden
• etc

AMENITIES / FACILITIES

• parking available
• drinking water available
• fuel available
• etc

HAZARDS

• dangerous place
• ticks
• thorns

Categorization can be used internally (for grouping and sorting) and, optionally, publicly for better UI.
It would also help with opencaching/okapi#70

Some attributes, in principle, may have 3 states :

• ATTRIBUTE SET
• NOT ATTRIBUTE SET
• UNSET

OPENCACHING-PL implemets only 2 states. However, careful design and categorization may be used to improve the attributes into a meaningful and useful set that provides better characterization for caches.
Solves #99

Some of the current attributes are less then optimal and imlpy less meaning for the cache, while other meanings are missing.

[andrixnet]

I will devise later an SQL query to analyze attribute usage on each node, such that the existing attribute meaningfulness can be evaluated.

[andrixnet]

The following code will generate a comparison matrix between the attributes (for the main languages PL EN NL RO) in your node's database:

select
  c1.language,c1.id,c1.text_short,
  c2.language,c2.id,c2.text_short,
  c3.language,c3.id,c3.text_short,
  c4.language,c4.id,c4.text_short
  from
    cache_attrib c1
    left join cache_attrib c2 on (c1.id=c2.id and c2.language='PL')
    left join cache_attrib c3 on (c1.id=c3.id and c3.language='NL')
    left join cache_attrib c4 on (c1.id=c4.id and c4.language='RO')
where
  c1.language='EN'

UNION 

select
  c1.language,c1.id,c1.text_short,
  c2.language,c2.id,c2.text_short,
  c3.language,c3.id,c3.text_short,
  c4.language,c4.id,c4.text_short
  from
    cache_attrib c2
    left join cache_attrib c1 on (c2.id=c1.id and c1.language='EN')
    left join cache_attrib c3 on (c2.id=c3.id and c3.language='NL')
    left join cache_attrib c4 on (c2.id=c4.id and c4.language='RO')
where
  c2.language='PL'

UNION 

select
  c1.language,c1.id,c1.text_short,
  c2.language,c2.id,c2.text_short,
  c3.language,c3.id,c3.text_short,
  c4.language,c4.id,c4.text_short
  from
    cache_attrib c3
    left join cache_attrib c1 on (c3.id=c1.id and c1.language='EN')
    left join cache_attrib c2 on (c3.id=c2.id and c2.language='PL')
    left join cache_attrib c4 on (c3.id=c4.id and c4.language='RO')
where
  c3.language='NL'

UNION 

select
  c1.language,c1.id,c1.text_short,
  c2.language,c2.id,c2.text_short,
  c3.language,c3.id,c3.text_short,
  c4.language,c4.id,c4.text_short
  from
    cache_attrib c4
    left join cache_attrib c1 on (c4.id=c1.id and c1.language='EN')
    left join cache_attrib c2 on (c4.id=c2.id and c2.language='PL')
    left join cache_attrib c3 on (c4.id=c3.id and c3.language='NL')
where
  c4.language='RO'

[andrixnet]

This is a CSV export showing the attributes matrix on OC RO.

attribute-matrix.txt

[andrixnet]

Use this query to generate attribute usage statistics according to your node:

select a.id,a.text_short,count(ca.attrib_id) as _cnt
from 
    cache_attrib a
    left join caches_attributes ca on (a.id=ca.attrib_id)
where
    a.language='RO'
    group by ca.attrib_id
    order by _cnt

Replace the language value with PL or NL (according to your node being OC PL or OC NL) to obtain your own statistics correctly based on your attributes matrix.

[andrixnet]

Attribute usage stats for OC RO (total of 309 cache analyzed)
attribute_usage.txt