[MGNLDAM-615] Offer to specify metadata for all assets in an archive to be uploaded Created: 25/Aug/15 Updated: 22/Apr/20 Resolved: 22/Apr/20 |
|
| Status: | Closed |
| Project: | Magnolia DAM Module |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Nils Breunese | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | support, ux | ||
| Remaining Estimate: | 4d | ||
| Time Spent: | 1d | ||
| Original Estimate: | 5d | ||
| Attachments: |
|
||||||||||||
| Issue Links: |
|
||||||||||||
| 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)
|
||||||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||||||
| Date of First Response: | |||||||||||||
| Story Points: | 8 | ||||||||||||
| Description |
|
To deal with copyright infringement claims it is important that our users always fill in the source and copyright fields for assets. We therefore made these fields required fields, but we found that when users upload assets via zip files these required fields are not enforced. Could Magnolia enforce these required fields for bulk uploads as well? I don't know what the UI for this should look like, because potentially this means filling out a form for every asset in the zip file. In our experience the source and copyright fields are usually the same for all assets in a zip file, so setting required fields for all assets in one go would be handy in our case, but for a field like title or description this might not be feasible. |
| Comments |
| Comment by Andreas Weder [ 01/Sep/15 ] |
|
Hi. First of all, I've added a quick mockup how I would tackle this, and the reasoning behind this. I would not tie this to required fields only, actually, but allow to configure a form shown while uploading an archive of assets. The form is shown during the upload and stays once it has finished until the user presses "done" or "save". It's at this point, when you also check for required values. This solution offers a customer to also specify non-mandatory fields, such as the "tags" in the example I modelled, and it explicitely forces you to think about what exactly it is you want to offer during an archive upload - this might be significantly different than what you offer when uploading a single asset. In the above example, I give you the option to also specify a (different, potentially new) folder to move the assets to. Everything entered in the form is applied to all uploaded assets. If you decide you ask for a title, then that title is assigned to all assets. This is clearer than having a mixture between bulk action and still the individuality of a single asset upload. |
| Comment by Andreas Weder [ 01/Sep/15 ] |
|
So for me, the current implementation is already going into the right direction; we show a dialog that allows you to select the encoding of the uploaded files. What I don't know is:
And:
|
| Comment by Nils Breunese [ 01/Sep/15 ] |
|
Looks good, Andreas! |
| Comment by Ngoc Nguyenthanh [ 26/Sep/16 ] |
|
Hi weder
See my attachment for what I've tried to map to Magnolia with form tabs: |
| Comment by Mikaël Geljić [ 29/Sep/16 ] |
|
I just clarified that with Andreas:
|
| Comment by Antti Hietala [ 19/May/17 ] |
|
This improvement has value as a generic action to edit metadata in bulk on assets that already exists in the DAM. The requirement about doing this in conjunction with a zip upload makes it more difficult – it'll be hard to figure out what is in the zip and whether the metadata should apply to all items or just items of same type. |
| Comment by Richard Gange [ 22/Apr/20 ] |
|
Hi, Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes. Best regards, The Magnolia Support Team. |