LSCS DCR metadata generation via fielmappings

Hello,

Currently inherited a TS 7.1 environment.

As i understand, when deploying to LSCS (development or producion) via PLC, we can map DCR content fields to metadata fields via livesite_customer\fieldmappings xml configuration files. Is this correct?

Are there additional steps necessary to do so?

Thanks in advance,

André

Find more posts tagged with

Comments

Adam Stoller

You can map DCR fields to be deployed to LSCS, and/or you can map DCR fields to selection lists in the the Search configuration file so that users can select / advanced-search on them.

If you want to explicitly map DCR fields to EAs (metadata) on the DCRs themselves, you'd have to write your own customization to do so (generally in the workflow, though potentially within custom tagging configurations to call custom code)

If you want to explicitly map DCR fields to EAs on Page files, I think you need to do that within a customization to the [copy-of-the] PLC workflow.

I'm not familiar with livesite_customer\fieldmappings xml - and don't see it mentioned in any of the docs other than from a different path in the context of Search configuration - so it could be part of a customization in your inherited environment.

nipper

I do not know why Ghoti didn't remmeber fieldmapping, as we used it on a project together.

This is slightly documented, here is a thread that talks about it:

/t5/LiveSite/LSCS-FieldMapping-how-to-override-customize/m-p/172674/highlight/true#M6757

nipper

This will allow you to search on DCR fields. Typically you are only able to seach on EAs.

I was told this changed in 7.3.2, but you are on 7.1 so you should be OK.

BTW, I hope you plan to upgrade. There are some issues with your version and I would not want to run live with anyhting under LSCS 721 SP1.

Adam Stoller

nipper wrote:
I do not know why Ghoti didn't remmeber fieldmapping, as we used it on a project together.

This is slightly documented, here is a thread that talks about it:

/t5/LiveSite/LSCS-FieldMapping-how-to-override-customize/m-p/172674/highlight/true#M6757

Nipper - re-read my response - I indicated it was possible to do what was included in the thread you pointed to and stated that I knew nothing about the explicit filename mentioned (in the thread, it's plural and is a directory - not a file)

avpadrao

Hi ghotti, nipper, yes, that's exactly what i want

Already created a fieldmapping configuration file in livesite_customer\fieldmappings\BalcaoEntryFieldMapping.xml, and edited livesite_customer\resources\customer-teamsite-resource-config.xml, adding the three beans described in the related post, built (and rebuilt), iwresetted all, but still to no avail.

I can see in Teamsite, in the DCR properties, the content of TeamSite/LiveSite/DeploymentAudit, that only the StandardMetadata is being applied.

Also, i see that the lscsidx and lscs_manifest.xml generated during deployment do not contain the custom fields extracted from the DCR, so it seems that my custom content extractor is not being called, but only the default one.

Are there any additional configuration steps that i should do in order to acccomplish this, that you know of?

Thanks in advance,

André

nipper

I have done it on 721, from that thread. You are on an older version and that functionality may not have been implemented. No clue, never tried.

FYI, this did not add new metadata, rather it allows you to query based on DCR values without adding them as EAs.

You may need ot use FormAPI to create EAs on the DCR and just query that.

avpadrao

Hello all,

"problem" solved.

The "problem" was actually a instalation of advanced-backpacking spar example, wich includes a spring bean with id=customer.teamsite.DeploymentService.DeploymentDescriptors, wich replaces the one customized in livesite_customer\resources\customer folder, so my configurations were not loaded.

Once i commented out the bean configuration in advancedbackpacking and iwresetted, the DCR fields got mapped and indexed, as expected.

Thanks for the help,

André