15
ePortfolio Task Group

Presentation to fact2 april

Embed Size (px)

DESCRIPTION

Findings of the ePortfolio Task Group

Citation preview

Page 1: Presentation to fact2 april

ePortfolio Task Group

Page 2: Presentation to fact2 april

What we’ve learned

Page 3: Presentation to fact2 april

What we’ve learned

Page 4: Presentation to fact2 april

What we’ve learned*Interoperability/portability will be key to the success of a system-wide implementation*The platform must be adaptable so that it can be used in different ways based on the needs of campuses and programs.*Integration with other systems will allow students and instructors to transfer content easily.*The platform is extremely important.

Page 5: Presentation to fact2 april

What are the benefits of a system wide platform?• Students would be able to have one ePortfolio in which to store

and display their work, while attending classes at numerous institutions within the SUNY system.

• Students transferring between institutions, will have a continuous record of their work.There would be no need to transfer artifacts or portfolios between systems.

• Training and support would be more consistent and should be more cost effective than if multiple systems are in place.

• System wide analytics would be much easier to accomplish if all of the portfolios were housed in one location in a shared database.

• Migration to a new architecture would be easier in the future should a new system be desirable.

• Standards are easier to enforce and integration points such as institutional artifact uploading would be easier to develop.

Page 6: Presentation to fact2 april

What might impede the ability to create a system-wide ePortfolio?• a. Several of the SUNY programs are

committed to the use of a particular platform, and many platforms do not use a standard format that would allow for interoperability.

• b. Varying needs of specific programs, for example: Education and Health Science.

• c. Emphasis placed on one aspect of an ePortfolio, which is in opposition to another emphasis.

Page 7: Presentation to fact2 april

Technical requirements• Interoperability and cross-platform capabilities• Supports lifelong learning--use after graduation • Supports visual customization by the various institutions

(branding)• Portfolios can be archived and/or exported in standard

formats for permanent records• Multi-institutional (support separate institutions on one

instance)--this would allow for instructors and students across SUNY to share ePortfolios and best practices more easily. It would also insure portability.

• Integrates seamlessly with an LMS (or is built into an LMS)--allows for seamless transfer of artifacts

Page 8: Presentation to fact2 april

Standard formats for interoperability

• LEAP2A: Mahara, Pebblepad, & Medbiquitous eFolio Connection (for Medical Schools)

• IMS Global: Chalk & Wire, Mahara, TaskStream, Pathbrite, Pebblepad

Page 9: Presentation to fact2 april

Special concerns for Education• edTPA integration: Chalk & Wire,

Data180, Foliotek, ILAT, Live Text, Nuventive, Task Stream, TK20 (Digication Fall 2013)

• Students can upload directly

Page 10: Presentation to fact2 april

Functional requirements• Repository managed by the user: Artifacts may be discrete or

packaged• Allows for multiple file formats including video, audio, images

and text. • Can display embedded media from within the system as well

as external media (Uses IMS Global Standards)• Provides the ability to create multiple blogs, and other

methods for recording reflections• Includes a resume builder• Allows users to create multiple portfolios (pages, views, etc)

for different purposes• Access levels can be set independently for every portfolio

page• Provides for comprehensive feedback

Page 11: Presentation to fact2 april

Continued functional requirements• Individuals can repurpose artifacts--appropriate them

into various purposes for various audiences.• Allows for the creation of templates• Provides for user customization/personalization• Will support the collection and display of Continuing

Professional Development activities and hours• Will support badging• Will display external content including RSS feeds, and

Google Drive documents• Provides methods for peer-reviewed and instructor

comments and feedback

Page 12: Presentation to fact2 april

Continued functional requirements• Provides support for displaying a variety of goals including

academic, career and personal.• Supports a way of recording and reflecting on co-curricular

activities including internships• Support the needs of all SUNY programs that require an

ePortfolio (able to be used in any context and for any program)

• Provides for the display of awards and certificates• Institution should be able to push out certified artifacts

into the student’s repository• Flexible and has ease of use• Plugins or other customization features that would allow

for things like facebook likes, embedding twitter feeds, linkedin, etc

Page 13: Presentation to fact2 april

What are the best methods for developing a system-wide environment that supports and encourages the use of ePortfolios?

• Faculty should be encouraged to use ePortfolios for their personal and professional growth as well as for Promotion & Tenure

• ePortfolios should be accepted and used in the admissions process• The system should work for all programs including Fine Arts,

Education, Engineering, Health Services, Medical Education, Business• The use of ePortfolios should be built into the curriculum: first year

experience,...• Advisors should be encouraged to help students build a career

portfolio• Teach education students how to use them in their K-12 classrooms—

require lesson plans that include the use of ePortfolios• Develop a culture that fosters reflective practice• Develop an environment that supports the use of ePortfolios across

the curriculum• Encourage students to take ownership of their ePortfolio and their

learning

Page 14: Presentation to fact2 april

Other questions we tackled• What training will be necessary to insure best practices?

• How can the system encourage research in the field of ePortfolios?

• What structures will the system put in place to support the use of ePortfolios for lifelong learning?

• What needs to be done to encourage the evaluation of ePortfolios in the Admissions process?

• Why and how can SUNY encourage the use of ePortfolios in the K-12 public schools?

Page 15: Presentation to fact2 april

What next?• Formation of a SUNY-wide Community of

Practice• Issue an RFI to consider our options• Develop a plan for building the use of

ePortfolios into Open SUNY for PLA, transfers, and teaching & learning across the system—particularly in General Education courses

• Include teaching with ePortfolios as part of the education curriculum.