This page is not restricted in any way by copyright. Please come up with a better way to manage this information and we'll all buy your mousetrap! If someone has a suggestion for keeping the FAQs available/editable, such as a Wiki, please feel free to re-post this information there.
If this list becomes relatively stable and/or organized, it may be included in the Portfolio Rubric site.
General
Q: Where's the Portfolio Rubric site, a sample portfolio, and past students' portfolios?
This will be individualized, based on your academic background. Be sure to weight it towards Performance Technology references. (1/29/07)
Q: Should each page of the portfolio reference SDSU?
Yes, that is a requirement. See this page for other formatting requirements. (1/29/07)
Here is the verbiage that was required for the 541 project pages: (2/5/07)
"Produced by J. Q. Public at the Department of Educational Technology, San Diego State University"
Q: Is it OK to make my Resumé different from the rest of the portfolio?
Yes. The idea is to present yourself well - use your judgement. (2/5/07)
Consider including a link to a printable, smooth copy of your resumé. Keep it up to date. (2/5/07)
Q: What's the best way to present my Artifacts?
Consider making a PDF of each page and/or artifact so users can download (and print) a clean copy, in addition to viewing the raw artifact. (1/29/07)
Several members of the class voiced the desire to set the stage for the artifact (as opposed to just "Artifact: Link"). Discussion settled around a short phrase describing what the artifact IS and the context in which it was prepared. Example: "Powerpoint presentation developed for EDTEC 684, Project Management: Link". The reflection will then expand upon the context and content as it relates to the standard in question. Example: "This powerpoint demonstrates some of my best work in communications."(1/29/07)
Another good way to present an artifact (from a pedagogical standpoint) is to put a small graphic of the artifact with the short description.
Since each Standard references a skill, consider including photos that highlight each skill as a way to "dual code" your intent on that artifact's page. (2/5/07)
Q: How much personalization should I put in front of a prospective employer? Maybe they won't like some of the things I like.
That's always a balance. Remember this portfolio is being developed to fulfill an academic requirement to show the reviewers what you've absorbed from your academic experience. So slant it in that direction until your presentation date. Then you can execute pragmatic tweaks and convert it into a professional portfolio. (2/5/07)
Intellectual Property
Q: What about copyright?
Copyright notice: should include one on every page of the portfolio, and generally everything you put on the web. (1/29/07)
Q: What should I do if some of my artifacts include classified or sensitive information?
Employer references: If you'd like to include some work that is still privileged to an employer or company, consider screen shots (get permission). It is acceptable to include testimonials and references from employers that address the aspects of your work that can't be included. (1/29/07)
Accessibility
Q: Should we include an accessibility check on every page of the portfolio? Or should we just check the portfolio for accessibility and build it in?
???
Q: What about browser compatibility?
Be sure to test your portfolio in several browsers. Sometimes your pages will display with incorrect formatting. (2/5/07)
Privacy
Q: What should I consider when including a personal portrait on my Bio or Resumé page?
Your personal picture: color will inspire visions of the 60s and 70s, black and white screams "50s"! (1/29/07)
Something else to consider is anti-discrimination regulations associated with Resumés - you may not be allowed to include a photo for some employers. (2/5/07)
Be cautious about putting personal information on your contact page. Email is probably good (scrambled?), and a PO Box if it'll be used for professional mailings. Home address and telephone number is probably not necessary, or even a good idea. (1/29/07)
