Ohio
High School Athletic Association
Update on the myOHSAA system
During the recent Ohio Interscholastic Athletic
Administrator Association (OIAAA) annual conference
in Columbus, a list of questions regarding the
myOHSAA system was submitted to the OHSAA staff by
athletic directors from around the state.
Those questions are below, along with answers and
interpretations from the OHSAA.
QUESTION:
Is it true that there is no ongoing communication
between the OHSAA and ScheduleStar in regards to the
bridge? Why is this the case? Athletic directors
were told last year that the bridge was on its way,
but now it appears that the public interface bridge
has taken priority.
ANSWER: The groundwork for the bridge – known as the
Application Programming Interface (API) – has begun.
The myOHSAA developer has knowledge of what is
expected and now has the resources available to work
on the bridge. The API will allow events entered
into any third party scheduling software to be
imported directly into myOHSAA. The actual building
of this API will begin following the completion of
the public interface. The OHSAA will survey the
OIAAA membership in the coming weeks to better
understand the expectations of the schools in
regards to the bridge. Of note, the myOHSAA
developer must establish the standards, not a
third-party company. The bridge may not be flawless
at first, but development will be continuous.
Regarding the public interface, the original
direction of the focus group was to make schedules
available to the public a top priority. The bridge
for pushing information is easier to build and will
take approximately 60 days, so it was moved up the
priority list. The next bridge will take twice as
long to build.
QUESTION:
Once the bridge between myOHSAA and ScheduleStar is
built, are there plans for statewide training
sessions?
ANSWER:
Statewide training will not be necessary since the
API bridge will pull data into myOHSAA.
QUESTION:
When the bridge between myOHSAA and ScheduleStar is
built, will it be compatible for other computer
software companies in which we are working?
ANSWER:
Yes, the API bridge will be compatible to all
scheduling software companies.
QUESTION: Will myOHSAA have access for league
commissioners to input schedules and officials?
ANSWER: Yes, that function will be built in the
spring of 2010.
QUESTION:
Will myOHSAA be moving toward one-page officials
contracts?
ANSWER: Yes, that
is
currently in the testing phase and should be
completed in the next two weeks.
For multi-team events, the contracts will be two
pages, but the electronic signature will be on page
one, with the teams listed on page two.
QUESTION:
What is the timeline for new developments with
myOHSAA, such as the decline option, the public
interface, etc.?
ANSWER: The decline option is now active in the
system and the public interface is currently in
development. This interface will most likely be
deployed in two phases. Phase one will allow the
public to view any sport schedule in the system.
Phase two of the deployment will add the community
notification piece for changes made to events.
Several items are in the development queue to allow
schools to better organize as well as move events
from one sport calendar to another. One feature will
allow the user to designate which calendar an
accepted event should populate. Another feature will
allow the user to move a contest from one calendar
to another. Currently the system is set to
automatically create a sport calendar for an event
if the accepting school does not have that sport.
This feature will be disabled as it now causes
events, especially individual co-ed events and
sub-varsity events, to populate several different
calendars. The deployment of these features will
coincide with the deployment of the public
interface, which will allow schools the opportunity
to “clean-up” any misplaced events.
Also in the development queue for late winter is a
redesign of the user management system. This
development will include enhancing and better
defining user access to the different areas of a
school’s interface. Also, allowing access for
central scheduling offices to manage events for
multiple schools. Finally, the unification of login
credentials for those administrators whose
responsibilities cover more than one school.
Transportation scheduling will be added, as well as
student records, which will allow administrators to
create eligibility certificates and rosters.
