[Building Sakai] Investigating site exports from Sakai 2
Speelmon, Lance Day
lance at indiana.edu
Tue Oct 13 07:35:10 PDT 2009
Agreed - I understand and appreciate the need for site backups. However, I personally am focused on migration and from a migration perspective the need for a full backup format will come late in the project lifecycle... And the primary use case as it has been expressed is moving Project sites from 2->3. L
Lance Speelmon
Scholarly Technologist
On Oct 12, 2009, at 9:03 AM, csev wrote:
> I agree with all that - I was just reacting to your "Use the blocker,
> Luke" statement. Like the force, the blocker has two sides to it.
>
> /Chuck
>
> On Oct 12, 2009, at 7:52 AM, Steve Swinsburg wrote:
>
>> I think the flipside to the 'once schools are ready they will fix
>> archive' argument is that once schools are ready to move on, they
>> may see there is no good full export, or some other product/vendor
>> will tell them that the export is no good, and they may consider
>> moving away from Sakai altogether. That being said, they still need
>> to get their content out, but 'vendor lock-in' isn't a good selling
>> point ;)
>>
>> I know a lot of institutions that have Sakai are just consumers and
>> see Sakai to be a vendor type product, they have no resources to
>> devote to Sakai except to keep it running, so hope someone else will
>> do it for them and it will be 'in the next release'.
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
More information about the sakai-dev
mailing list