Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
courses:cs335:spring2013:project_brainstorming [2013/04/17 15:54] – [Graffiti Project] admin | courses:cs335:spring2013:project_brainstorming [2013/04/20 20:31] – [NSF Reports] admin | ||
---|---|---|---|
Line 3: | Line 3: | ||
Work in progress for figuring out team projects. | Work in progress for figuring out team projects. | ||
- | ===== Collegium Project | + | ===== Voluntary Associations |
+ | * Client: [[http:// | ||
+ | * 5 team members | ||
+ | * Goal: Create an interface to make ancient inscriptions easily editable, searchable, and exportable | ||
+ | * public views - searching, viewing, exporting | ||
+ | * administrative views - edit | ||
+ | * Expected skills/ | ||
+ | * Extensions: mapping, dynamic interaction, | ||
+ | * {{: | ||
+ | * Expected audience: ancient scholars and students can use the tool to learn new information about the time period | ||
===== Graffiti Project ===== | ===== Graffiti Project ===== | ||
- | * An alternative search interface to the [[http:// | + | |
+ | * 4 team members | ||
+ | | ||
* Goal: Look at the inscriptions in context of the location | * Goal: Look at the inscriptions in context of the location | ||
* Prototype will be demoed at [[http:// | * Prototype will be demoed at [[http:// | ||
+ | * Extensions: Dynamic searching features | ||
* Extensions: Mapping component | * Extensions: Mapping component | ||
+ | * Extensions: mining data for new information | ||
+ | * relative numbers of text vs drawings? | ||
+ | * size of inscriptions? | ||
+ | * What do you think would be interesting? | ||
- | ===== NSF Reports | + | ===== Visual Course Scheduler |
+ | |||
+ | * Client: Sara Sprenkle | ||
+ | * Team Members: 5 | ||
+ | * Goal: a visual course scheduler that makes it easy for students to visualize possible course schedules/ | ||
+ | * Don't look at [[http:// | ||
+ | * Expected audience: W&L students and faculty | ||
+ | * Expected skills: | ||
+ | * Expected outcome: a tool that students across W&L can use | ||
- | National Science Foundation grant winners have to submit annual reports to NSF. The report describes the various activities and results from the past year. Often winners get to that time, and forget what all they did that year. | ||
- | |||
- | They need a way to enter activities, tag them based on the nsf research.gov | ||
- | categories of where it will get reported in the final report, and any other information | ||
- | about the task, e.g., when complete, who completed it, how many people involved, | ||
- | |||
- | Then when they have to write the report, they could search on particular tags for certain date ranges and get a start of a report of activities that they can then just smooth out into paragraphs. | ||
- | |||
- | It would be a web interface that is private to only those people we are | ||
- | allowed to enter data and create reports, basically the PIs on the grant. | ||
- | |||
- | Categories of activities: | ||
- | * education | ||
- | * research | ||
- | * outreach | ||
- | * publications | ||
- | * outcomes | ||
- | |||
- | I have an example report, but I don't want to post it online. | ||
- | |||
- | Could use similar fields/ | ||