Posts

Showing posts with the label Notes

Micro Learning - The best microlearning examples to inspire you for 2021 (Elucidat)

  Greany, K. (2019, September 7).  The best microlearning examples to inspire you for 2021 . Elucidat.  https://www.elucidat.com/blog/microlearning-examples/ How can I use this?  explain rationale for using micro learning simple framework for realizing micro learning  situation, seek, share other 20 seconds of theory,  3-4 in-depth demos,  a “how to”  some expert tips 6 example frameworks  Why must I use this?  facilitates design  has concrete examples  When will I use this?  ideal for supporting writing project / generic .. presentation project 

Micro Learning - 6 Reasons Micro-Learning Will Make a Huge Impact In Your Organization (eheld)

Image
  eheld. (2017, July 12).  6 Reasons Micro-Learning Will Make a Huge Impact In Your Organization  [Business].  https://www.slideshare.net/eheld/6-reasons-microlearning-will-make-a-huge-impact-in-your-organization?qid=c124334e-8a93-413b-bf19-26e6187861b3&v=&b=&from_search=6 How can I use this?  explain rationale for using micro learning differentiating between training & performance support  Why must I use this?  cost savings  nature of today's learners / workers  effectiveness for promoting repeated use  When will I use this?  writing up rationale for using it  reviewing persona of today's students / trainees 

Micro Learning - Micro Instructional Design for Problem Based and Game Based Learning

Image
  Andy Petroski. (2013, December 18).  Micro Instructional Design for Problem-Based and Game-Based Learning  [Education].  https://www.slideshare.net/apetroski/micro-instructional-design-for-problembased-and-gamebased-learning?next_slideshow=1

File Naming Standards - Notes (Research Data Management at Princeton)

Image
Cowles, W. (n.d.).  Research Guides: Research Data Management at Princeton: File naming and structure . Retrieved May 31, 2021, from  https://libguides.princeton.edu/c.php?g=102546&p=930626 Key takeaways  be consistent  avoid special characters  use  capitals and underscores instead of periods and spaces  use date format YEAR / MONTH / DAY -  ISO 8601 include a version number include naming convention in data management plan (and commonly used docs - i.e. agenda - for quick reference)  Interesting is how this article suggests the following and how that compares with the Pode article Elements to consider  Date of creation (putting the date in the front will facilitate computer aided date sorting) Short Description Work Location Project name or number Sample Analysis Version number    

File Naming Standards - Notes (Pode, Staffing Industry Analysts)

  Pode, A. (2014, December 21).  Probably the best file naming convention ever . Staffing Industry Analysts.  https://www2.staffingindustry.com/eng/Editorial/Archived-Blog-Posts/Adam-Pode-s-Blog/Probably-the-best-file-naming-convention-ever Again, Sharepoint focus  based on work by Anne Thompson, U of Edinburgh 7 recommendations  File name?  File name lettering?  use Capital letters / not spaces  do not use underscores or dashes i.e. 450Agenda  vs 450_Agenda rationale? removing underscores shortens file name, use of capitals differentiates words in file name  File name length? Short is the word Keep files names short, but meaningful   i.e. 450AgendaMidterm vs  450AgendaonUpcomingMidterm File name date? Back to front start back to front (year, month, day) i.e.  20210314450AgendaMidterm   vs  14Mar 2021450AgendaMidterm helps with cataloguing and finding files by date File name elements?  Order ...

File Naming Standards - Notes (University of Maryland Baltimore)

Center for Information Technology Services. (n.d.).  File Naming Standards . University of Maryland Baltimore. Retrieved May 31, 2021, from  https://www.umaryland.edu/office365/sharepoint/file-naming-standards/ Key points do not use special characters ( " # % * : < > ? / \ |) do not use spaces (spaces will be converted to the characters "%20" in hyperlinks) do not  use   version numbers in file names (versioning may be available automatically in Google and/or Sharepoint - viewing history)  do not separate words in file names with underscores or dashes (underscores "_" or dashes “-“) check properties of doc (author, title, date, etc.) for accuracy (while hidden they can and will still be used for search purposes) avoid using dates in file names (typically done by default - created by, modified by); only use them if you have two docs with the same name (only relevant for Sharepoint) caution - aimed at Sharepoint users