Skip to content

Commit e7a540e

Browse files
committed
Categorize ideas as per page difficulty levels
1 parent e2049a7 commit e7a540e

File tree

4 files changed

+11
-11
lines changed

4 files changed

+11
-11
lines changed

content/internships/project-ideas-collection/catalog-expansion/contents.lr

+3-3
Original file line numberDiff line numberDiff line change
@@ -10,11 +10,11 @@ The [CC Catalog](https://github.com/creativecommons/cccatalog) gets a huge amoun
1010
expected_outcome:
1111
We would like to have a number of completed, well-tested Provider API Scripts written by the end of this internship, and they should be deployed in production. Deployment in production implies we’d also have Apache Airflow DAGs (Directed Acyclic Graphs) that run the Provider API Scripts on an appropriate schedule.
1212
---
13-
internship_tasks:
13+
internship_tasks:
1414
The intern should write more Provider API Scripts, taking priorities from the backlog linked above. Such a script must pull image information from a public API provided by the provider, and pass it along to a function that will validate the information, format it as necessary, and write it to disk. This validation/storage function is already written, so the intern needs only to write a script that knows how to get the relevant data from the public API of the provider. For examples of what we are expecting from a Provider API Script, see `wikimedia_commons.py` and `flickr.py `in [the repository](https://github.com/creativecommons/cccatalog/tree/master/src/cc_catalog_airflow/dags/provider_api_scripts), as well as their accompanying tests.
1515
---
1616
application_tips:
17-
Knowledge or experience with pulling real data from public APIs in JSON format would be helpful. It would also help if the intern is familiar with Python.
17+
Knowledge or experience with pulling real data from public APIs in JSON format would be helpful. It would also help if the intern is familiar with Python.
1818
---
1919
resources:
2020
* [CC Catalog code](https://github.com/creativecommons/cccatalog)
@@ -25,4 +25,4 @@ skills_recommended: Python, JSON, Apache Airflow (optional)
2525
---
2626
mentors: Brent Moran, Kriti Godey
2727
---
28-
difficulty: Low
28+
difficulty: Easy

content/internships/project-ideas-collection/linked-commons/contents.lr

+2-2
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ expected_outcome:
1414
* We may also add live updating to the data that backs the visualization.
1515
* If these features are completed ahead of schedule, the intern may suggest further features to add to the visualization.
1616
---
17-
internship_tasks:
17+
internship_tasks:
1818
The intern should implement the first feature above, and if there’s time, implement the second. It may be useful for the intern to assist with setting up live-updating of the data backing the visualization.
1919
---
2020
application_tips:
@@ -31,4 +31,4 @@ skills_recommended: JavaScript, Graph Theory
3131
---
3232
mentors: Brent Moran, María Belén Guaranda Cabezas
3333
---
34-
difficulty: Low
34+
difficulty: Easy

content/internships/project-ideas-collection/metrics-dashboard/contents.lr

+3-3
Original file line numberDiff line numberDiff line change
@@ -9,15 +9,15 @@ problem:
99

1010
While we do keep track of certain user actions in our database, and are able to glean other insights with the use of Google Analytics, we do not have a single dashboard to see relevant information.
1111

12-
This is a problem for two reasons:
12+
This is a problem for two reasons:
1313
* We have a lack of comprehensive understanding of user behavior, as we have to look in multiple places and pull disparate information to paint a picture of overall user behavior.
1414
* Our catalog partners have no way to understand what impact their presence in CC Search is having in terms of discoverability and increased exposure to their collections.
1515
* In turn we are unable to tell a story about that impact to potential, future partners.
1616
---
1717
expected_outcome:
1818
We’d like the outcome to be an analytics interface, of some kind, where all of these metrics are pulled together into one place. The interface should be both aesthetically pleasing and clear to understand, allowing those accessing it to get the pertinent information they need, whether it is by day, week, month, collection, or any other logical grouping.
1919
---
20-
internship_tasks:
20+
internship_tasks:
2121
* Understand the required data to be displayed as defined by CC HQ
2222
* Research analytics dashboards to provide recommendations on additional data that is valuable
2323
* Document a cohesive plan for structuring an analytics database storing all pertinent data
@@ -39,4 +39,4 @@ skills_recommended: CSS, design, HTML, Python, PostgreSQL
3939
---
4040
mentors: Alden Page, Anna Tumadóttir
4141
---
42-
difficulty: High
42+
difficulty: Hard

content/internships/project-ideas-collection/web-monetization/contents.lr

+3-3
Original file line numberDiff line numberDiff line change
@@ -12,8 +12,8 @@ CC is a non-profit supported by donations from foundations, corporations, and in
1212
expected_outcome:
1313
We’d like the outcome of this internship to be a deliverable, in written form, detailing in-depth research regarding the current state of web monetization technology, with recommendations for options for CC. We expect this deliverable to take the form of a CC-licensed research paper, based on which we expect the intern to also write a blog article.
1414
---
15-
internship_tasks:
16-
The intern will be expected to create their own detailed work plan, containing activities including but not limited to:
15+
internship_tasks:
16+
The intern will be expected to create their own detailed work plan, containing activities including but not limited to:
1717
* preliminary research
1818
* user interviews
1919
* preparation of an outline
@@ -36,4 +36,4 @@ skills_recommended: Research, Writing. In so far as the work is technical, it is
3636
---
3737
mentors: Anna Tumadóttir, Sarah Pearson
3838
---
39-
difficulty: Low
39+
difficulty: Easy

0 commit comments

Comments
 (0)