Skip to content

Commit a3a311e

Browse files
Merge pull request #92 from oss-slu/portfolio-TPEN-Interfaces
created a portfolio page for TPEN Interfaces
2 parents e2c13d3 + 1460b57 commit a3a311e

File tree

4 files changed

+68
-0
lines changed

4 files changed

+68
-0
lines changed

docs/portfolio.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -52,6 +52,11 @@ We are especially interested in projects supporting researchers, focused on rese
5252
**[iSpraak](project_ispraak/about.md)** - This project is to automate speech evaluation of language learners and to provide them with instantaneous corrective feedback.
5353

5454

55+
## External Projects
56+
57+
**[TPEN Interfaces](project_tpeninterfaces/about.md)** - The TPEN Interfaces project provides a set of customizable web interfaces that leverage the TPEN Services API.
58+
59+
5560
## Other Projects
5661

5762
- ML Code Generator

docs/project_tpeninterfaces/about.md

Lines changed: 63 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,63 @@
1+
---
2+
title: TPEN Interfaces
3+
custom_edit_url: https://github.com/oss-slu/TPEN-interfaces
4+
---
5+
<!-- A header image is optional; if used should be no greater than 200x600 -->
6+
<!--![Header Alt Text](header.png) -->
7+
![TPEN logo](tpen_logo.png)
8+
9+
## Overview
10+
11+
These vanilla default and internally useful interfaces for the TPEN ecosystem that exemplify how you might build your own interfaces for specific projects. The directories each contain a named interface that serves as an example for how an external developer might use the TPEN Services API to implement a custom interface that leverages the TPEN platform. Interfaces are typically a web application, a simple HTML document, that utilizes Web Components that might be reused by others.
12+
13+
14+
### Information
15+
16+
- **Source Code:** [https://github.com/oss-slu/TPEN-interfaces](https://github.com/oss-slu/TPEN-interfaces) [<img src="/img/git-alt.svg" alt="git" width="25" height="25" />](https://github.com/oss-slu/dads)
17+
- **Client** Dr Artia Larson
18+
- **Current Tech Lead:** Sowmya Mutya [<img src="/img/github.svg" alt="github" width="25" height="25" />](https://github.com/MutyaSowmya123) [<img src="/img/linkedin.svg" alt="linkedin" width="25" height="25" />](https://www.linkedin.com/in/sowmya-mutya-7576211a0/)
19+
- **Developers:**
20+
- Patrick Cuba (SLU Research Computing Group) [<img src="/img/github.svg" alt="github" width="25" height="25" />](https://github.com/cubap)
21+
- Bryan Haberberger (SLU Research Computing Group) [<img src="/img/github.svg" alt="github" width="25" height="25" />](https://github.com/thehabes)
22+
- Victor Onoja (Web Developer) [<img src="/img/github.svg" alt="github" width="25" height="25" />](https://github.com/jsvoo)
23+
- **Start Date:** Jan, 2023
24+
- **Adoption Date:** Aug, 2024
25+
- **Technologies Used:**
26+
- Tech Stack- Web pages accessing TPEN API services
27+
- Key Languages- HTML, CSS, JavaScript
28+
29+
- **Type:** Web application
30+
- **License:** Primary Developers: Bryan Haberberger and Patrick Cuba © 2023 Research Computing Group at Saint Louis University
31+
32+
### User Guide
33+
34+
- **Public website** - Users can access the TPEN public website using the [link](https://t-pen.org/TPEN/). This version of TPEN (2.8) allows users to attach transcription data (either new or uploaded) to the actual lines of the original manuscript in a simple and flexible interface.
35+
- **TPEN3 Interfaces** -
36+
The directories here each contain an example of an interface that uses the TPEN authentication and interactions with the TPEN platform. For instance, the default location for transcription is TPEN Transcription Interface, which returns the file in /transcribe/index.html. If a project involves specialized transcription, such as music, the configuration can direct users to a custom location, like https://example.com/musicproject/interfaces/transcribe.html, with the project ID included in the query string. Examples of best practices include:
37+
38+
- `index.html`: The default interface to launch,
39+
- Supporting files: `*.js`, `*.css`, `*.html`, etc.,
40+
- Configuration files: `manifest.yml` or `manifest.json`
41+
42+
## Technical Information
43+
44+
### Technical Overview
45+
46+
The TPEN Interfaces project follows a layered architecture, consisting of front-end user interfaces built using HTML, CSS, and JavaScript that communicate with the TPEN Services API. This architecture allows developers to create custom interfaces by leveraging existing TPEN components and services. Below is a high-level overview of the architecture:
47+
48+
![Architecture](tpen_architechture.png)
49+
50+
### Development Priorities
51+
52+
- **Development priorities for TPEN interfaces:**
53+
- Developing interface examples for external developers to use as templates.
54+
- Customizable interfaces include:
55+
- Classroom group management
56+
- Musical transcription
57+
- Project toolsets
58+
- Alternative languages and alphabets
59+
- **Current Priority:** The Classroom Group Interface, which is a suite of interfaces for creating and managing TPEN groups. This interface focuses on setting permissions for roles. Permissions determine access to various resources and dictate what visualizations might be needed within the interface.
60+
61+
## Get Involved
62+
63+
If you would like to contribute to this project, please visit our [GitHub page](https://github.com/oss-slu/TPEN-interfaces) to create your own issues or pull requests.
30.9 KB
Loading
203 KB
Loading

0 commit comments

Comments
 (0)