Noah Savage
My feedback
9 results found
-
5 votesNoah Savage
shared this idea
·
-
1 vote
-
2 votesNoah Savage
shared this idea
·
-
3 votesNoah Savage
supported this idea
·
-
4 votesNoah Savage
shared this idea
·
-
10 votesNoah Savage
supported this idea
·
-
20 votesNoah Savage
supported this idea
·
-
4 votesNoah Savage
supported this idea
·
-
6 votes
An error occurred while saving the comment Noah Savage
shared this idea
·
Hi Genie,
We are one of the institutions that disabled shared lists. Our goal with setting up Ares at UNC was to make everything as simple as possible, so that the web form could be used without instruction or training. Shared lists was initially accessible at our institution, but we found that the feature did not save instructors much extra time, and was additionally difficult to figure out.
To add some background, in order to minimize the amount of things that faculty need to memorize, we do not explain to instructors the problems that come up when the data generate separate pages for the same cross-listed course: instead, we run a query that tells which items were added by instructors the previous day. When we spot one that was added for a cross-listed class, we clone it behind the scenes. Fortunately, most classes are not cross-listed, so this is not that large an issue.
A related issue is the introductory classes that have a lot of different sections. If a class uses the same material for 30 different sections, we have to clone it 29 times. Again, this isn't a huge burden, but it would be more convenient to have a quick way of doing this.
I recently spoke with a librarian at another institution, who expressed his wishes this way (just found the E-mail): "1: the External ID and Registration ID fields support multiple items, That way many CMS courses could access the information in a single Ares course. And 2: the creation of a Merge Button that would essentially smash 2 or more course lists together."