Moodle

I think this is an intended feature. Importing into an existing course does not overwrite existing data, so existing summaries are not overwritten.

We could add an option to import/restore to "overwrite section summaries in the destination course" ...

I've tested this on 1.9.1 and verified that the summaries are NOT imported.

When fixing this bug please add a checkbox to select 'Summaries' at import/restore.

That would be a great solution, since the course shells have no material content, only the CRN and the role assignments, the existing summaries are blank waiting to be filled by the incoming content.

A checkbox for the behavior change would be very useful.

It does appear that the desired behavior could be accomplished by using a restore to an existing course, deleting content and without users. (thanks MP)

Eloy can you have a look at this bug? It's causing problems for a client of a Moodle Partner. Thanks.

Linking this with MDL-8848 . We need to decide how to fix this. I like the "overwrite section summaries" switch (it's unique and clear enough). Please read the linked report.

Ciao

I'd like to add a vote in favor of being able to select "Sumaaries" at import. Some of our faculty get a little confused using the restore function and end up adding students from old classes to new ones. By using "Import" that is not an issue.

Importing is faster than restoring. Also, it requires less steps on part of user, hence less possibility for error. For higher ed institutions, this effects the semester to semester (or quarter to quarter) process. As restore requires more cpu time, if all instructors are restoring over the same period of time in prep for the new semester - we have slow down (yes, I know this depends upon many variables but restore does take longer than import regardless of many of those variables). Also, import does not require faculty to choose user data - just content is imported (which is what our institution wants) - as Jeff Snow points out.

A possible similar topic - it would be nice if instructor created glossaries could come over in the import (as they are user data - by the instructor - this is not the default). Or, at least if this was an option upon import to select only instructor created glossaries/databases/wikis/etc. instead of using the export and import function from within those activities....(wish list).

A new fact pointed out to me:

If you use Import to restore semester to semester, actions such as "update activity open/close dates" will not be triggered by changing the course start date. This only occurs upon restore of a course - not import.

Quite a number of faculty staff use the summary feature and we'd like to be able to import and/or copy the summaries as an option. At present we've got our admin staff retyping all the summaries for each topic / week within each course.

I'd like to add a vote in favor of being able to select "Sumaaries" at import as well. +1 for this, thanks!

Yes, here's another vote for this! This would make life so much easier for faculty to move course content from term to term. I'd like to add another checkbox into the mix: BLOCKS.

Ideally this import function would be a total alternative to backup/restore - in that faculty each term could just hit "import" and select from a list of courses, then select what from the course to import - and that should include the possibility of importing:

content
summaries
blocks
settings (such as # of topics, forced theme, availability, etc.)
update activity start/close dates (set new start date)
various roles of users

This would make life far easier from my standpoint...

Another reason to allow faculty to use "import" OR to allow faculty in the role of "teacher" to be able to restore to an existing course, deleting it first (rather than limit teacher role to only restoring to "current course, deleting it first"):

http://tracker.moodle.org/browse/MDL-18599

There's a problem when a user other than the faculty member restores a course associated with the single simple discussion type forum.

It looks like this issue was fixed when the linked issue was fixed.