Once you have decided on the product, you need to make a plan like every other software installation or adoption. If you are hosting the servers yourself you can go right into the adoption planning.
See a MERLOT collection of ways higher ed institutions are supporting their ePortfolio projects via an online presence.
If you have decided on a product that supports data aggregation, accreditation, or expect to use the system to collect data specific to goals and standards then you need to spend time planning out the back-end web. (See the Concept Map .) This is more administrative than technical as it requires breaking down which specific assignments, taught in which specific classes (and departments) meet which specific goals and standards. The most successful implementations involve many meeting to sort this out so allow time and make sure all the stakeholders are involved. (You can start this before you decide on a vendor.)
Plan your rollout carefully. Some products are specific to classes/departments and are only used internally. Others provide a broad umbrella of use.
Each of these requires a different rollout. All require careful training of the professors and students.
See a MERLOT Collection of vendor products.
It's important to evaluate what each stakeholder will gain from using ePortfolios and being clear about the potential outcomes. Educate the users about why they should embrace ePortfolios - what's in it for them.
Student:
Faculty (if the faculty have their own ePortfolio sites then refer to the listing above):
Department:
Institutional:
See the Mapping, Creating an ePortfolio Culture, and Implementation videos from the ePortfolio Day of Planning Conference, with presentations by Kevin Kelly and Maggie Beers (San Francisco State University).
top of page© 2015 California State University
Concept and design by the Center for Distributed Learning