link relation app?

I've got a request from the business units to find an app/solution that tells them what links to what in our website directories. For example they want to know if there is a .pdf (.asp, .doc, .xls, etc.) file what files link to it. Would love to know how each of you are addressing this type of issue.

Windows/TS 6.7.1

Thanks,
Nico

Find more posts tagged with

Comments

nipper

I ignore requests like that. Smiley Very Happy

I know there are some link checkers out there that you can use. I have also tailored some things.

If you want a complete list, try to buy a tool.

If you are looking for certain files (like images) that have links managed in templates, then you can, during the WF (or as part of the TPL) attach an EA on the DCR and/or the destination that one links to the other.

If you are looking for general purpose, you can write a perl script that will parse the HTML, looking for links and maintaining a list. Trying to do an all-inclusive list will not be trivial, there will be a lot of data. If you want to do only PDFs or something like that, it won't be tough.

Of course these only work when the link is in TS managed code, if you have data outside TS, then no links show.

Tbag

We've got a similar request right now, but it isn't for links so much as it is for knowing "an example page that includes a include."

For example, you've got "abc.html" with server side includes foo.shtml and bar.shtml. Currently, our workflow will only send out URLs for approval that correspond directly to the assets attached to the workflow.

This presents a bit of a problem for some of our .... umm .... less experienced? users because they're getting this preview url on QA that's essentially just a snippet of the page kinda floating off in mid air by itself.

One architecture we're looking at here is using something like DataDeploy to capture the "container-to-include" relationships during the TeamSite TPL generation process.

Then, in the workflow, we can reverse lookup a sample page that references the SSI that's attached to the workflow for purposes of sending out a "real" URL.

Make sense?

If you hate DataDeploy as much as I do, it'd be pretty straight-forward to gin up your own equivalent that gets triggered during a TPL's execution. You're basically forced to tightly-couple your TPLs to your DCTs anyway, so go ahead and identify what links exist in your DCR during generation, and then call a reusable database abstraction layer to stick that relationship in a DB for later retrieval.

HTH,
Tom