[Using Sakai] Resource links - updated on move?

[Matthew Jones]

Well you'd have to be authenticated, but it sounds like that linkchecker
application does http auth so it could provide going into your website
which other apps couldn't. You'd probably also have to have a script
driving it that provides it the top level of every site so like.

<Write something REST/Web service/API to get the URLs of the front page of
all Sakai Sites>
Run linkchecker on all of the site urls with an admin authenticated user
Consolidate all of the resulting reports

iFrames might cause a problem, but running the mobile portal with
portal/pda should improve the result from that. (Makes running selenium
tests a little easier)

Anyway, just ideas here, the actual implementation I think would take a
little time and probably more likely to be some type of small group
Computer Science style class research project.




On Mon, Aug 4, 2014 at 1:14 PM, Gregory Guthrie <guthrie at mum.edu> wrote:

> I think the challenge with this would be that links are content mostly in
> sub-pages not all directly linked by a URL on the front page (yes?).
>
> The “dark web” impact.
>
>
>
> For example, the w3.org link checker (and others..) don’t even find bad
> links in the front page “site info” text.
>
>
>
> -------------------------------------------
> *From:* Matthew Jones [mailto:matthew at longsight.com]
> *Sent:* Monday, August 04, 2014 11:47 AM
> *To:* Adam Marshall
> *Cc:* Gregory Guthrie; sakai-user at collab.sakaiproject.org
>
> *Subject:* Re: [Using Sakai] Resource links - updated on move?
>
>
>
> Yeah, sure you probably could run an app like
> https://code.google.com/p/linkchecker/ on your own instance and get a
> report, but then you'll have to go fix everything manually.
>
>
>
> One of the feature requests on that page was to convert that to a web
> application to run it on the page so I guess it could be made to be more
> embedded in something like Sakai but it would take some work for sure. It
> doesn't look like this project hasn't been updated in a while, and I've
> never personally run it. Probably would be nice, especially if it could
> scan content hosting to try to find the fixed links, but adding in more and
> more features for sure would add to development time.
>
>
>
> On Wed, Jul 30, 2014 at 7:05 AM, Adam Marshall <adam.marshall at it.ox.ac.uk>
> wrote:
>
> It would!
>
>  adam
>
>  --
>
>  ** Note change of email address to adam.marshall at it.ox.ac.uk **
>
>  Dr A C Marshall, WebLearn Service Manager, University of Oxford.
>
> IT Services, 13 Banbury Rd, Oxford. OX2 6NN.
>
>  *From:* sakai-user-bounces at collab.sakaiproject.org [mailto:
> sakai-user-bounces at collab.sakaiproject.org] *On Behalf Of *Gregory Guthrie
> *Sent:* 29 July 2014 21:05
> *To:* Matthew Jones
> *Cc:* sakai-user at collab.sakaiproject.org
>
>
> *Subject:* Re: [Using Sakai] Resource links - updated on move?
>
>  There are many web-site link-checkers, to check for stale or broken
> links in a web-site.
>
>  Wouldn’t it be nice to have something similar for a Sakai site?
>
>  *From:* Matthew Jones [mailto:matthew at longsight.com
> <matthew at longsight.com>]
> *Sent:* Monday, July 28, 2014 11:17 PM
> *Subject:* Re: [Using Sakai] Resource links - updated on move?
>
>  No, the only time that links within content are updated are when you're
> duplicating a site and importing the material. Moving a file doesn't
> trigger updating any links to that file.
>
>  On Mon, Jul 28, 2014 at 10:25 PM, Gregory Guthrie <guthrie at mum.edu>
> wrote:
>
> If I move resources, using the tools within Sakai, are the links within
> the site updated?
>
>  (I want to re-organize some resources, but don’t know all the places
> from which then may be referenced.)
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-user/attachments/20140804/bb43e69c/attachment.html