[OPENAIINT-3] OpenAI: improvement function Created: 23/Jun/23 Updated: 13/Jul/23 Resolved: 13/Jul/23 |
|
| Status: | Closed |
| Project: | OpenAI Integrations |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.0.2 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Yen Lac Tue | Assignee: | Sebastian Geschke |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 2.5h | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Template: |
|
| Acceptance criteria: |
Empty
|
| Date of First Response: |
| Description |
|
Please help to take a look at some feedback from FE testing:
|
| Comments |
| Comment by Sebastian Geschke [ 23/Jun/23 ] |
parameters: titleField: title #name of the title property metaDescriptionField: metaDescription #name of the meta description property ogDescriptionField: ogDescription #name of the og description property metaKeywordsField: metaKeywords # name of the keywords property |
| Comment by Tomáš Gregovský [ 23/Jun/23 ] |
|
hi sgeschke in reaction to:
I can’t select which fields will be generated. We need only the Title, description a meta keywords. The additional OG:title and OG:description can’t be removed
-- This is currently not possible but can be considered as new feature
I would expected it to be a key feature to be able to define list of field and its mapping, rather than having 5 hardcoded fixed fields. Could this be pls implemented?
Also question for keywords... keywords should be coma separated terms/words. right know it generates sentences not usable for meta keywords. could this be somehow improved?
Thank you |
| Comment by Sebastian Geschke [ 23/Jun/23 ] |
|
Hi tgregovsky we'll add the configuration for the fields in the next release. I'll add to option to enable/disable the most common SEO fields. In case you need more than the 5 props let me know. Regarding keywords this is a bit tricky as I mentioned before the API doesn't return deterministic results. In my tests the keywords were always comma separated. A possible solution would be to just split the text and comma separate it (not ideal). |
| Comment by Sebastian Geschke [ 04/Jul/23 ] |
|
Also adding support for logging and context path. |
| Comment by Sebastian Geschke [ 13/Jul/23 ] |
|
Done and released with 1.0.2 |