nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can I capture the save button on metatagger?

buddyholly

Is there anyway to capture the save button on MetaTagger when tagging files? We need to eliminate bad characters like curly quotes from the summary field, we can not use regex because since we're using the rack script in the config file to autosummarize it somehow bypasses the validation-regex, so we thought we maybe be able to check for bad characters via capture of the save button. Any other suggestions tho are appreciated if the capture is not possible? Thanks.

Find more posts tagged with

Comments

Migrateduser

Can you clarify what you mean by "capture the save button?" Are the bad characters in your original files?

buddyholly

This is how it works. The user will create a DCR, which has a content field. MetaTagger we have set up to auto summarize the DCR's content field. So when they tag the document the summary is prefilled. The prefilled data is fine it is cleaned up text. However we are also allowing users to replace the auto summary with their own summary if they do not like the generated one. We have a situation where they may paste content from MS Word and characters such as curly quotes will remain in the summary and not be cleaned if they hit save. This is a problem for our search engine which does not like these characters outside the set it recognizes. So is there a way to capture the MetaTagger save button to process the summary field and clean out these characters?

Migrateduser

It sounds like the easiest thing to do would be to invoke some kind of script to cleanse your summaries of the bad characters before the data is passed to your search engine. How are you sending the metadata to your search engine?

TESTPRoject.dcpackage

New Text Document.txt