[IMGREC-16] Publish new image tags to public, if applicable Created: 29/Aug/18 Updated: 26/Aug/22 |
|
| Status: | Open |
| Project: | Image Recognition |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Cedric Reichenbach | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoR: |
Empty
|
||||||||
| Date of First Response: | |||||||||
| Epic Link: | ImgRec Later | ||||||||
| Team: | |||||||||
| Description |
|
Since image recognition should only run on author, tags should be somehow propagated to public instances. This could be done by publication, but we should be careful about when this is desirable and when it is not. For example a not-yet published asset should not be published just because it received a new tag, but an already fully-published one should likely be re-published. This behavior could be configurable, and even include user interaction (like a button "publish all tagged assets" inside a pulse notification when indexing is done). |
| Comments |
| Comment by Antti Hietala [ 08/Jan/19 ] |
|
creichenbach, can you provide a use case where a special publishing action would be needed? I consider image tags metadata like any other metadata: copyright, location etc. If you add tags then you need to re-publish the image. The default publishing action should be enough. Currently we don't demonstrate the use of image tags on the visitor website. We don't index image tags for website search. We also don't render tags as navigable links like we do with tour tags. Sure, I can imagine that a website that has lots of image content might want to do that. But today image tags are only used/demoed to help editors find images faster on the author instance. |
| Comment by Cedric Reichenbach [ 09/Jan/19 ] |
|
ahietala I guess the normal, built-in publishing action is indeed appropriate here. The remaining question then is when and how we apply it after auto-tagging images. Do we ask the user, or even do it automatically? |
| Comment by Antti Hietala [ 09/Jan/19 ] |
|
I was thinking that we should leave it completely up to the users to publish tagged images. If the client has a case where image tags are used on public (rare) then they should publish the assets manually. |