Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Can metadata schema form auto adjust to contents?

Avatar

Avatar
Validate 1
Level 2
Gl369
Level 2

Likes

5 likes

Total Posts

24 posts

Correct Reply

2 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 1
Applaud 5
View profile

Avatar
Validate 1
Level 2
Gl369
Level 2

Likes

5 likes

Total Posts

24 posts

Correct Reply

2 solutions
Top badges earned
Validate 1
Boost 5
Boost 3
Boost 1
Applaud 5
View profile
Gl369
Level 2

05-09-2018

Is there a way to have a component for the metadata schema expand based on the contents of the node? 

For example we have a field called "legacyMetada" which came from previous DAM systems.  This legacyMetadata can have many words and values that are strung together on the node:

{"IndexClass":"NYPD-Gap","AssetClass":"Accessories","AssetNumber":"20061018.00.00011","SampleType":"Headwear-Other","Description":"White straw cowboy hat with embroidered flowers","Department":"Girl's","Classification":"Straw","Details":["Overall Design"],"PurchasedFrom":"Retail","Season":"Summer","Year":"2006","SecGroup":"NYPD - Gap","SecType":"_grp"}

Currently, the form display is a single line and the user has to "scroll" to see the full contents.  Is there a way to have the form adjust to the amount of content?

Ideally, we would like to parse out these values and put into a proper metadata space but do not know how...

Replies

Avatar

Avatar
Validate 25
Level 10
smacdonald2008
Level 10

Likes

1,408 likes

Total Posts

12,671 posts

Correct Reply

2,278 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Give back 900
Give back 600
View profile

Avatar
Validate 25
Level 10
smacdonald2008
Level 10

Likes

1,408 likes

Total Posts

12,671 posts

Correct Reply

2,278 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Give back 900
Give back 600
View profile
smacdonald2008
Level 10

05-09-2018

This is not available out of the box. You would need to develop a lot of custom functionality in AEM to perform this use case. There is no example or doc for this either.

Avatar

Avatar
Validate 25
Level 10
smacdonald2008
Level 10

Likes

1,408 likes

Total Posts

12,671 posts

Correct Reply

2,278 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Give back 900
Give back 600
View profile

Avatar
Validate 25
Level 10
smacdonald2008
Level 10

Likes

1,408 likes

Total Posts

12,671 posts

Correct Reply

2,278 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Give back 900
Give back 600
View profile
smacdonald2008
Level 10

05-09-2018

Also - i have asked the team to look here to provide additional thoughts.

Avatar

Avatar
Boost 5
Level 3
ashu4pma
Level 3

Likes

17 likes

Total Posts

38 posts

Correct Reply

15 solutions
Top badges earned
Boost 5
Boost 3
Boost 10
Boost 1
Affirm 5
View profile

Avatar
Boost 5
Level 3
ashu4pma
Level 3

Likes

17 likes

Total Posts

38 posts

Correct Reply

15 solutions
Top badges earned
Boost 5
Boost 3
Boost 10
Boost 1
Affirm 5
View profile
ashu4pma
Level 3

13-09-2018

there is no OOTB filed predicate to cater this use case offered by Assets Metadata Schema Editor. There is text area componen[0] offered by the Granite's platform which can be used to add a custom field predicate. All field predicates at Metadata Schema Editor are the wrapper of  Granite platform's form elements, be it textfield, sectionheader, dropdown etc.

Moreover [0] takes rows, cols and max-length  as an input parameter to control the textarea height/width on rendering, these configurations should be set dynamically based on the metadata content length.

[0] /libs/granite/ui/components/coral/foundation/form/textarea