Open
Conversation
…ts containing custom metadata from a type in the data model. These types should never be created directly but only used when uploading data
Collaborator
|
This is a good idea. |
|
I'm considering making a tiny change, where instead of types or proxy types, we would be able to select standalone aspects directly (that is, aspects not being children of any type/subtype/proxy type. This pull request is definitely the right direction. Just adding a note: currently the model manager doesn't allow to be included in the custom type. So this feature, although very useful, won't work with a content model created through Share. It will only work for the standard xml model bootstrap |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Added the concept of proxy types used to create cm:content with aspects containing custom metadata from a type in the data model. These types should never be created directly but only used when uploading data.
When a type is selected as a proxy type in the admin console for uploader plus and a file is uploaded and the proxy type selected in uploaded plus, the uploader will show the form for the type, but the uploaded file will be of type cm:content with all the aspects of the selected type applied.