DH2014Hackathon-Projects - Revision history

Felix Lange: /* Google Doc for the Extraction & Query Section */

2014-07-07T08:23:19Z

‎Google Doc for the Extraction & Query Section

James at 08:15, 7 July 2014

2014-07-07T08:15:28Z

Felix Lange: /* Suggested setup using Git */

2014-07-07T08:12:27Z

‎Suggested setup using Git

Raffaele.viglianti: /* Develop the MS description framework */

2014-07-07T07:33:51Z

‎Develop the MS description framework

Elli Bleeker: /* ODD visualizer */

2014-07-06T20:28:28Z

‎ODD visualizer

Rahtz: /* Develop the MS description framework */

2014-07-06T17:02:37Z

‎Develop the MS description framework

Rahtz: /* Basic framework for rendering a document and creating simple visualizations */

2014-07-06T16:56:06Z

‎Basic framework for rendering a document and creating simple visualizations

Rahtz: /* ODD visualizer */

2014-07-06T15:50:51Z

‎ODD visualizer

Rahtz: /* Suggested setup using Git */

2014-07-06T15:37:59Z

‎Suggested setup using Git

Rahtz: /* Let's Hack */

2014-07-06T15:23:55Z

‎Let's Hack

@@ Line 20: / Line 20: @@
 === Google Doc for the Extraction & Query Section ===
 https://docs.google.com/document/d/1W-f2jdQInxA3IKzSH_hn6sBD68lZcBTYZzWdBVjjSoo/edit?usp=sharing
 === ODD visualizer ===

← Older revision		Revision as of 08:15, 7 July 2014
Line 22:		Line 22:

	=== ODD visualizer ===		=== ODD visualizer ===
		+
		+	Some notes at: http://tinyurl.com/dh2014-TEIODD

	A group might try to put together a plan and start to code up an ODD visualizer. ODD is a literate programming language for XML schemas written by the TEI, and which is used to define the TEI schema. An ODD visualizer might be a component of an ODD customization tool such as the successor of Roma, and could provide information to a user about what modules they have included in their TEI schema, or what modification they have made.		A group might try to put together a plan and start to code up an ODD visualizer. ODD is a literate programming language for XML schemas written by the TEI, and which is used to define the TEI schema. An ODD visualizer might be a component of an ODD customization tool such as the successor of Roma, and could provide information to a user about what modules they have included in their TEI schema, or what modification they have made.

← Older revision		Revision as of 08:12, 7 July 2014
Line 17:		Line 17:

	Sebastian will be available during the Hackathon to wrangle the web server as needed.		Sebastian will be available during the Hackathon to wrangle the web server as needed.
		+
		+	=== Google Doc for the Extraction & Query Section ===
		+	https://docs.google.com/document/d/1W-f2jdQInxA3IKzSH_hn6sBD68lZcBTYZzWdBVjjSoo/edit?usp=sharing

	=== ODD visualizer ===		=== ODD visualizer ===

@@ Line 56: / Line 56: @@
 [[User:Alexander Czmiel|Alexander Czmiel]] 14:20, 4 July 2014 (CEST) Maybe I don't get it, but it seems to me this project has the same aims like "Basic framework for rendering a document". Anyway, rendering TEI documents is an imortant issue which has not been adressed enough in the past. Especially when looking on complex markup such as recommended by the Genetic Markup SIG.
-There are already a few approaches which try to do exactly the same, we want to do here: build a generic framework to publish TEI documents online. There is eLaborate (http://elaborate.huygens.knaw.nl/) from Den Haag, xMod (http://www.cch.kcl.ac.uk/xmod/) from London, DENQ from Rome, and SADE (best/current version on Github by vronk: https://github.com/vronk/SADE) which we try to build in Berlin/Göttingen/Wien. To a certain point OMEKA (http://www.omeka.net/) could be used as well, I think. There are many more, I don't know of. So please don't let us start from the scratch with a new project.
+There are already a few approaches which try to do exactly the same, we want to do here: build a generic framework to publish TEI documents online. There is eLaborate (http://elaborate.huygens.knaw.nl/) from Den Haag, xMod (http://www.cch.kcl.ac.uk/xmod/) from London (the latest installment of xmod is called "Kiln" and is more sophisticated and multiplatform: the code is here: (https://github.com/kcl-ddh/kiln)--[[User:Raffaele.viglianti|Raffaele.viglianti]] 09:33, 7 July 2014 (CEST)), DENQ from Rome, and SADE (best/current version on Github by vronk: https://github.com/vronk/SADE) which we try to build in Berlin/Göttingen/Wien. To a certain point OMEKA (http://www.omeka.net/) could be used as well, I think. There are many more, I don't know of. So please don't let us start from the scratch with a new project.
 --[[User:Elli Bleeker|Elli Bleeker]] 14:56, 4 July 2014 (CEST) I agree it would be pointless to start from scratch. But it might be worth considering to further develop one of the abovementioned approaches. I am not familiar with all of them, but most tend to fail once the textual genetics becomes more complex. The fact that many of the proposed projects in this Hackathon are aimed at the rendering of complex TEI mark up, suggests that this is one of the most important needs of textual scholars and that there is still no sufficient way to do so.

← Older revision		Revision as of 20:28, 6 July 2014
Line 34:		Line 34:

	--[[User:Rahtz\|Rahtz]] 17:50, 6 July 2014 (CEST) Elli - a modification is often simply specifying a subset of the TEI, ie removing elements you don't need. Visualizing just this relationship is itself quite useful; the proof of concept at http://tei.it.ox.ac.uk/Byzantium/ demonstrates a trivial example. In an ideal alternate work, the visualization would dynamic. Ie it would show a list of modules, and you could click on one to remove the elements in it, and that would trigger writing an ODD file.		--[[User:Rahtz\|Rahtz]] 17:50, 6 July 2014 (CEST) Elli - a modification is often simply specifying a subset of the TEI, ie removing elements you don't need. Visualizing just this relationship is itself quite useful; the proof of concept at http://tei.it.ox.ac.uk/Byzantium/ demonstrates a trivial example. In an ideal alternate work, the visualization would dynamic. Ie it would show a list of modules, and you could click on one to remove the elements in it, and that would trigger writing an ODD file.
		+
		+	--[[User:Elli Bleeker\|Elli Bleeker]] 22:28, 6 July 2014 (CEST) Thanks Sebastian for the clarification. I would like to join this group too.

	=== Basic framework for rendering a document and creating simple visualizations ===		=== Basic framework for rendering a document and creating simple visualizations ===

← Older revision		Revision as of 17:02, 6 July 2014
Line 72:		Line 72:

	[[User:Patrik Granholm\|Patrik Granholm]] 08:55, 6 July 2014 (CEST) I have a few preliminary MS descriptions from our cataloguing project, and quite a large collection of MS descriptions from other projects which we could work with.		[[User:Patrik Granholm\|Patrik Granholm]] 08:55, 6 July 2014 (CEST) I have a few preliminary MS descriptions from our cataloguing project, and quite a large collection of MS descriptions from other projects which we could work with.
		+
		+	--[[User:Rahtz\|Rahtz]] 19:02, 6 July 2014 (CEST) I agree that starting a new framework isn't a good idea, but I do think there is a future in taking just the components of the transcription module and doing rendering of those. Its a horribly open-ended exercise, though.

	=== Discussing, working out and documenting best practices for an authoring workflow ===		=== Discussing, working out and documenting best practices for an authoring workflow ===

@@ Line 45: / Line 45: @@
 --[[User:Elli Mylonas|Elli Mylonas]] 11:27, 4 July 2014 (CEST) Frederike has a good comment - are there suggestions? Google Maps is one idea. Leaflet, and D3 (more complex) are others. Thoughts?
---[[User:Rahtz|Rahtz]] 17:02, 6 July 2014 (CEST) I would suggest we limit ourselves for this project to Leaflet (mapping) and D3 (graphs) with its companion C3. Both have loads of examples and addons. Leaflet rather than Google Maps because it doesn't need API keys etc, and can use other tiles easily. The key thing here is to proof of concept - get a visualization up and running quickly, then tweak it. If its successful, recoding it later in another library is not so hard. Note, however, that we come up against cross-site scripting which we read JSON in an HTML file. See Setup section above.
+--[[User:Rahtz|Rahtz]] 17:02, 6 July 2014 (CEST) I would suggest we limit ourselves for this project to Leaflet (mapping) and D3 (graphs) with its companion C3. Both have loads of examples and addons. Leaflet rather than Google Maps because it doesn't need API keys etc, and can use other tiles easily. The key thing here is to proof of concept - get a visualization up and running quickly, then tweak it. If its successful, recoding it later in another library is not so hard. Note, however, that we come up against cross-site scripting when we read JSON in an HTML file. See Setup section above.
 === Develop the MS description framework ===

← Older revision		Revision as of 15:50, 6 July 2014
Line 32:		Line 32:

	[[User:Raffaele.viglianti\|Raffaele.viglianti]] 13:40, 6 July 2014 (CEST) I'd happily work on this		[[User:Raffaele.viglianti\|Raffaele.viglianti]] 13:40, 6 July 2014 (CEST) I'd happily work on this
		+
		+	--[[User:Rahtz\|Rahtz]] 17:50, 6 July 2014 (CEST) Elli - a modification is often simply specifying a subset of the TEI, ie removing elements you don't need. Visualizing just this relationship is itself quite useful; the proof of concept at http://tei.it.ox.ac.uk/Byzantium/ demonstrates a trivial example. In an ideal alternate work, the visualization would dynamic. Ie it would show a list of modules, and you could click on one to remove the elements in it, and that would trigger writing an ODD file.

	=== Basic framework for rendering a document and creating simple visualizations ===		=== Basic framework for rendering a document and creating simple visualizations ===

@@ Line 7: / Line 7: @@
 === Suggested setup  using Git ===
-There is a Git repository at https://github.com/TEIC/Hackathon which can be used for any group during the Hackathon. Sebastian Rahtz can add people to the TEI group on request so that they have write access. This repository is synchronized with a web server at http://tei.it.ox.ac.uk/Hackathon/ every minute. This web server has a  CORS setup, which should allow cross-site scripting to work for any
+There is a Git repository at https://github.com/TEIC/Hackathon which can be used for any group during the Hackathon. Sebastian Rahtz can add people to the TEI group on request so that they have write access. You can use any Git client, obviously. If you don't have a client setup
 group working with JSON or other Ajax technique.

← Older revision		Revision as of 15:23, 6 July 2014
Line 4:		Line 4:

	A suggestion for how to proceed based on the range of proposals and the range of participants. The group is likely to be able to sustain 2 or at most 3 projects in the time frame allotted. Some suggestions; please modify, develop or otherwise shape to your liking!		A suggestion for how to proceed based on the range of proposals and the range of participants. The group is likely to be able to sustain 2 or at most 3 projects in the time frame allotted. Some suggestions; please modify, develop or otherwise shape to your liking!
		+
		+	=== Suggested setup using Git ===
		+
		+	There is a Git repository at https://github.com/TEIC/Hackathon which can be used for any group during the Hackathon. Sebastian Rahtz can add people to the TEI group on request so that they have write access. This repository is synchronized with a web server at http://tei.it.ox.ac.uk/Hackathon/ every minute. This web server has a CORS setup, which should allow cross-site scripting to work for any
		+	group working with JSON or other Ajax technique.
		+
		+	To test this, clone the Git repository on your local laptop and open the file map/maptest.html in your browser. It should read JSON data from
		+	http://tei.it.ox.ac.uk/Hackathon/map/objects.json and display it on a map. If you add more JSON data files to the repository, and push them up to Github, they should appear on the web server quite quickly; similarly this can be used to "publish" HTML.
		+
		+	Sebastian will be available during the Hackathon to wrangle the web server as needed.

	=== ODD visualizer ===		=== ODD visualizer ===