2022-23:fall
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| 2022-23:fall [2022/07/20 16:40] – aan | 2022-23:fall [2022/07/22 15:49] (current) – aan | ||
|---|---|---|---|
| Line 2: | Line 2: | ||
| ====== Proposed Projects For Fall 2022 ====== | ====== Proposed Projects For Fall 2022 ====== | ||
| - | Below is a list of 4080/ | + | Below is a list of 4080/ |
| + | |||
| + | ====== Automation of Copyright Takedowns ====== | ||
| + | **Course:** EECS4070/ | ||
| + | |||
| + | **Supervisor: | ||
| + | |||
| + | **Contact: | ||
| + | |||
| + | COVID has accelerated the trend for delivering university courses online. This has been a boon to providing accessible learning modes to students. | ||
| + | |||
| + | A copyright takedown process (e.g. DMCA) is in place on these commercial sites but it is cumbersome to use. The objective of this project is to semi-automate the take-down process in one of two ways: | ||
| + | |||
| + | 1. Allow a copyright holder to identify a category of course material (e.g. a course name and number) a priori and engage a scheduled process which regularly scans a commercial site (e.g. Course Hero) and automatically submits takedowns on behalf of the copyright holder | ||
| + | |||
| + | 2. Submit reports to the copyright holder when an identified category of course material is found on a commercial site (e.g. Course Hero) and asks the copyright holder whether a takedown request should be made on the holder' | ||
| + | |||
| + | **Required skills:** General programming skills | ||
| + | |||
| + | **Recommended skills:** Experience in Python (and perhaps Beautiful Soup) and/or Java and/or equivalent | ||
| + | |||
| + | ====== Visualization of Course Maps at YorkU ====== | ||
| + | |||
| + | **Course:** EECS4070/ | ||
| + | |||
| + | **Supervisor: | ||
| + | |||
| + | **Contact: | ||
| + | |||
| + | Students at York have long been missing the ability to visualize the connections between courses when planning or reviewing their progress through their program. | ||
| + | |||
| + | This is a continuation of an existing open-source project written in Python. | ||
| + | |||
| + | 1. A visualization can be produced and displayed on the web | ||
| + | |||
| + | 2. Corrections to the existing data set (the University' | ||
| + | |||
| + | Students involved in the project will be required to maintain public-facing documentation. The result of this project will remain open source for further development by students, staff and faculty. | ||
| + | |||
| + | **Required skills:** General programming skills | ||
| + | |||
| + | **Recommended skills:** Experience in Python (and perhaps Beautiful Soup) and web-centric tools | ||
| + | |||
| + | ====== Privacy assessment of online services and platforms ====== | ||
| + | |||
| + | **Course:** EECS4480/ | ||
| + | |||
| + | **Supervisor: | ||
| + | |||
| + | **Contact: | ||
| + | For any question email: yansh@yorku.ca | ||
| + | |||
| + | This project involves performing privacy assessment of online services and platforms. The student will help design usable-privacy tools that analyze information handling practices of online services. | ||
| + | |||
| + | For prior project, see work https:// | ||
| + | |||
| + | **Required skills:** Ability to work indepently. Experience in full-stack development and using Jupyter and R notebooks for data analysis. | ||
| + | |||
| + | **Recommended skills:** Experience with Machine Learning, Natural Language Processing techniques, HCI design. Interest in usable privacy, critical analysis of privacy policies and privacy related regulation. | ||
| /** | /** | ||
| Line 41: | Line 100: | ||
| **/ | **/ | ||
| - | Back to [[https:// | + | Back to [[: |
2022-23/fall.1658335208.txt.gz · Last modified: by aan
