---
tags: projects
---

# MINERVA #

_by Tom Brughmans_

| Key | Value |
| --- |:---:|
| name | nameson, name |
| email | [e-mail] |
| university | someuni |

---

Proposal: Sprint
* Clear specifications
* Break down you data to smallest possible units
* Clear description of
* Webpage with these features

__Upgrade Current Database Solution__
* NEED to HAVE
* New implementation

__Develop New Graph-based Database__
* NICE to HAVE

these to are dependent

We need to break down and prioritize your job(s) to
Week 32
* specifications
1. Break down you data: what is the smallest unit(-s) for distances and points, e.g., geom distance between two places, potsherd
2. Relationship to Pleiades
3. Relationship to extracted data
* usecase-s
1. What will your RAs be doing in the fall
2. What will end-users be doing
* Prioritization: need-to-haves and nice-to-haves
* Outcome and ultimate goal
1. Are we solving multiple small tasks (easier upload, graph database for spatial analytics...)
2. OR one generic solution
3. Final Website, how does it work, what does it looks like

---

## Project Developers

## Project Description
manual process of publishing archeological findings on geolocation projection:
- roman road (hand drawn from published maps)
- vector area field (proprietary QGIS code)
- projection file
- shape file
- section file (edits)
- identify and link geo codes to Pleiades urls (references to archeologic sources)
- download data (single files) from QGIS (propreitary, but transpilable w/ OS software)
- manually filling out forms on itiner-e.org (private)
- related visualizations can be updated (http requests + map overlays)

### Part 1, Data Extraction
Uploading individual roman roads is labor intensive. Automation of process?
Roads are uploaded in sections, each with possibly independent url, sources, and data.
- pleiades urls link between sets (manual)
- 2D normalized entries

### Part 2, Database
**DATABASE** (from September 2021-early 2022):
* online database that allow for data entries online
* 5 people
* front-end, visible
* entities with attributes
* search
- travelling salesman?
- routing for modes of travel (friction of lanscape, road conditions)
- point to point > which sections, stops

### Part 3, Modeling
what is the normalized anchor for db entries?
- geolocation?
- map projection location?
- Pleiades urls?
- road section edit?

### web design (long term)
map with filter/overlay bars on the sides (better version of orbis.stanford.edu)
must be future stable.

___

## OLD DESC
I would like to talk about the following things:
- How to budget activities
- How to pay CHC
- Database
- Data analysis scripts
- Explorable explanations
- Agent-based and other simulation modelling, and HPC if necessary

[Ulterior Goal of Project](https://orbis.stanford.edu/)

## Databases January 2021 ##

**ANALYSIS**: four database for analysis (two relational, two linked open data)
- [Priority 2021] link-able on (data extraction & analysis), **Peter Bjerregaard** (Data Extraction) [SECONDARY]
--> Peter
- data analysis, _UCloud_ (statistical modeling, EDA for time series)

**DATABASE** (from September 2021-early 2022): [PRIMARY PRIORITY]
Linked open data, turn internal database into front end (), back-end

https://pleiades.stoa.org/ transformed to a road database (currently a place database), canonical uri for each entry, users with read, and editors, allow for data dumps.

Have data set that can be queried and downloaded

**ABM (2023)**
Driven by CS postdocs, math, (__HPC engineering__ from )

**Dissemination (2023)**

https://explorabl.es/

Data analysis scripts/notebooks.
Draw on linked open data from two sources:

Samian:
https://www1.rgzm.de/samian/home/frames.htm

CEIPAC:
https://romanopendata.eu/sparql/epnet.html

Both should be linked based on place names: they use the same placename URI’s from the Pleiades gazetteer:
https://pleiades.stoa.org

These two databases should be linked to two other offline relational databases, which use the same gazetteer.

ceramics (2021) --> road (2022) --> ABM (2023) --> (outreach & dissemination)

> software engineering
>

## Data Assessment ##
| Source | risk | Storage | Comment|
| --- |:---:|---|---|
|||| |

## Data Identification ##
| Item | Answers |
| --- | --- |
| Description | |
| Collection | |
| Volume | |
| Formats | |
| Software | |

### Data Management Comments ###

## MISC
- how to export data from QGIS https://gis.stackexchange.com/questions/135801/exporting-attribute-table-to-excel-from-qgis