[CONTEXP-2] Improvement Ideas Created: 19/Apr/23  Updated: 18/Sep/23  Resolved: 13/Sep/23

Status: Closed
Project: Content Exporter
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0.1

Type: Improvement Priority: Neutral
Reporter: Christoph Damm Assignee: Yen Lac Tue
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: 1d 5h
Original Estimate: Not Specified

Attachments: PNG File asset_reference_properties.png     PNG File csv_asset_reference_id.png     PNG File csv_delimiter.png     PNG File page_asset.png     PNG File referenceValue_column.png    
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

Hello,

i tried the module and have a few improvement suggestions (if some of those is already working but i oversaw it then please let me know).

1) Allow export of more than one node

2) Allow resolving referenced properties. E.g. one has only a uuid of an item within another workspace as property, maybe similiar to how it's done within the delivery API

3) Allow configuration of using "," or ";" as separator

 

Best wishes,

Chris



 Comments   
Comment by Teresa Miyar [ 20/Apr/23 ]

Hi,

Thank you for your input, we analyse your requests and get back to you soon.

Comment by Yen Lac Tue [ 20/Apr/23 ]

Hi chrisD ,

Could you please tell me which configuration part you need for this update?

3) Allow configuration of using "," or ";" as separator

Comment by Christoph Damm [ 20/Apr/23 ]

Hi 

Sorry, this was not phrased precisely. I mean: allow to configure the separator within the csv file "," or ";".

Comment by Yen Lac Tue [ 24/Apr/23 ]

Hi chrisD ,

1) Due to identify parent node and sub nodes of one selected node when exporting, so we can not support export multiple node.

2) Note sure if I understand you correctly, I try with export page include asset, update image field with another asset id, import again and it works

3) Add one more configuration for delimiter:

Please let me know if you have any concern. Thanks!

Comment by Christoph Damm [ 24/Apr/23 ]

Hi,

thank you very much for the effort!
1) maybe it would be possible to (optionally) only allow exporting nodes of the same level.
My clients use case would be more of a bulk export of a workspace (maybe one could add that option then to jcr tools if that makes more sense).

2) My point / use case is more about readability not export and them import again data. So similiar as with delivery API where we transform jcr uuids to asset links. Example: you have an app/workspace a products which references another another app/workspace category. Now ideally within the csv export i'd like not to export simpy the jcr:uuid of the catgeory referenced by a product but its name.

3) awesome, thanks

Best,

 

Chris

Comment by Yen Lac Tue [ 24/Apr/23 ]

Hi chrisD ,

2) Now I understand the use case, I know it's convenient for user by update the referenced just by name, but it depend on the way that product reference to category (by name, by id or by category path...).

For an example between page and asset, it identify asset by asset's jcr id, via image field, even though we can update related fields such as: imageTitle, imageCaption, but the image field is the key to know which asset should be linked.

Does it have a export function in product workspace? if it does, can you send me a export file so I can check to see the way product and category linked together and find the way. Is the category name unique?

Thanks! 

Comment by Yen Lac Tue [ 08/May/23 ]

Hi chrisD ,

I'm back with item 2

I add one new column name Referenced value, which will display referenced value (name or path) from different workspace (dam, tours, categories...) for user easy to read. 

In case user want to update value, they need to update value in Content column.

How do you think?

Thanks!

 

Generated at Mon Feb 12 00:22:12 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.