Film Findr Pre-Proposal

Background

There are dozens of movies released every year – far more than any single person (or even a group of people) can expect to keep up with. While there are websites such as IMDB that allow users to search for facts and information about movies, these sites do not also look for relationships between movies. Having access to such a database would provide both academics and film enthusiasts with a new resource for examining connections between movies – from the words in similar scenes to the colors that were used across a movie.

In such a system, a key feature is the ability to search and navigate easily. By including as many relations as possible for users to search on, we can guarantee that there will be a wealth of information that becomes available to them for analysis. Similarly, making it easy for users to navigate through the database (and even upload films that they wish to be able to analyze) will make the database more accessible and applicable to everyone. Both of these features will make the online database invaluable to anyone who has the desire to examine connections and parallels between different films.

Executive Summary

This project has already been started as a web application and that is certainly the best medium for it, due to the fact that it will provide the most people access on the most devices. At the moment, the data and search functionality are displayed through simple web pages, which could be brought more to life with a reactive interface that would better present the information pertinent to a user’s search, while still allowing them to view more information if desired. By removing visual pains of searching through the data, there is an increased chance of the tool being useful as desired.

There should also be a feature for uploading new movies, which would allow the server to automatically pull data from movie files (screenshots, subtitles, etc) and could even have the images taken analyzed by a computer-vision program to retrieve information such as objects in the image from them, allowing for more meaningful searches and relational matches. By automating the submission process, we would lower the work required to submit films to the system, making users more likely to submit films (thereby expanding the breadth of the database).

Viability Analysis

As with any cloud-hosted database, the cost of hosting will increase with the number of movies that are held in it. The images themselves would be the largest files, ranging from 2KB to 10KB after compression. Even with such compression, however, there will be cost constraints associated with the number of movies that can be held in the database while operating within a reasonable budget. Another constraint will come from the use of any sort of remote library for image analysis. The majority of libraries that will be able to successfully analyze the images for metadata in the database will have some cost associated with them (see the Google Vision API as an example). Finally, we may also wish to consider creating a local application that users could download for parsing movies so the size of files that have to be uploaded are drastically reduced in size.

Risks and Rewards

This project has one primary issue that comes with it, which is the legality of the use of movies. The movie industry is known for aggressively defending its copyrights and going after people for violating them. Because the database uses only screenshots, however, this hopefully should  not be an issue with fair use laws. Having users upload movies themselves might be another grey area legally, due to the sharing of content that (in most cases) was purchased for personal use. There is a good chance it would be safe under fair use, but it is certainly a grey area that must be examined and addressed if necessary. This would certainly need to be looked into.

The benefits of the project, on the other hand, are significant. Having access to a massive relational database of movies with extra metadata associated with them will allow film buffs and scholars to make connections between plots and scenes where they might have not been able to before. This could be a massive boon to the film studies field as it could provide insights that were never before considered.

Closing

The film database that is being created will certainly be a revolutionary tool for scholars and film buffs everywhere. To make it truly useful, however, it needs to have comprehensive search and uploading features that are accessible through a friendly and reactive interface, all of which this project will add to the database. All of our team members are very interested in furthering such a database’s accessibility, because there is such a wealth of information that such a project will add to the field of film studies, and we are excited by the possibilities that it could unleash.

Team Members

Eric Marshall

Cole Whitley

Stefano Cobelli

Andrew Capuano

Web Interface for Excurvant Pre-Proposal

 

Background

In the modern world, everything we do can be shared with our friends, family, and acquaintances through the use of social media. This allows us to share ideas and thoughts seamlessly with those we care about. There currently is no good place, however, to discover, book, and share travel ideas. This is where Excursion finds its market. Creating a socially-interconnected travel platform would allow people to share their travel plans and ideas with their friends and family. Essential to such a system is an easy-to-use uploading feature and efficient backend. Thus, the true problem to be solved in this project is the creation and streamlining of a system that is friendly to users as well as quick and responsive.

Executive Summary

For Excurvant, as with any social platform, one of the most important features is accessibility to its users. Even further, in the modern world, smartphones and laptops are ubiquitous. The one application that is common to all of these devices is the web browser. Because this is an application that will need to be accessible on all sorts of devices, the clear choice for a platform is a web app, allowing any browser to use the application (therefore gaining the largest possible audience). As has been seen with previous social applications, one of the hardest parts of such a platform is gaining users.

To make it as easy as possible for someone to sign up, the application will allow users to authenticate through common social accounts, such as their existing Google or Facebook account. This will make it easy for new members to join and begin sharing with their friends/family. To create the necessary infrastructure for such a web app, we will need to create a backend (Node.JS was specified) that includes a server for the application itself, as well as a database for any trips and sharing relationships created by the application. This will allow the application to manage and track relationships between its users, perhaps even suggesting who they might like to share trips with or create a feed of users who have shared similar trips. On the UI side, we will need to design an interface that is fast and easy to use – most likely meaning that we will have to make several iterations of the user interface to improve on each iteration.

Viability Analysis

The tasks involved with this project are certainly attainable, but it is by no means a minor project. The design of a user interface alone is no small feat, and there will need to be a significant infrastructure put in place to handle the requests associated with a reactive web application.

The first task will be creating a server with which we can serve the necessary javascript and html for an application – this should be fairly quick to set up, however, we will also need to decide on and set up a database that is scalable for the application once it reaches full load which could take longer to do. Second, we would need to set up an API (Application Programming Interface) for communicating between the web application and server from a user’s browser. This will take a good deal longer as the use cases for the product will need to be flushed out and pathways designed/created to serve the application. The next major task would involve designing the user interface that can be then created in a given Javascript framework – this is almost guaranteed to be the longest and most involved as it will involve designing a user interface and iterating on each design to improve usability.

The project also calls for improving the user experience. Through classes we have taken at Bucknell (HCI, Mobile Development) and our own personal findings, we should be able to design a user interface that is practical, easy to use, and impactful.

Risks and Rewards

This is a unique application as there is currently no popular application that allows its users to plan and share trips with friends and family, which could aid people in the planning of future vacations and trips. On the other hand, as is true with any data-based application, it could open the users to potential theft if their trip data is gained by a malicious party, so any data must be kept securely wherever it is held, as well as transmitted in a secure fashion.

Another risk with this application that can be seen with essentially any social media app is that it would need to get a large following in order for it to have any value. This would involve large amounts of capital to fund marketing campaigns. While this is more of the customer’s problem, it is something to keep in mind when thinking about the viability and usefulness of what we build. If a working product is completed before the end of our senior year, the client might consider a closed test period with bucknell students.

Closing

This application could be absolutely revolutionary for the travel industry. It has become clear in recent years that there is a massive potential for any social application because it lets people integrate the platform into their lives, increasing its value to them. As such, the application has huge potential to gain a large following and user base, making it an extremely valuable idea.

Team Members

Eric Marshall

Cole Whitley

Stefano Cobelli

Andrew Capuano

Ternary Trip Sharing Pre-proposal

Trip Sharing Platform
Jingya Wu, Jordan Faith, Lucas Gregory, Sienna Mosher

Background

This project was raised initially to solve the problem of tracking national parks that the client has visited. Later on the client expended the problem to a trip sharing platform through which users can create, share, and complete lists of places to visit and is not limited to national parks any more. To be accessible this platform should be on the web and also mobily accessible. There have been many attempts at this type of software solution, but only marginal success stories. This leaves a market gap for us. The final deliverable should be a fully functional platform that can be used to log and share places as well as potentially creating lists of places for users to interact and compete with each other.

Executive Summary

To solve the problem identified above, we propose that the solution should at least be a mobile app, and ideally also a web application to complement the mobile version. The mobile app should include location service to enable users to check in at different places. The app also need to integrate Google Maps and utilizes its APIs to retrieve popular places. To be successful this needs to be a social travel network. This entails allowing users to login through their Facebook and/or Gmail accounts so that they can interact with their friends much easier, as well as allowing users to post to Facebook via the travel app. The mobile version is necessary because users need to check-in at places they visit, and we cannot expect them to bring a laptop wherever they go. The web application can complement the mobile app to provide a better exploring and viewing experience of trips and lists created by others. Every user will have a travel list comprised of their travel history, as well as the option to make lists for specific areas, wish lists, and more. Another great feature would be to have locals compile public lists of all the must-visit spots in the area. The basic structure of this application for both the mobile end and the web will include: a database for users’ account information, back-end algorithms to display the most relevant places/lists, as well as a clean and user-friendly front-end interface that can attract users as a new application.

Viability Analysis

The biggest challenge in this app is going to be organization. There are similar apps out there that attempt some of the proposed functionality, but the user interface is complicated, unorganized, and renders many features useless. Much of development will need to be spent finding the best organization to categorize locations, present the data, and lower overhead for users. Another issue is that this app needs users as much as the users need the app. If the locations are all created by users, the app starts with zero locations. It may be beneficial to internally create a base list of locations in order to overcome this challenge. In addition, this project will be built from scratch, meaning that as a team we need to decide on what languages and frameworks to use, and thus must keep in mind the current knowledge of all team members as well as the learning curve of learning new stuff. This is especially relevant to this project since we might need to develop on Android, iOS, and web, and this can be challenging.

Risks and Rewards

Currently there is no existing way to track and share places visited. This application can promote the traveling industry as traveling can become more rewarding for some people when they have a checklist to complete or when they are competing with someone else. This application, if in good use, can also give visitors to a local village good recommendations on where the good attractions and/or restaurants are for visiting. It can also empower locals to show the world the best things to do in their city. One issue that may arise is moderation. If we have a list representing a city that anyone of the city can add to, there may be some ill fitting locations added that are private residences, fake places, and/or places that seek to gain popularity through this app. Some moderations may be required, and this risk can be minimized by creating a rating system for locations lists and users who are publishing the lists, as well as by implementing an algorithm that recommends valuable and accountable lists to the users.

Closing

Overall, this is a fantastic idea and is reasonable to implement given the time and resources constraints. This application will be instrumental for travelers, who now have a place to log, share, and enthuse about their travel experiences. With the proposed features (places logging and sharing, list creating, etc) and external resources (Google Maps, Facebook, Google account) integrated, we can see a successful product that nothing else in the market has in common.

Ternary Antigua Pre-proposal

Interactive Digital Map
Jingya Wu, Jordan Faith, Lucas Gregory, Sienna Mosher

Background

Antigua has a rich history that goes largely unshared and unappreciated to the general public. Creating an accessible way for people around the country to learn more about Antigua’s history in an interactive, in depth, and exciting way would raise awareness about the history of Antigua, focusing on their historic sugar mills. A good start would be to create a digital map with plenty of interactivity and facts about the country. For these purposes you could use a modified google map, or a paper map representation, that then allows a user to click through each location and bring up a window displaying all relevant information. This map would act as the homepage and navigation bar of the website which would then branch off into the other pages which would be necessary to convey as much information as is required. There is a large amount of information that must be conveyed in a meaningful way, to this end the site has to be easily navigated and understood while still being interesting to the user.

Executive Summary

An interactive map would be a good plan to keep a user absorbed while still letting them achieve the goal of learning about Antigua. This solution would allow the user to navigate a detailed map, either decorative or realistic via google maps, that would let the user navigate to each point of interest and learn about its significance to the local area. These points could be marked via symbols or dots to represent what their significance is, then upon clicking on the marker the user would see a popup that displays minimal information with the option to go to a location specific page to read a more in depth summary. Such an implementation would allow the users to get drawn into exploring the map and make the act of learning an interesting experience. For easier navigation at a later date there could also be the option to lookup locations by name, or by using a list of all points organized by historical purpose. Curating an immersive historical journey through Antigua is the best way to get users familiar with its geography and history.

Viability Analysis

Through either satellite imagery or a decorative map, such as that employed in a related Mount Vernon interactive map, it would possible to easily navigate the site’s information. The basic information and the expanded pages could each be their own individual resources, meaning that an external database would not be necessary for initial implementation. As noted above each point of interest could trigger a popup window with the most basic information for that location. It could then allow the user to follow a hyperlink to another web page, either internal or external to the main site, where they could do more in depth research. Plugins such as GMaps or D3js allow for large amount of customization and include support for HTML overlays that would make user interaction a seamless process. Other tools, such as Kartograph, allow for large scale customization including custom maps, data points, click structures, animations, and more.
As for future maintenance, each point of interest could be edited on an as needed basis directly through the source code. If any edits are required, or a new point is added on the map, it would only need minor adjustments to go live on the existing structure. This alleviates the need for a robust backend and instead allows for full dedication to a purposeful front end to fully accomplish the goals of this project. This also decreases the upkeep load on the client and removes unnecessary costs for maintaining an extensive database linked to the website. With this model a database could be kept locally or online in the cloud, and data could be pulled whenever required for minor updates.

Risks and Rewards

This map would allow users to learn the history of Antigua through a fun and interactive medium, especially if we utilized tools for animations and real time inputs. There is some possibility of historical error about the area; however, this would be left to those maintaining and updating the website, not the initial developers. Impact from this service would be more niche than widespread, but would still provide useful tools to someone interested in learning about Antigua and the surrounding areas. Such a tool could also be extrapolated to surrounding areas and applied to more locations worldwide.

Closing

A project as important as preserving history needs to have careful attention paid to it. A solution such as the one listed above would allow for growth and iterations on the design, encouraging the continued expansion of facts and corrections of data as the need arises. The owner would be provided with a set of tools that would fully meet their needs and allow them to have full authority of how the history is represented in the most meaningful way possible via an administrative view of the map. This project would be an interesting challenge to build and make sure that the user’s interface and experience meet the highest expectations of the client.

TopDoc Pre-Proposal

Levi Adair

Dunni Adenuga

Brooke Bullek

Bobby Cao

Jason Corriveau

TopDoc

Background

Medical education involves repetition of concepts over years until it becomes second nature, just like a language. In medical school, doctors must memorize thousands of terms. These range from bones to arteries, and other systems in the body. Many times, medical students have to rely on using flash cards or other conventional methods of doing drills in order to memorize all of these new terms. However, all of these methods have their weaknesses. People can lose flashcards or write them incorrectly, they also can forget to study on their busy days. In order to have students and doctors in the field brush up on their medical knowledge or even learn new concepts, a mobile application could be used.Instead of books and tedious readings, an application can utilize puzzles, games, and quizzes to promote fun and interactive learning. Overall, a mobile app can significantly improve the convenience and effectiveness of medical education.

 

Executive Summary

A mobile application can be useful because many people have smart phones and use them frequently. If someone wants to learn,  they can open the application whenever they are free. Interactive games, puzzles and quizzes would be used as study tools. After the user takes the quiz, we can implement an algorithm based on their score to tell user they should learn more in a particular area. This application could also be tailored to specific fields; because of this a neurosurgeon would not have to waste time studying bones in the hand. Further, the application needs to be able to customize the learning for each individual; each doctor will need to review different subjects at varying amounts. In addition to the learning aspect of the application, we could also implement a search function. The search would be used for doctors to look up concepts that they need quick information on. Instead of having to look through Google search results or use a book, the terms could all be logged in the application. This application can be done in either Android via Android SDKs and the use of Java, IOS via IOS SDKs and Swift, or both.

 

Goals

  • Creation of games
  • Creation of puzzles
  • Creation of quizzes
  • Implement an algorithm to track user learning and show where they need improvement.
  • Have an intuitive and fun application

 

Viability Analysis

The most difficult part of developing this application is that we are not experts in the medical field. So we will need a database of medical concepts and facts. We will also need a third party to verify our information because there could be issues with incorrect or incomplete information. Another difficulty is  just how to apply medical concepts into a game and puzzle since that will require a lot of thinking and creativity. Lastly, we will have difficulties creating algorithms that decide what information people should study and the frequency they should study.

 

Risks and Rewards

A risk is that since this application is created by purely computer science students, we do not really know  how deep we want the users to know the concept. Further, our lack of medical knowledge will provide some challenge in identifying the most important topics for different doctors to review. Also, there is a risk for having incorrect information or having information misinterpreted and of course for a person practicing in the field this possibly can mean major harm to others. However, the reward is this can be a great application that millions of people in the medical field can utilize to learn or brush up in medical concepts during their free time and on the go. Of course this will mean better doctors, which can result in more lives being saved.

 

Closing

Learning medical concepts can be a chore, with a mobile application learn concepts can be intuitive and fun. Also interactive learning promotes deeper understanding of a concept as well. Millions of people in the medical field can use this and in turn become better in their field.

 

LifeAtHere PreProposal

Levi Adair

Dunni Adenuga

Brooke Bullek

Bobby Cao

Jason Corriveau

Life at Here

Background

Bucknell University is a 4-year college in the middle of nowhere. Many events, such as parties, games, dinners, talks, and concerts, are organized by different student organizations at different times and locations to maintain a healthy social scene. There are usually posters advertising some events and students usually have to take pictures or enter events into their Google Calendar in order to keep track (personal experience). It’s important to have a central location for all of these events. For events available to outsiders, more specific location information should be provided as well as useful information that can help them navigate the campus (e.g parking locations). Lastly, another difficulty that many Bucknell students face is keeping track of appointments and meetings with fellow students and Bucknell faculty. As such, it would be really useful to have an application that allows students to schedule and track meetings with others on campus.

Executive Summary

A good solution to this problem is a mobile phone application that contains regularly updated events on campus, along with event details such as time and location. Personal user accounts (or more favorably, integration with Bucknell students’ and faculty’s personal Google Calendar accounts) could offer the advantage of tracking personal appointments, an addition that would fit nicely with the theme of LifeAtHere and keeping campus commitments in one centralized location. This app can also be used to push urgent information to the student body. Events would be pushed to the app and students can select the events they’re interested in and would receive reminders about the events. For visitors, Google Maps can be integrated with the app to provide directions and help them navigate the campus. Visitors, instead of having access to Bucknell community’s personal appointments, would have ready access to the school directory.

 

Viability Analysis

It is possible to build this app, but it is important to determine the system by which the school events get added, the different level of access, etc. Another important decision would be to select a platform: Android/iOS. Further, this project would require close interaction with the CAP Center to learn about the ways events are organized and advertised. University-backed APIs (in addition to the CAP Center) could be used as resources to automatically provide the latest event details, rather than relying on a strictly student-run or crowdsourced method of adding new events (which hasn’t worked well with similar apps in the past). We would also have to work with Public Safety to learn about provisions created for visitors on campus. Additionally, to create appointments with other Bucknellians, the system would likely have to integrate with both the currently implemented “Room Request” on myBucknell and Google Calendar. Lastly, this app would probably require online access, so it’s important that the “bucknell_guests” WiFi access is always available and working effectively. To create this app, knowledge about mobile computing is necessary.

 

Risks and Rewards

If this is accepted and adopted by the campus community, this app would be a game changer in the way social life is organized on campus. As final year students, this is an opportunity to leave a legacy in a useful way. This project would not require too much financial commitment but would require time, especially when integrating already existing programs with our project. Also, the school may not be in support of some events posted on the app and/or students may be unwilling to post their events if the app is policed by the school. It’s important to find a compromise. Another issue that we will have to work around is that some app features, such as “appointment making” should only be available to members of Bucknell University and not visitors. Hence, we will have to request that users login to their Bucknell accounts, as they will otherwise not have access to specific features. Finally, one last risk associated with building this sort of app is that a similar app is already in existence. The “Bucknell” app, available on Android and iOS, is able to provide directions to visitors, along with a few features for currently enrolled students. Since this app already exists, the risk is that users may not want to download yet another “Bucknell” app onto their phone. Perhaps we can consider the solution of implementing and updating currently existing features in the “Bucknell” app.

 

Closing

The company should consider investing in this app because most of the tools required for building the app are open source. It’s also a fairly uncomplicated solution with a possible large impact. A centralized hub for viewing and scheduling upcoming campus events (and appointments) would fill a noticeable void in Bucknell’s otherwise technically savvy community. The pre-existing official Bucknell app leaves much to be desired as far as campus events and making appointments are concerned. LifeAtHere can be used by new and prospective students to learn about Bucknell’s social scene even before learning about the environment. If made into an app, LifeAtHere would be a viable means of keeping students in the loop and showing visitors/prospective students that Bucknell has an active and vibrant community.

LifeAtHere Preproposal

Background

Life at Bucknell’s campus is vibrant and full of opportunities for students to be active. Additionally, visitors to campus often need to know about parking and events that are happening. There is an obvious need for an all around campus assistant that visitors, students, and faculty can use to stay up to date with what is happening on campus.

Executive Summary

A tool like this could take the form of an app and a web page. Both would have the same functionality, and having both would allow for visitors to campus to find resources they need without having to find an app they might not know about. The app should be able to provide the user with relevant campus events, available parking for visitors and students, and help facilitate community involvement in events by advertising them.

Viability Analysis

A key piece of this project will be keeping the app up to date with relevant events. Ways to keep the app up to date would be to set up a script to scrape bucknell websites and automatically create new events based on what is posted on bucknell websites (like the main page, different athletic pages, weis center main page, etc). A different option would include creating a simple way to create a new event on the app and let, either through a whitelist or just by anybody, people post events. Other problems could be letting users use the app without service. Cell service at Bucknell and surrounding areas is not always the best, and this could prove problematic.

Risks and Rewards

The main risk in this app is that is doesn’t have much room to grow. A Bucknell campus assistant is an app that can only be used at Bucknell. On the other hand, the app could be developed in a way that leaves it more general. This could lead to a whole suite of apps that can become campus assistants for many schools. In addition, the app could clear up annual commotion that happens with annual events (like the high school swimming tournament that is hosted).

Closing

Bucknell is a campus that is always buzzing. Whether it is busy with an athletic event or the campus is hosting some national event, there is always something going on. Students and visitors alike are often interested in these events and other things that go on. At times the influxes of people can cause unexpected commotion on campus that leads to parking and other problems. An app that solves these issues would not only help Bucknell students, but could even lead to a whole new design for campus assistant apps.

Sienna Mosher Preproposal TopDoc

TopDoc

Background

Medical jargon and terminology is a vast and confusing language.  Currently the newest tool for learning these terms is digital flashcards.  However these aren’t fun or interactive and are not the best learning tool. Gamifying learning is the newest craze, with fast and lasting results.  What better way to assist those that aspire to keep your heart beating than by the best way to learn?  The task at hand is to make a gamified learning mobile app on medical terminology.

 

Executive Summary

There are three main aspects to this project:  Content, Games, and People.  For this app to be successful, the app must have a knowledge base of all the medical terminology.  Then we can figure out some game bases that have been proven successful in other languages, and implement them.  After a user takes a game, there will be a fun way to display feedback to the user.  To do this right, every user needs to have a profile that keeps track of what they know, and what they don’t know- This can be displayed as experience points, as well as an actual legible checklist of terminology.  This way the games can be customized to the user to help them learn what they don’t know, rather than what they do know.  The app could also have competitions and user versus user games as well for those who have a healthy competitive .  

 

Viability Analysis

The biggest difficulty in this project will be the content.  Either consultation of a knowledgeable medical professional, or a database of all the medical terminology and use cases will be crucial to complete this project. Another big step will be finding the best games to implement for the app.  This step might require a decent amount of research, and should be well thought out.  Once we find what works best, implementation should be relatively straightforward.  

 

Risks and Rewards

One risk would be the cost of developing on IOS.  The reward would be the first and best medical terminology gaming app on the market!  Not only will this impact current aspiring students, but could inspire a whole new wave of young health care physicians.  

 

Closing

This would be a helpful study tool for doctors-to-be, and a great way to get more people interested in the medical profession.  The major difficulty would be the content.  We would also design a stock of plug-and-play games to learn the terminology.  It is worth investing resources in this project  to better prepare new health care professionals , and to help them do the best job they can.  This application has huge potential to be very successful and leave a lasting impact.