1)[WARN ] Failed to write node: <SectionMeeting xmlns="file://SIS/SectionSpokeData.xsd"><SECTIONMEETINGSISKEY>22141912_21940187</SECTIONMEETINGSISKEY><SECTIONSISKEY>22141912</SECTIONSISKEY><MEETINGTYPESISKEY></MEETINGTYPESISKEY><MEETINGTYPENAME></MEETINGTYPENAME><SECTIONMEETINGSTARTDATE>2010-08-23T00:00:00</SECTIONMEETINGSTARTDATE><SECTIONMEETINGENDDATE>2010-09-24T00:00:00</SECTIONMEETINGENDDATE><SECTIONMEETINGDAYSMETPATTERN></SECTIONMEETINGDAYSMETPATTERN><SECTIONMEETINGHASINCOMPLETEMTGPATTERN>True</SECTIONMEETINGHASINCOMPLETEMTGPATTERN><SECTIONMEETINGREQUIRESATTENTION>True</SECTIONMEETINGREQUIRESATTENTION><SECTIONMEETINGREQUIRESATTENTIONREASON>Invalid meeting pattern</SECTIONMEETINGREQUIRESATTENTIONREASON><TERMSISKEY>10-11 300</TERMSISKEY><SECTIONMEETINGSTARTTIME>00:00:00</SECTIONMEETINGSTARTTIME><SECTIONMEETINGENDTIME>00:00:00</SECTIONMEETINGENDTIME><ROOMSISKEY>On-Campus_PEARCE_413</ROOMSISKEY></SectionMeeting>; The 'file://SIS/SectionSpokeData.xsd:MEETINGTYPESISKEY' element is invalid - The value '' is invalid according to its datatype 'http://aais.com/schema/7.4.0/ATE/AstraTypes:nonEmptyString' - The actual length is less than the MinLength value.

Indicates there is a section being imported that doesn’t have a meetingtype, which is required, and that it can’t build the meeting record without it. The correction is to add a meeting type to the data., or not. But the meeting won’t be built without a meeting type.

 

2)17:02:25,453 Astra.Business.Processors.ATE.Framework.Engine.AteJobRunContext [WARN ] Failed to write node: <Instructor xmlns="file://SIS/SectionSpokeData.xsd"><INSTRUCTORSISKEY>0000000000</INSTRUCTORSISKEY><SECTIONMEETINGSISKEY>22127155_40104900</SECTIONMEETINGSISKEY><PERSONSISKEY>0000000000</PERSONSISKEY><PERSONFIRSTNAME></PERSONFIRSTNAME><PERSONLASTNAME></PERSONLASTNAME><INSTRUCTOREMAIL></INSTRUCTOREMAIL><TERMSISKEY>10-11 300</TERMSISKEY><PERSONMIDDLENAME></PERSONMIDDLENAME><PERSONSUFFIX></PERSONSUFFIX><PERSONEMAIL></PERSONEMAIL><CONTACTINFORMATIONEMAIL></CONTACTINFORMATIONEMAIL></Instructor>; The 'file://SIS/SectionSpokeData.xsd:PERSONFIRSTNAME' element is invalid - The value '' is invalid according to its datatype 'http://aais.com/schema/7.4.0/ATE/AstraTypes:nonEmptyString' - The actual length is less than the MinLength value.

Indicates that there is a null first name for an instructor. Since he’s populating the file with an ID value “0000000000” the system expects that there will be a name associated with the instructor id. The options here would be to remove the bogus ID, or fully fill out an instructor record. Either way, the system is warning because it’s getting an ID value and nothing else for an instructor assignment like first and last name, etc.

 

3)17:04:12,635 Astra.Business.Processors.ATE.Framework.Hubs.BasicImportHub [WARN ] SectionMeeting '22127175_21938081' requires attention: Invalid meeting pattern

Indicates that for this meeting, something is missing in regard to meeting pattern. This is the normal message for section meetings that don’t have meeting patterns including daysmet, start or end time, etc. The meeting is marked as “Requires Attention” and imported into Astra.

4)Skipping row: '' is not a valid 'SisKey' when processing MeetingType from SectionMeetingHub: [SECTIONSISKEY = '2012_02_TRL  106  05                  ' SECTIONMEETINGSISKEY = '201202TRL  106  05                  1' MEETINGTYPESISKEY = '' MEETINGTYPENAME = '' SECTIONMEETINGDAYSMETPATTERN = 'MTWRF' SECTIONMEETINGSTARTTIME = '1900-01-01T08:00:00' SECTIONMEETINGENDTIME = '1900-01-01T17:00:00' SECTIONMEETINGSTARTDATE = '2012-03-12T00:00:00' SECTIONMEETINGENDDATE = '2012-04-20T00:00:00' ROOMSISKEY = 'BAIN_000_00000' SECTIONMEETINGHASINCOMPLETEMTGPATTERN = 'N' SECTIONMEETINGREQUIRESATTENTION = 'N' SECTIONMEETINGREQUIRESATTENTIONREASON = '']

Indicates that for the section no meeting type is associated in the SIS.  Either the Meeting Type needs to be added in the SIS to the section or we can modify your spoke file to add a meeting type of “General” to these sections.

5)[WARN ] The hub 'SectionMeetingInstructorHub' has been deprecated.  Please update your spoke file to use 'SectionMeetingInstructorHubEx' instead.

 

We changed this in the ATE engine and letting you know that the section Meeting hub has changed.  This still brings in instructors and sections and can be ignored.