[IMGREC-22] Use space character as word separator in tags Created: 10/Sep/18 Updated: 16/May/19 Resolved: 16/May/19 |
|
| Status: | Closed |
| Project: | Image Recognition |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.1 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Antti Hietala | Assignee: | Antonín Juran |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 0.5h | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Documentation update required: |
Yes
|
| Date of First Response: | |
| Epic Link: | Image Rec |
| Sprint: | Add-Ons 11 |
| Story Points: | 1 |
| Description |
|
AWS Rekognition and Google Vision use spaces in multiword tags ("Clock Tower", "Leisure Activities", "black and white"). Magnolia uses underscore ("prairie_chicken"). Let's make Magnolia local image recognition work the same way. Acceptance criteria:
Note: Check if space is allowed in content tags to begin with. Could be a limitation of tagging rather than image recognition. |
| Comments |
| Comment by Laura Delnevo [ 02/May/19 ] |
|
Hi ahietala, we will keep this ticket here; but to be able to show space rather than underscore, this issue should be fixed with CONTTAGS project. Once it's fixed in CONTTAGS it will be automatically fixed for IMGREC too (if they don't do this, we'll get the hyphen rather than the space) |