<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://sifzone.com/sifzonecs20085/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Search results matching tag 'best practices'</title><link>http://sifzone.com/sifzonecs20085/search/SearchResults.aspx?o=DateDescending&amp;tag=best+practices&amp;orTags=0</link><description>Search results matching tag 'best practices'</description><dc:language>en-US</dc:language><generator>CommunityServer 2008.5 SP1 (Build: 31106.3070)</generator><item><title>SectionInfo - Duplicate RefID's </title><link>http://sifzone.com/sifzonecs20085/forums/p/1132/1654.aspx#1654</link><pubDate>Fri, 05 Mar 2010 13:06:53 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:1654</guid><dc:creator>kdoore</dc:creator><description>&lt;p&gt;It seems that for SIF1.5r1, schoolYear was not mandetory for SectionInfo.&amp;nbsp; That being the case, a SectionInfo refID had to be unique for every SectionInfo record published.&amp;nbsp; I am now finding that with Sif2.x, the powerschool agent is publishing SectionInfo records where there is a duplicate refID for sections that have a different SchoolYear value.&amp;nbsp;(I have also discovered the same thing for TermInfo) &amp;nbsp;If the PSAgent was able to filter publishing records for SectionInfo, SSecE so it only published the current year&amp;#39;s data, it wouldn&amp;#39;t be as big of a&amp;nbsp;problem...but it is causing problems for the subscribing agent.&amp;nbsp;&amp;nbsp; The SIF spec doesn&amp;#39;t seem to give any clear guideline on the use of SchoolYear as the distinguishing identifier for SectionInfo records.&amp;nbsp; From what I can tell, this only seems to occur for a small percent of the SectionInfo records for each district where I&amp;#39;ve encountered this.&amp;nbsp; Is this how SectionInfo is supposed to be published, or is this an error in the way the PSAgent is handling sectionINfo?&lt;/p&gt;</description></item><item><title>Re: Publisher/Subscriber Expectations</title><link>http://sifzone.com/sifzonecs20085/forums/p/934/1126.aspx#1126</link><pubDate>Sun, 12 Jul 2009 21:35:27 GMT</pubDate><guid isPermaLink="false">21093a07-8b3d-42db-8cbf-3350fcbf5496:1126</guid><dc:creator>andy</dc:creator><description>&lt;p&gt;You are seeing things correctly. Subscribers need to support querying for all data of interest to them when they first enter a zone. After that, if they are subscribed, they can stay up to date by listening to events.&lt;/p&gt;
&lt;p&gt;A well-written subscriber agent should have the capability to resynchronize at any time, so that if the administrator of the agent thinks that it is out of date, it can sync up. In addition, a good subscriber agent should expect to resynchronize every year at the start of school. There is no guarantee that SIF events alone will be able to keep the subscriber in sync during end of year processing in the SIS, so the subscriber should plan to resync after that is complete.&lt;/p&gt;
&lt;p&gt;A subscriber should not unregister when it shuts down. If it does, any events that it could have received during that period will be lost.&lt;/p&gt;</description></item></channel></rss>