[EXTDAM-152] [Verify Use Case] Exclude copyrights field from asset search Created: 08/Sep/20 Updated: 28/Sep/21 Resolved: 18/Nov/20 |
|
| Status: | Closed |
| Project: | External DAMs |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor |
| Reporter: | Lucius Müller | Assignee: | Laura Delnevo |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| 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)
|
| Date of First Response: | |
| Epic Link: | DAM Phase 2 |
| Description |
|
Go to 2m10s of the video https://drive.google.com/drive/folders/1m79EZCyH9b_DBRnwSRkWPmKBkDan5ntP Current behaviour
Expected Behaviour
|
| Comments |
| Comment by Jesus Alonso [ 24/Sep/20 ] |
|
It turns out this is how bynder works, it searches in all the metadata properties, not only by the name. You can check the video of the bynder console -> https://drive.google.com/file/d/1WJKVuPPZI8nhnETGcnaOGYeozgd3BguG/view?usp=sharing If needed, we could exclude of the result the assets whose name do not match, but maybe this is a better behaviour. |
| Comment by Laura Delnevo [ 18/Nov/20 ] |
|
Won't fix for now. If we will get client's feedback in future, we should consider configuration (as per latest comment) |