[DOCU-259] Pre-populating metadata Created: 07/Mar/12 Updated: 30/Sep/19 Resolved: 30/Sep/19 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | content |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Antti Hietala | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | outdated | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Date of First Response: |
| Description |
|
Document how to pre-populate metadata fields. The goal is to read any available metadata created by the system and use it to pre-fill corresponding user-editable metadata properties. Or pre-fill values from a static resource. This way editors don't need to fill all fields by hand. This is a common request for image uploads. For example, you might want to pre-fill the Publisher or Rights fields with the company name or the current user's name to ensure that they are not left empty. Use case drafted at Pre-populating metadata. |
| Comments |
| Comment by Julie Legendre [ 30/Sep/19 ] |
|
In order to better focus our efforts on DOCU tickets that are still relevant and important, all tickets older than 18 months have been labelled as outdated and are being automatically closed. |