[Using Sakai] for learning material

[Rashmi Maheshwari]

Hi Adam,
The url for etudes-util is 
https://source.sakaiproject.org/contrib/etudes/etudes-util/tags/1.0.7
and to use the class here is a code snippet from our announcements tool:
/
                         // translate old message embed data
                         String nMessageData = oMessage.getBody();
                         Set<String> refs = 
XrefHelper.harvestEmbeddedReferences(nMessageData, null);

                         if (!refs.isEmpty())
                         {
                             List<Translation> translations = 
XrefHelper.importTranslateResources(refs, toContext, "Announcements");
                             nMessageData = 
XrefHelper.translateEmbeddedReferences(nMessageData, translations, 
toContext);
                         }/

Hope this helps,
Rashmi

On 11/3/2010 2:46 AM, Adam Marshall wrote:
>
> Rashimi
>
> Do you have a patch for  XrefHelper?-This would be very useful for us.
>
> adam
>
> *From:*sakai-user-bounces at collab.sakaiproject.org 
> [mailto:sakai-user-bounces at collab.sakaiproject.org] *On Behalf Of 
> *Rashmi Maheshwari
> *Sent:* 02 November 2010 18:54
> *To:* sakai-user at collab.sakaiproject.org; Etudes
> *Subject:* Re: [Using Sakai] for learning material
>
> Hi Marsh,
> We have worked on similar issue at Etudes and in our etudes-util 
> project,there is a XrefHelper class which parses the content and for 
> all embedded media translates the url and
> changes it from old site id to new site id. We have included the call 
> to XrefHelper methods on tool's transferCopyEntities().
>
> I am pointing here for reference only and this work is not tested on 
> Sakai 2.6 and higher versions,
> thanks,
> Rashmi
>
>
>
> On 11/2/2010 11:32 AM, Marshall Feldman wrote:
>
> I'm trying to post this again, but not in HTML.
>
>     I realize that some tools are packaged to stand alone or plug into
>     other systems, but I'd really like to see Sakai have some
>     standardized ways of sharing data between tools and for converting
>     relative links to site-specific tools when importing from one site
>     to another. For a developer porting a separate tool, meeting these
>     standards would be the price of admission. A good API could make the
>     process relatively painless. I'm thinking of Unix stdin, stdout,
>     pipes, etc. as models of inter-module communications.
>
> Marsh Feldman
>
> On 11/2/2010 1:42 PM, sakai-user-request at collab.sakaiproject.org 
> <mailto:sakai-user-request at collab.sakaiproject.org> wrote:
>
> Date: Tue, 2 Nov 2010 14:59:23 -0000
> From: "Jon Higham"<J.Higham at hull.ac.uk>  <mailto:J.Higham at hull.ac.uk>
> Subject: Re: [Using Sakai] for learning material
> To: "Adam Marshall"<adam.marshall at oucs.ox.ac.uk>  <mailto:adam.marshall at oucs.ox.ac.uk>,   "Marshall Feldman"
>         <marsh at uri.edu>  <mailto:marsh at uri.edu>,<sakai-user at collab.sakaiproject.org>  <mailto:sakai-user at collab.sakaiproject.org>,       "Regimantas
>         Maciulskis"<regimantas.maciulskis at gmail.com>  <mailto:regimantas.maciulskis at gmail.com>
> Message-ID:
>         <EE007AF7077B7749B57FD9B55A75709505E62CB3 at EXCL1VS1.adir.hull.ac.uk>  <mailto:EE007AF7077B7749B57FD9B55A75709505E62CB3 at EXCL1VS1.adir.hull.ac.uk>
> Content-Type: text/plain; charset="us-ascii"
>   
> I'll start a jira for the Resources update. It only works if you are
> saving Resources to the file system, rather than to the database, which
> production systems will do. I'm not sure what would happen if you save
> Resources to the DB. I'm a bit concerned about it being inefficient,
> however, as it copies the file then checks to see if it is of type text
> and if it is reads it in and changes any instance of the old site id
> before writing the file out and updating the file size.
>   
> In Melete, if you link to a file in the site Resources and do an Import
> > From Site, the file will be added to Melete's own resource area on the
> new site and the link updated appropriately. We have bypassed this so
> that it will still link to Resources but with an updated URL whilst
> still copying over the file from old to new site. I don't think etudes
> are likely to want this in their core code as it breaks the
> self-contained nature of Melete.
>   
>   
> Jon
>
>   
>   
> _______________________________________________
> sakai-user mailing list
> sakai-user at collab.sakaiproject.org  <mailto:sakai-user at collab.sakaiproject.org>
> http://collab.sakaiproject.org/mailman/listinfo/sakai-user
>   
> TO UNSUBSCRIBE: send email tosakai-user-unsubscribe at collab.sakaiproject.org  <mailto:sakai-user-unsubscribe at collab.sakaiproject.org>  with a subject of "unsubscribe"
>
>
>
>
> -- 
> Rashmi Maheshwari
> Learning Systems Developer
> Etudes Inc
> http://etudes.org


-- 
Rashmi Maheshwari
Learning Systems Developer
Etudes Inc
http://etudes.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-user/attachments/20101103/5af3b1e6/attachment.html