<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Aug 16, 2012, at 3:30 PM, Marc KempsSnijders wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div>2. We are working out the b) route at the moment since the harvesting and indexing step has already been taken care of. So on our side we should simply be able to query for all SRU endpoints on the available CMDI files and start the content search method from there. Or to insert a content search engine widget at the UI level for each resource that has a content search engine link.</div></span><br class="Apple-interchange-newline"></blockquote></div>Exactly :) In the future the aggregator could simply ask the VLO or the (not-yet-there) metadatasearch.<div><br></div><div>Cheers,</div><div><br></div><div>Herman<br><div><div><br></div></div></div></body></html>