Home / Import/Export / Topic
Admin
Registered: 2 years ago
Posts: 81
Registered: 2 years ago
Posts: 81
Let me just say: this is huge. Karen Geary of Indiana University-Purdue University Fort Wayne (IPFW) has sent me the SQL code which they use to generate the necessary data to import into eLumen. The way I understand it (BANNER experts could explain this better), they:
1. Use the attached SQL queries to generate views against BANNER.
2. The views are then exported to XML document fragments.
(NOTE: if eLumen Collaborative handles your imports, you're done. Send them the XML and you can skip the rest)
3. The XML fragments are combined and validated against the eLumen XSD (contact Sebastian or your support person for the latest)
4. The final XML document is imported into eLumen, probably using their latest (and greatest!) web-based import utility.
Please post your thanks to Karen for sharing these files. Everyone needs them if they have the ability to execute SQL against BANNER. I unfortunately, do not have that luxury [yet], so I use a different method.
THANKS, KAREN!
James Revillini
eLumen Admin / Research Specialist / Webmaster
Tunxis CC
1. Use the attached SQL queries to generate views against BANNER.
2. The views are then exported to XML document fragments.
(NOTE: if eLumen Collaborative handles your imports, you're done. Send them the XML and you can skip the rest)
3. The XML fragments are combined and validated against the eLumen XSD (contact Sebastian or your support person for the latest)
4. The final XML document is imported into eLumen, probably using their latest (and greatest!) web-based import utility.
Please post your thanks to Karen for sharing these files. Everyone needs them if they have the ability to execute SQL against BANNER. I unfortunately, do not have that luxury [yet], so I use a different method.
THANKS, KAREN!
James Revillini
eLumen Admin / Research Specialist / Webmaster
Tunxis CC
Re: Banner SQL for eLumen, compliments of Karen @ IPFW
Feb 25, 2008 04:58AM
Feb 25, 2008 04:58AM
Registered: 2 years ago
Posts: 11
Posts: 11
Re: Banner SQL for eLumen, compliments of Karen @ IPFW
Feb 26, 2008 01:12PM
Feb 26, 2008 01:12PM
Registered: 2 years ago
Posts: 4
Posts: 4
Re: Banner SQL for eLumen, compliments of Karen @ IPFW
Mar 14, 2008 01:02AM
Mar 14, 2008 01:02AM
Registered: 2 years ago
Posts: 8
Posts: 8
Am in the same situation as Jim with the limits on our Banner access. Right now I work with an extract that is provided by a spreadsheet, that I then import into an Access db (provided by Sebastian). Once that db is verified for all its details, I can now do the last step of the import through the data load interface that the Bluefin team (Sebastian?) have built into eLumen. I just did this for the first time, and it worked like a charm. It even caught some possible inconsistencies in our courses-- which were actually the result of having "special topics" courses the titles of which change each semester; the interface caught these and asked to verify that this is what we intended.
Brian
Brian
Admin
Registered: 2 years ago
Posts: 81
Registered: 2 years ago
Posts: 81
Yeah - I, too, noticed that it's very important to be careful during the import when it comes to the special topics courses. Good point.
To expand on this for the general community:
Special Topics courses are courses which are real credit courses but which we are still "trying out" more or less. At the end of the run of the course, it can either be dropped (as in: not offered again) or "promoted" to a real course with a permanently assigned course code, like ABC*123, and title. Here's the hitch as Brian pointed out: one semester, the title of HIS*299 might be "History of Blue Jeans;" next semester, maybe "History of Blue Jeans" was a wild success so it became a regular elective with a code of HIS*140, and now there's a new special topics course with the same course code (HIS*299) but with a title of "History of Waffles." During the import process, eLumen will notice that they both have the same course code and will ask if they should be combined under the new title, "History of Waffles." Clearly, they need to remain as separate courses. So the import tool is really excellent - it puts the control in your hands.
To take this a step further, HIS*299 "History of Blue Jeans" sections from the first semester should probably be combined under the new HIS*140. My understanding is that this functionality is on the way also, which will be great for merging our oldest data in the system with the imported data.
James Revillini
eLumen Admin / Research Specialist / Webmaster
Tunxis CC
To expand on this for the general community:
Special Topics courses are courses which are real credit courses but which we are still "trying out" more or less. At the end of the run of the course, it can either be dropped (as in: not offered again) or "promoted" to a real course with a permanently assigned course code, like ABC*123, and title. Here's the hitch as Brian pointed out: one semester, the title of HIS*299 might be "History of Blue Jeans;" next semester, maybe "History of Blue Jeans" was a wild success so it became a regular elective with a code of HIS*140, and now there's a new special topics course with the same course code (HIS*299) but with a title of "History of Waffles." During the import process, eLumen will notice that they both have the same course code and will ask if they should be combined under the new title, "History of Waffles." Clearly, they need to remain as separate courses. So the import tool is really excellent - it puts the control in your hands.
To take this a step further, HIS*299 "History of Blue Jeans" sections from the first semester should probably be combined under the new HIS*140. My understanding is that this functionality is on the way also, which will be great for merging our oldest data in the system with the imported data.
James Revillini
eLumen Admin / Research Specialist / Webmaster
Tunxis CC
Sorry, only registered users may post in this forum.
Design by James Revillini. Powered by Phorum. Respected by ALL.