Skip to content

Commit

Permalink
add surnames and required new sections
Browse files Browse the repository at this point in the history
  • Loading branch information
peterstadler committed Feb 7, 2025
1 parent de30069 commit b0a7229
Show file tree
Hide file tree
Showing 5 changed files with 49 additions and 15 deletions.
10 changes: 8 additions & 2 deletions _gsoc/edirom-3D-integration.md
Original file line number Diff line number Diff line change
@@ -1,9 +1,9 @@
---
title: Integration of 3D objects and 3D viewer in Edirom Online
mentors:
- name: Daniel
- name: Daniel Röwenstrunk
github: roewenstrunk
- name: Dennis
- name: Dennis Friedl
github: DennisFriedl
skills:
- Javascript
Expand Down Expand Up @@ -36,6 +36,12 @@ the front end. The integration is then essentially limited to the introduction
of a new object type. The other object types can serve as a template for all
tasks.

#### Goal

#### Impact

#### Warm-up Tasks

[Edirom-Online]: https://github.com/Edirom/Edirom-Online
[Kompakkt-StandaloneViewer]: https://github.com/Kompakkt/StandaloneViewer
[ExtJS]: https://www.sencha.com/products/extjs/
Expand Down
8 changes: 7 additions & 1 deletion _gsoc/edirom-frontend-testing.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
title: Front-end testing for Edirom-Online
mentors:
- name: Daniel
- name: Daniel Jettka
github: daniel-jettka
skills:
- Selenium
Expand All @@ -16,6 +16,12 @@ difficulty: medium

The front-end of the Edirom is written in JavaScript ([ExtJS]) and is currently modularized and modernized by developing and integrating custom web components. To ensure the quality, functionality, performance, and user-friendliness across different browsers we are seeking for support in implementing front-end testing with [Selenium]. The proposed project includes setting up and configuring a robust test automation framework using Selenium WebDriver for cross-browser testing and integrating it into the existing CI/CD pipelines. Compatibility with modern web browsers, including Chrome, Firefox, Safari, and Edge should be ensured, and reusable and maintainable test scripts to cover core user flows and features should be implemented. The testing framework will ensure that new code changes do not affect existing functionality. Defects will be clearly identified and meaningfully logged by the tests to allow for resolving the reported issues.

#### Goal

#### Impact

#### Warm-up Tasks

[Edirom-Online]: https://github.com/Edirom/Edirom-Online
[TEI]: https://tei-c.org/
[MEI]: https://music-encoding.org/
Expand Down
28 changes: 19 additions & 9 deletions _gsoc/edirom-ontology.md
Original file line number Diff line number Diff line change
@@ -1,30 +1,43 @@
---
title: Building Ontology for Edirom Data
title: Building a Knowledge graph for Edirom Data
mentors:
- name: Hizkiel Mitiku Alemayehu
- name: Salome Obert
github: obertsalome
- name: Tobias Bachmann
github: feuerbart
skills:
- SPARQL
- Linked Data
- Python
forum: https://chat.edirom.de/gsoc
est_project_length: 90 hours
difficulty: medium
keywords:
- Ontologies
- Linked Data
- SPARQL
- Open Source
- Knowledge graphs
---

[Edirom-Online](https://github.com/Edirom/Edirom-Online) is a software for presenting and analyzing critical musical editions in a digital format, particularly in **musicology** and **philology**. It supports various data formats commonly used in digital humanities, such as **TEI** (Text Encoding Initiative) for textual data and **MEI** (Music Encoding Initiative) for musical data, visualized with **Verovio**. This enables integration of different data formats, initially including texts, images, and music, and later expanding to audio and film within a single edition.

## Goal
The main goal of this project is to **build an ontology** for the data formats supported by Edirom-Online to improve **interoperability** and ensure **data consistency**. It will also serve as a foundation for **future linked data projects**. This can be achieved by:
#### Goal
The main goal of this project is to **build a knowledge graph** for the data
formats supported by Edirom-Online to improve **interoperability** and
ensure **data consistency**.
It will also serve as a foundation for **future linked data projects**.
This can be achieved by:

- Using **graph query technologies**.
- Constructing an **ontology** based on existing vocabularies, such as **Dublin Core** and **DICT**.
- Establishing a **structured and standardized ontology** to enhance **data consistency** across other projects using Edirom-Online.
- Supporting **internationalization** efforts of Edirom-Online.

## Impact
#### Impact
This project will be a **milestone** for Edirom-Online as it will introduce its first **consistent data structure** and **shareable resources**. Improving **interoperability** and **accessibility** will also contribute to the **internationalization** of the software.

## Warm-up Tasks
#### Warm-up Tasks
To get started with this project, complete the following tasks:

1. **Read the documentation** for Edirom-Online:
Expand All @@ -37,6 +50,3 @@ To get started with this project, complete the following tasks:
- [OWL (Web Ontology Language)](https://www.w3.org/OWL/)
- [Introduction to Linked Data](https://www.w3.org/wiki/LinkedData)
- [SPARQL 1.1 Query Language](https://www.w3.org/TR/sparql11-query/)

## Keywords
**Ontologies, Linked Data, SPARQL, Open Source**
8 changes: 7 additions & 1 deletion _gsoc/image_retrieval.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
title: Implement image retrieval algorithm for printed text and musical sheets
mentors:
- name: Dennis
- name: Dennis Friedl
github: DennisFriedl
skills:
- JavaScript
Expand All @@ -15,3 +15,9 @@ Scholarly music editions are increasingly being published in a hybrid format. Wh
To achieve this, a lightweight, resource-efficient image retrieval algorithm is required—ideally one that can run on a user’s mobile device (using web technologies) or on a remote server. The algorithm should be able to compare a captured image against a database of several thousand pages. While solutions for image retrieval via hashing/fingerprinting already exist, this task poses two primary challenges:
1. Pages containing text or musical notation often have very similar layouts and may differ only in a few measures or notes, making it easy for a typical low-resolution hashing procedure to miss these subtle distinctions.
2. Because users take photos under real-world conditions, the images are likely to be imperfect (e.g., poorly lit or misaligned) and may include more than just the page content.

#### Goal

#### Impact

#### Warm-up Tasks
10 changes: 8 additions & 2 deletions _gsoc/wega-oai.md
Original file line number Diff line number Diff line change
@@ -1,9 +1,9 @@
---
title: Develop an OAI-PMH API for the WeGA-WebApp
mentors:
- name: Peter
- name: Peter Stadler
github: peterstadler
- name: Dennis
- name: Dennis Ried
github: riedde
skills:
- XQuery
Expand Down Expand Up @@ -43,6 +43,12 @@ The task should also include testing the implementation for compliance with
the OAI-PMH standard and documenting the API endpoints, including their
functionality and expected parameters, for internal and external users.

#### Goal

#### Impact

#### Warm-up Tasks

[WeGA-WebApp]: https://github.com/Edirom/WeGA-WebApp
[OAI-PMH]: https://www.openarchives.org/pmh/
[Swagger OpenAPI]: https://www.weber-gesamtausgabe.de/api/v1/index.html

0 comments on commit b0a7229

Please sign in to comment.