Import Errors

A couple issues I encountered yesterday loading XML files on Blackboard Vista 8.

siapi output says:

error invoking method in adapter, message is: cvc-complex-type.2.3: Element ‘extension’ cannot have character [children], because the type’s content type is element-only.

Means the wrong type between luminis and ims was used. I created a file which sets the import type based on the name of the file. For the luminis type, the persons records are in persons1.xml. For the ims type, the persons records are in ims_users1.xml.

webct.log says:

Message is : Authorization denied

User trying to import the file must be an institution administrator. I probably created the import user but did not enroll it as an admin. What I get for moving too fast.

The following were added 26-MAY-2010…
webct.log says:

error invoking method in adapter, message is: Deployable component is not enabled

This one is actually accurate. The Luminis Message Broker settings need to be changed so Enabled equals true. Probably the other settings are also back to defaults. This happens after most Service Pack upgrades.

webct.log says:

The learning context represented by the lc_id and lc_source parameters is not within or equal to the learning context represented by the glcid parameter. This may cause problems if the learning contexts in the XML do not specify a parent or cannot be imported directly under the instituion

The XML file only contained 1 person and 1 member record. So this must be about the sourcedid.source and of that file. The student was enrolled in the section, so I guess maybe the error can be ignored?


Gave a former coworker, Stu, from my Valdosta State days a heads up about a complaint my brother heard from a close friend of his. Stu is working with Sakai these days at Georgia Institute of Technology. He made an interesting comment:

It would be great to have all the energy your team puts into Blackboard be put into Sakai instead.

One of the unknowns which always seems to come up in talking about Sakai or Moodle is hiring a development staff. How many programmers we need depends on how much customization we will need to implement. Certainly finding the programmers is another problem. A large fear is we’d need 10 programmers and years to implement all the features people insist are critical. People need to be told. “No, you will have to live without that feature,” which would be very cool… However, it would be like your ISP telling you, “Sorry, we turned off port 80. You will have to live without it.” Finding the balance between features we can abandon, features which would need to be created pre-go-live, and features we can post-go-live? Difficult enough when you have 15,000 users. It seems more than 10x harder with over 150,000 users.

Surely people have cracked this nut?

Read and post comments | Send to a friend