ABCDEFG
1
Amgen Scholar Program Key Dates*
2
February 1st, 2018Application Deadline
3
May 29th, 2018Program Start date
4
July 11th, 2018Program End date
5
*Program dates are generally consistent every year. Platform should be ready for the 2019 cycle.
6
7
Dates below represent final product dates.
8
9
Contract and Platform Specs finalized no later thanMarch 31stApril 10 2018
10
Full UX/UI design including high quality demoAugust 31st
11
12
Platform timelines for Scholar usesDelivery DatesDays from start
Work days (excluding weekends and public holidays)
13
14
Development Start Date4/1/2018
15
Need to be able to add content to the catalog from edX & content partners9/1/2018153108
16
Users need to be able to utilize the catalog and create pathways1/1/2019275189
17
Users need to be able to complete their prelab work on the platform (pathways & simulations), use the social network to find mentors4/1/2019365251
18
Users need to be able to utilize the platform, data for gamification needs to be tracked6/1/2019426294
19
Users need to be able to create case studies from their research8/1/2019487337
20
Platform is fully functional and publicly available to all users9/1/2019518358
21
22
*ABE Teachers will be use the platform all year so there aren't any specific dates associated with them. Plan will be to make a publicized secondary school launch in time for September 2019 school year even though teachers will be using it earlier.
23
24
We would obviously prefer earlier dates but these will allow us to meet our obligation to the Scholars. I'm sure some features will be added/removed as we dive deeper as well.
25
26
Platform features and timelines
27
28
Frontend
29
LabX Frontend UI will reflect the UI designed by the creative team (this may vary from the current UI which was constructed for the grant)
30
Three portals: Educator, Student, Student Researcher
31
32
Authoring and Permissions
33
Different account levels (read only, read/write accounts)
34
35
Library Catalog
36
Faceted search filtering: Ability at the administrative level to create new fields for faceted search
37
Ability to add metadata to the content for search and recommendation engine
38
Recommendation engine for the catalog (e.g. recommendations based on content metadata)
39
Ability to search, filter, and view content at the asset level
40
Ability to add an asset from the catalog into a pathway
41
Ability for users to add content to the catalog
42
Ability to utilize content from edX & non-edX publisher sites (e.g. Khan Academy, OCW, OER etc.) without leaving the LabX environment
43
Ability for users to control visibility of their added content (e.g. "public" to make it discoverable by catalog search vs. "private" to make it accessible only via direct link)
44
All assets should have relevant citation data, authorship data, associated with each asset
45
46
Pathways
47
Ability to combine assets into a pathway
48
Ability to combine multiple pathways into a larger pathway
49
Ability to add interstitial material (either text or video element) to provide context around pathways
50
Ability to add metadata to a pathway
51
Ability to clone pathways for editing
52
Editing pathways should allow you to add, delete, and reorder content within the pathway
53
Ability to share pathways (same visibility settings as an asset)
54
Ability to link directly to a pathway (this is connected to the "private" setting on the visibility mode)
55
56
Simulations, Interactives and Tool Integrations (LTI)
57
Ability to integrate LTI tools into the platform (all simulations and interactives that we build will be LTI)
58
All LTI tools should be treated as assets in the catalog which will allow users to integrate them into pathways
59
60
Content Flagging and Removal System
61
Ability for users to flag content (e.g. copyright violations, accessibility shortcomings, TOS violations)
62
System in place for flag monitoring and content removal
63
64
Digital Portfolios
65
Lightweight templated authoring tool which allows for users to create new content (e.g. a templated case study)
66
These digital portfolios should be treated as a distinct asset type within the catalog and have the associated asset functionality
67
Digital portfolios should also be integrated (as an option) into the user profile and available through the public facing page
68
69
Global Discussion Forum
70
Threaded discussions
71
@ mentions with connected user notifications
72
Ability to follow threads
73
Ability to follow users
74
Content tagging for threads allowing them to be searchable
75
Flagging & removal system for threads
76
77
Bulletin Boards
78
Ability to posts volunteer opportunities, jobs, etc.
79
Restricted user access for write permission to bulletin boards
80
81
User Profile
82
Public facing user profile on a stable url which can be linked externally (linkedin, academia.edu, etc.)
83
Ability to integrate other social networks (LinkedIn, Twitter, Facebook, etc.) into their LabX profile
84
Ability to customize which elements users want public with various fields predefined (e.g. badges, pathways completed, # of mentees, etc.)
85
86
Messaging
87
Messaging system once appropriate permissions are grant
88
1:1 Direct messaging
89
Live chat (including group chat)
90
Video chat within the platform
91
92
Social Network
93
Social networks connected to user profiles
94
Different social networks, all individually searchable (e.g. "Current Scholars", "All Scholars, "Teachers", etc.)
95
Ability to add & remove yourself to different groups (e.g. add yourself to "Available to Mentor" group)
96
Ability to request membership connection for messaging/mentorship, auto-generated responses based on acceptance/rejection
97
98
Notifications
99
Global notification system (messages, emails, progress status, etc.)
100
The notification system should be interactive, allowing users to directly access the relevant notification