Details
- Location: UC Irvine
- Date: June
- Parking:
Working group charge
- Leading up to forum:
- Program (and communicate with presenters)
- Local arrangements
- At the forum, assist with:
- Registration table
- Note takers
Goals, outcomes, objectives of the forum
- Connecting people in their region
- Opportunities to hear how others are using ASpace
- Opportunities to learn new skills in using ASpace
- Opportunities to work together
- To meet more people and find out more tips and tricks
- Large community here using it
Content ideas
- Migration stories –
- Implementation also. can go on for months, fold in new workflows, functionalities
- Find out where other people are, and find out who's at a similar place
Program
Morning program - approx 3 hours
- Maybe first half is presentations - 2 or so longer presentations with Q&A, lightning round of local speakers, discussion session (maybe something like roadmap or digital objects module)
- Morning snacks/refreshments
Topic | Lead | Note | Time |
---|---|---|---|
Welcome message | Host institution | 2-5 minutes | |
Welcome presentation | Program team | Include updates/news - brief | 10 minutes |
Presentation A | Invited speaker | Include q&a | 20 minutes |
Presentation B | Invited speaker | Include q&a | 20 minutes |
Break | 15 minutes | ||
Lightning rounds | Open submissions, accepted speakers
| 5 min each speaker | 45 minutes |
Lightning round q&a | For all speakers | 15 minutes | |
Break | 15 minutes | ||
Discussion | Could we ask other institutions to lead topics?
| 45 minutes | |
Break for lunch on your own | Host institution can guide? | 75-90 minutes |
Afternoon program (approx. 2.5-3 hours)
- Second half is hands on, engaging (sometimes doing, sometimes learning) - sometimes really technical, sometimes not so much (digital objects, spreadsheets to EAD, Hackathon).
- Come up with list of 3-10 things we can do on a rotating basis (list provided in next section)
- During registration, allow participants to choose (rank?) which they’re interested – selection based on response.
- 2.5-3 hours
- Breaks embedded as needed
- End the day with a group closing wrap-up – 10 minutes?
Topics | Lead | Note | Time |
---|---|---|---|
Afternoon activity | Breaks embedded as needed | 2.5-3 hours | |
Closing remarks | Program team | 5-10 minutes | |
Happy hour/mixer | Local consortium, group?? | ? |
Potential topics for afternoon program
- Hackathon
- Advanced training topics
- API
- Plugins
- Digital objects
- Ruby
- etc
- Level 1 introduction to aspace breakout session – if you're interested and know very little, this is the workshop for you
- How you can integrate, digital objects, or use a certain plugin
After forum mixer/reception/happy hour
- Working group selects -- happy hour, bowling, karaoke, etc etc
- Partner with local group to plan?