-
Notifications
You must be signed in to change notification settings - Fork 0
/
methods.html
126 lines (108 loc) · 10.7 KB
/
methods.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
<!DOCTYPE html>
<html>
<head>
<!-- Global site tag (gtag.js) - Google Analytics -->
<script async src="https://www.googletagmanager.com/gtag/js?id=UA-166319682-1"></script>
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('js', new Date());
gtag('config', 'UA-166319682-1');
</script>
<!-- tab -->
<title>
Methods | Heritage Reconstructed
</title>
<link rel="stylesheet" type= "text/css" href="stylesheet.css">
<script async defer src="https://buttons.github.io/buttons.js"></script>
</head>
<body onload="myFunction()" style="margin:0;">
<div id="loader"></div>
<div style="display:none;" id="myDiv" class="animate-bottom">
<!-- website title -->
<header>
<h1 style="text-align: center; font-family: 'Gill Sans', 'Gill Sans MT', Calibri, 'Trebuchet MS', sans-serif; color: #336699; font-weight: normal; text-transform: uppercase;">Heritage Reconstructed</h1>
<h2 style="margin-top: 5px; font-style: italic;">Virtualizations of Archaeological Sites in Peril</h2>
</header>
<!-- menu -->
<nav>
<a href="index">Home</a>
<a class="active" href="methods">Methods</a>
<a href="mission">Mission</a>
<a href="team">Team</a>
<a href="resources">Resources</a>
<a href="https://hreconstructed.omeka.net/exhibits">Database</a>
</nav>
<!-- body text -->
<section>
<articlemain>
<h3>Our Data</h3>
<p>Virtual Reality (VR) methods have been used for almost three decades in the field of cultural heritage, specifically, for the reconstruction, visualization, and interpretation of archaeological sites. The Virtual Reconstruction database is organized following two selection criteria: first, we focus on archaeological sites that, unlike natural sites, require human intervention and creation, and may include cultural artifacts, architecture, art, religious buildings and objects. Second, we focus on archaeological sites in peril due to poaching, armed conflict, terrorism, war, and environmental damages such as natural disasters and pollution.</p>
<p>We selected the VRs following a snowball technique. First, we explored the <a href="https://whc.unesco.org/en/danger/" target="_blank">UNESCO World Heritage in Danger</a> list. The list includes 53 sites in danger and includes cultural (archaeological) sites and natural sites. We focused solely on the archaeological sites. We searched for any VRs accessible online, country by country, using different keywords as the search parameters. The UNESCO list allowed us to find some start-ups, artists, and scholars that are also working on virtual reconstructions of archaeological sites in peril and have created VRs on the topic.</p>
<p>Having completed the search following UNESCO's list, we identified three patterns: one, there are not many VRs for the sites that UNESCO considers in peril. Second, the VRs available are of archaeological sites from countries that come from the same geographical region and, mostly are in peril or were destroyed by war and terrorist groups (e.g., Iraq, Libya, Syria, and Afghanistan). Third, the VRs available are available for countries and archaeological sites that are very well known (e.g. Italy and Greece).</p>
<br/>
<h3>Website and Database Creation</h3>
<p>When thinking about how we would display our data, the main focus was on the database. We decided to use Omeka, which "provides open-source web publishing platforms for sharing digital collections and creating media-rich online exhibits" (<a href="https://omeka.org/" target="_blank">Omeka.org</a>). Omeka is used by thousands of institutions and organizations across the US and all over the globe. The Berlin theme is a simple layout that is one of two that are preloaded and makes the content easily accessible. The database focuses on the use of items which are then described by using the <a href="https://omeka.org/classic/docs/Content/Working_with_Dublin_Core/" target="_blank">Dublin Core Metadata Initiative</a>. Omeka.net has a Trial plan that allows the use of one site with 500MB of storage space that we believe to be sufficient space for the start of our database. Although we are working with images and videos of digital reconstructions, in addition to digital reconstruction themselves, we have been able to showcase all these different types of formats.</p>
<p>Despite Omeka's "Simple Pages", which allows for the creation of static pages within the Omeka website, the feature did not allow for much freedom in terms of web design or embedding. This is what led us to creating static pages using HTML/CSS and hosting the pages for free on <a href="https://pages.github.com/" target="_blank">GitHub Pages</a>. This allowed us to have an area that we can remain engaged with our community (with the embedded Twitter feed on the side), as well as having an area separate from the database to explain our project.</p>
<br/>
<h3>Mapping the Database</h3>
<p>In addition to our database, we created a map in Tableau to represent the sites we have included in our Omeka database. Tableau Software is a data visualization software company specializing in graphs and charts. However, another important aspect of Tableau is their mapping feature, which helps to inform with the use of tooltips. The tooltips for our sites include country, name of site and URL. To navigate to a specific item in our database from within the embedded map below, simply click the desired point of interest. Also, the map can be visited <a href="https://public.tableau.com/views/HeritageReconstructed/Map?:display_count=y&publish=yes&:origin=viz_share_link" target="_blank">here</a>.</p>
<div class='tableauPlaceholder' id='viz1588695378278' style='position: relative'><noscript><a href='#'><img alt=' ' src='https://public.tableau.com/static/images/He/HeritageReconstructed/Map/1_rss.png' style='border: none' /></a></noscript><object class='tableauViz' style='display:none;'><param name='host_url' value='https%3A%2F%2Fpublic.tableau.com%2F' /> <param name='embed_code_version' value='3' /> <param name='site_root' value='' /><param name='name' value='HeritageReconstructed/Map' /><param name='tabs' value='no' /><param name='toolbar' value='yes' /><param name='static_image' value='https://public.tableau.com/static/images/He/HeritageReconstructed/Map/1.png' /> <param name='animate_transition' value='yes' /><param name='display_static_image' value='yes' /><param name='display_spinner' value='yes' /><param name='display_overlay' value='yes' /><param name='display_count' value='yes' /></object></div> <script type='text/javascript'> var divElement = document.getElementById('viz1588695378278'); var vizElement = divElement.getElementsByTagName('object')[0]; if ( divElement.offsetWidth > 800 ) { vizElement.style.width='800px';vizElement.style.height='827px';} else if ( divElement.offsetWidth > 500 ) { vizElement.style.width='800px';vizElement.style.height='827px';} else { vizElement.style.width='100%';vizElement.style.height='927px';} var scriptElement = document.createElement('script'); scriptElement.src = 'https://public.tableau.com/javascripts/api/viz_v1.js'; vizElement.parentNode.insertBefore(scriptElement, vizElement); </script>
</articlemain>
<articleside>
<a class="twitter-timeline" data-tweet-limit="4" data-width="270" data-chrome="noscrollbar" data-theme="light" href="https://twitter.com/HReconstructed?ref_src=twsrc%5Etfw">
</a>
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8">
</script>
</articleside>
</section>
<!-- footer code by webdevtrick ( https://webdevtrick.com ) -->
<footer class="footer-distributed">
<div class="footer-left">
<h3>Heritage Reconstructed</h3>
<p class="footer-links">
<p class="footer-links">
<a href="index">Home</a>
<a> | </a>
<a href="methods">Methods</a>
<a> | </a>
<a href="mission">Mission</a>
<a> | </a>
<a href="team">Team</a>
<a> | </a>
<a href="resources">Resources</a>
<a> | </a>
<a href="https://hreconstructed.omeka.net/exhibits">Database</a>
</p>
<p class="footer-company-name">Heritage Reconstructed 2020</p>
</div>
<div class="footer-center">
<p style="font-size: 18px; font-weight: bold;">Contact Us:</p>
<pre></pre>
<p><a style="text-decoration:none; color:white;" href="mailto:heritagereconstructed@gmail.com"><u>heritagereconstructed@gmail.com</u></a></p>
<pre></pre>
<p><a style="text-decoration: none; color: white;" href="https://gccuny.az1.qualtrics.com/jfe/form/SV_38EwF4J2delXR4x" target="_blank"><u>Subscribe to our mailing list</u></a></p>
<pre></pre>
</div>
<div class="footer-right">
<p style="font-size: 18px; font-weight: bold; color: white;">Follow Us:</p>
<div class="footer-icons">
<a href="https://twitter.com/hreconstructed?ref_src=twsrc%5Etfw" class="twitter-follow-button" data-show-count="false">Follow @hreconstructed</a><script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
<!-- Place this tag where you want the button to render. -->
<a class="github-button" aria-label="Follow @hreconstructed on GitHub" href="https://github.com/hreconstructed">Follow @hreconstructed</a>
</div>
</div>
</footer>
</div>
<script>
var myVar;
function myFunction() {
myVar = setTimeout(showPage, 500);
}
function showPage() {
document.getElementById("loader").style.display = "none";
document.getElementById("myDiv").style.display = "block";
}
</script>
</body>
</html>