EAs, 7.3.2, and LSCS Preview

cecilb63

In 7.3.2, it is no longer necessary to publish content to LSCS preview. Instead, all content within TeamSite is automatically made available to LSCS preview through the underlying IDOL indexing.

But now that we don't publish documents to preview, for some, an important step will now be missing: The setting of DCR attrs as EAs during publishing workflow. Some have implemented this functionality as a callout during DCR onSave(), others elected to do it during publishing. It seems that though we don't need to publish to LSCS preview now, some will still have to do some form of workflow to their EAs set so preview will work unless they use onSave()

Frankly both approaches seem to be poor solutions. onSave only effects the file being changed at the moment, not all the other 1000s of DCRs that may exist already. This is a problem when an existing attribute must now be exposed as an EA. There's no choice but to run workflow against the 1000s DCRs to get them "converted", then rely on onSave() moving forward.


I've looked at FieldMappings and that file can certainly extract data from inside a DCR and expose it as an IDOL field but not an EA. Eduction can do this too but this only gets that data as a IDOL field as well. I don't see how FieldMapping can be configured to expose extracted data as a EA.


Unless someone can tell me how to get FieldMapping to expose DCR attrs as EAs, or if there is some other automatic solution I am missing, I think TeamSite needs to expose some hook during IDOL indexing that will allow the creation of EAs from DCR attrs. That way whenever a new EA needs to be introduced, the document simply needs to be reindexed, which is a lot of easier than running workflows.

Thoughts? Solutions? Suggestions?

Rick Poulin

Unless someone can tell me how to get FieldMapping to expose DCR attrs as EAs, or if there is some other automatic solution I am missing, I think TeamSite needs to expose some hook during IDOL indexing that will allow the creation of EAs from DCR attrs. That way whenever a new EA needs to be introduced, the document simply needs to be reindexed, which is a lot of easier than running workflows. Thoughts? Solutions? Suggestions?

I don't see how your query has anything to do with 7.3.2? It wasn't automatic before; now it's still not but it's somewhat closer than before.

Personally, I don't like the FieldMapping route because that only works for your authoring side; you end up needing a different solution for the runtime, thus duplicating effort + config. The onSave() and workflow are both legitimate options to write EAs and I think a third would be using iwat triggers. That latter one is probably closest to being 'automatic', as far as what you seem to be looking to achieve.