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; } } }

Holy grail of link tracking

Mr_Cruise

TS: 6.7.2
OS: Windows

Dear All,

I have a cunning plan to extract the links out of DCR content and store them in a single extended attribute called 'Links'. I will then configure the search to index this attribute so the business can search for links that are embedded in their content.

Pros
1) Using the power of the search engine
2) Easy search as only you have to search one field in search screen.

Cons
1) Difficult to extract links

Can anyone think why this might be a bad idea?

Many thanks

Lee

Lee

Find more posts tagged with

Comments

nipper

A single EA ? What if there are multiple links ? Just the URL or the name as well ?

IMHO, build a generic link processer inline (may take some reformatting of DCRs), use that in all DCRs.

Then in your workflow when you automatically build your HTML (you do automatically build HTML in your WF don't you ?) you can regex the DCR and get all links, attach something like TeamSite/Links/0/Label, TeamSite/Links/0/URL, TeamSite/Links/1/Label etc.

This will slow your WF down but it is not a huge issue. I do it already for images.