As Jim knows, this has been one of my projects going back quite some
time - and no factors to be included keep popping up, nevertheless...
We decided to integrate what we felt to be "best of breed" regardless of
vendor. Like Jim we settled on finalsite as the landing point. We have
ended up adding more "portals/constituencies" than I anticipated as
other needs appeared.
Advice - get some sort of exclusive, cross data source identification
system running first. Everyone now has a unique ID that works across
roles so that if an alumnus gets hired as a faculty member, and is also
a parent, they only have one ID. This simplifies the process a great
deal.
Advice 2 - define your God system(s). What system is going to be
authoritative about whom. In our case - HR about anyone receiving
paycheck (even if faculty), SIS about currently enrolled students and
their parents (if not on payroll), Advancement about Alumni, etc.
We are concurrently working on a public face (finalsite), SIS and
Admission (PCR Educator), Advancement (RE7), Payroll/HR (Paychex),
Authentication (AD/LDAP), Business Office (MAS 200) integration that
moves slower than I'd like but in the right direction. Requires
significant willingness on the part of the vendors to "play nice." Some
play nicer than others - seems to be a function of scale. The larger the
organization, the less the perceived need to help out.
Most of this is still batch oriented but we do have some automated
linkages working.
Details available to anyone who's interested.
Dan
Daniel F. Hudkins
Director of Instructional Technology, Director of Information Systems
Ethics Teacher, Advisor Class of 2011, JSA Teacher/Adviser, Assistant
Varsity Softball Coach
500 Saratoga Ave.
San Jose, CA 95129
(408) 345-9631
-----Original Message-----
From: A forum for independent school educators
[mailto:ISED-L@LISTSERV.SYR.EDU] On Behalf Of Jim Heynderickx
Sent: Friday, December 19, 2008 9:37 AM
To: ISED-L@LISTSERV.SYR.EDU
Subject: Online Unification and Synthesis
Hi, All
I've been working away for about 18 months now on a multi year
project, so it's probably time for a report.
I'm working on a way to improve communication and work flow via online
portals and services. Currently, we're migrating to a full Finalsite
implementation as a framework portal system, with unique "landing
pages" for different constituent groups. We're thinking critically
about systems that separate instead of unify the community-- such as
email systems used only by some constituents, and web pages built
primarily for other community members. One objective is to have a
"one stop shop" for communications and services.
One concept underlying our work is that information can have greater
value and accuracy if appropriately shared with larger groups.
Another premise is that unified tools working off of a single user and
demographic lists can be more effective than stand-alone applications
with bigger feature sets.
Next stages include a core student information system that meshes well
with the online portal, integrated email systems, and more windows of
unique information and services shared with constituents online
instead of via specific software clients or "only on campus" tools.
It's been an interesting process so far-- I've had to rethink a lot of
concepts to try to envision stable and reliable systems that may
hosted online instead of run on campus. It's also been an opportunity
to think about serving an increasingly diverse and user-owned and
user-centric technology environment, as opposed to a standardized,
locked-down or domain-controlled environment.
There's many concepts at work here, but I might ask just one question
of others at this point. How many others are working on these
concepts, and how do you feel about your online synthesis so far?
Others are already further down the road with online student
information systems and online portals for parents, students, faculty
and staff, and I'm interested in reports of progress and
complications.
Thanks, and happy holidays to all!
Jim Heynderickx
Director of Technology
American School in London
[ For info on ISED-L see http://www.gds.org/ISED-L ]
Submissions to ISED-L are released under a creative commons,
attribution, non-commercial, share-alike license.
RSS Feed, http://listserv.syr.edu/scripts/wa.exe?RSS&L=3DISED-L
[ For info on ISED-L see http://www.gds.org/ISED-L ]
Submissions to ISED-L are released under a creative commons, attribution, non-commercial, share-alike license.
RSS Feed, http://listserv.syr.edu/scripts/wa.exe?RSS&L=3DISED-L
