<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=windows-1251"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Okay, I've sorted more of the data fields (this might not come up
right, I hope it does), comments welcome!<br>
<br>
I am sure I am missing some useful bits (it's also very simplified -
apart from the admin side, at the start this might be all the tables -
so it's not going to be fully normalised, have no related "games" or
"theory" links, and it is probably going to be a MySQL thing, thus the
choice of data types is pretty limited - although I'll probably make
some varchar rather then text later).<br>
<br>
<table border="1">
<caption> Resource Data Table
</caption><tbody>
<tr>
<th> Field Name </th>
<th> Data Type </th>
<th> Data Size </th>
<th> Description
</th>
</tr>
<tr valign="top">
<th> key
</th>
<td> +VE INT </td>
<td> 128bit (Maximum size)
</td>
<td> This identifies the entry. A int is used to speed up lookups
and so forth, and is never ever shown to anyone, even admins. Game
names change, and so do URL identifiers (if the need arises), so this
is the one bastion of "neverchanging" which links all the names and
URL's to it (as well as all other reference tables!)
</td>
</tr>
<tr valign="top">
<th> title
</th>
<td> TEXT </td>
<td> 0
</td>
<td> Title of the resource
</td>
</tr>
<tr valign="top">
<th> local_title
</th>
<td> TEXT </td>
<td> 0
</td>
<td> If set, this will contain the English translated/localised
title. NB: Multilingual will need to be sorted eventually!
</td>
</tr>
<tr valign="top">
<th> author
</th>
<td> TEXT </td>
<td> 0
</td>
<td> Maybe VARCHAR? or allow an ID link? (can be multiple
authors!) In any case, the person, group of people or organisation who
authored the resource
</td>
</tr>
<tr valign="top">
<th> date
</th>
<td> DATETIME </td>
<td> 0
</td>
<td> Standard date field. Allow full input (down to the
millisecond) or just a "day" or "month" or "year"
</td>
</tr>
<tr valign="top">
<th> url
</th>
<td> TEXT </td>
<td> 0
</td>
<td> URL to the resource, if on the web.
</td>
</tr>
<tr valign="top">
<th> page_count
</th>
<td> SMALLINT </td>
<td> 0
</td>
<td> Positive integer - number of pages in the article.
</td>
</tr>
<tr valign="top">
<th> isbn
</th>
<td> VARCHAR </td>
<td> 13
</td>
<td> International Standard Book Number (13 digits long)
</td>
</tr>
<tr valign="top">
<th> issn
</th>
<td> VARCHAR </td>
<td> 8
</td>
<td> International Standard Serial Number
</td>
</tr>
<tr valign="top">
<th> publication_info
</th>
<td> TEXT </td>
<td> 0
</td>
<td> Publication information. Might be the publisher, where it
was published, who by
</td>
</tr>
<tr valign="top">
<th> abstract
</th>
<td> TEXT </td>
<td> 0
</td>
<td> Fair use abstract from the paper
</td>
</tr>
<tr valign="top">
<th> description
</th>
<td> TEXT </td>
<td> 0
</td>
<td> Description of the paper, if any more is necessary over the
abstract.
</td>
</tr>
<tr valign="top">
<th> editors_notes
</th>
<td> TEXT </td>
<td> 0
</td>
<td> Editors notes for the entry - hidden from the public
</td>
</tr>
<tr valign="top">
<th> keywords
</th>
<td> TEXT </td>
<td> 0
</td>
<td> Keywords for the resource, like tags (so could be a phrase)
to aid searching for things outside of categorisation, probably
separated by commas or something similar.
</td>
</tr>
<tr valign="top">
<th> NAMEOFFIELD
</th>
<td> DATATYPE </td>
<td> 0
</td>
<td> DESCRIPTION
</td>
</tr>
</tbody>
</table>
<p><br>
</p>
<table border="1">
<caption> Resource Type Category Relational Table
</caption><tbody>
<tr>
<th> Field Name </th>
<th> Data Type </th>
<th> Data Size </th>
<th> Description
</th>
</tr>
<tr valign="top">
<th> key_resource
</th>
<td> INT </td>
<td> 128
</td>
<td> Joint PK with key below. This is the resource Id the
category is for.
</td>
</tr>
<tr valign="top">
<th> key_resource_category
</th>
<td> INT </td>
<td> 128
</td>
<td> Joint PK with key above. This is the category that is to be
related to the resource.
</td>
</tr>
</tbody>
</table>
<table border="1">
<caption> Resource Category Type Data Table
</caption><tbody>
<tr>
<th> Field Name </th>
<th> Data Type </th>
<th> Data Size </th>
<th> Description
</th>
</tr>
<tr valign="top">
<th> key
</th>
<td> INT </td>
<td> 128
</td>
<td> Primary key - uniquely identified resource category.
</td>
</tr>
<tr valign="top">
<th> name
</th>
<td> TEXT </td>
<td> 0
</td>
<td> Resource category name. "book", "news article", "opinion
article" etc.
</td>
</tr>
<tr valign="top">
<th> description
</th>
<td> TEXT </td>
<td> 0
</td>
<td> Textual description of the category.
</td>
</tr>
</tbody>
</table>
<p><br>
</p>
<table border="1">
<caption> Resource Content Category Relational Table
</caption><tbody>
<tr>
<th> Field Name </th>
<th> Data Type </th>
<th> Data Size </th>
<th> Description
</th>
</tr>
<tr valign="top">
<th> key_resource
</th>
<td> INT </td>
<td> 128
</td>
<td> Joint PK with key below. This is the resource Id the
category is for.
</td>
</tr>
<tr valign="top">
<th> key_resource_category
</th>
<td> INT </td>
<td> 128
</td>
<td> Joint PK with key above. This is the category that is to be
related to the resource.
</td>
</tr>
</tbody>
</table>
<table border="1">
<caption> Resource Content Category Type Data Table
</caption><tbody>
<tr>
<th> Field Name </th>
<th> Data Type </th>
<th> Data Size </th>
<th> Description
</th>
</tr>
<tr valign="top">
<th> key
</th>
<td> INT </td>
<td> 128
</td>
<td> Primary key - uniquely identified resource content category.
</td>
</tr>
<tr valign="top">
<th> name
</th>
<td> TEXT </td>
<td> 0
</td>
<td> Resource category name. "game history", "game culture",
"legal", "preview", "review", "discussion" - the larger tags.
</td>
</tr>
<tr valign="top">
<th> description
</th>
<td> TEXT </td>
<td> 0
</td>
<td> Textual description of the category.
</td>
</tr>
</tbody>
</table>
<br>
<br>
Andrew<br>
<br>
Andrew Armstrong wrote:
<blockquote cite="mid:49D8CA33.5020008@aarmstrong.org" type="cite">
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
Sounds good, the rating thing was probably going to be for articles
highly related to preservation - if we add an article, it implies it is
a good source for *something* but not necessarily historical work - the
way a game is made is useful for certain types of research into that
game for instance, but not generally historical, whereas why a game was
made and what went on when it was made in the company might be better.<br>
<br>
Will have to think if it it just needs a simple "Yes/No" for "Highly
useful" or whatever it is given. Might need to fine tune it more - if
it is useful for information and accuracy on "X" but not on "Y".<br>
<br>
Must reads is a key part - key texts need to be added for general work,
and I've noted down your other fields - I forgot publisher etc.! :)<br>
<br>
Andrew<br>
<br>
Devin Monnens wrote:
<blockquote
cite="mid:b96706b70904031156g24afef50x97d9f9c694341418@mail.gmail.com"
type="cite">
<div>Andrew,</div>
<div> </div>
<div>Sounds like a good idea. I'd say required fields are the
things
we generally use for references:</div>
<div> </div>
<div>Author, title of work, title of source, publication
information.
ISBN is also useful, as would be a mention of other places the article
appears.</div>
<div> </div>
<div>Commentary and rating system can be useful, but I would
suggest
that the rating system (say 5 stars) could be out of context - not
useful in what way? The article may be very good, but if the article
has nothing to do with preservation, then why rate it highly?</div>
<div> </div>
<div>I also think when possible we should have a collection of
essays
that have been written on the site. This might not be possible with
some texts, but we could at least do an external link to them (say
through Google books or the like).</div>
<div> </div>
<div>Anyway, this will be a great project. I think we definitely
need
a list of 'must reads' because this indicates sort of the canon of
digital media preservation (and preservation in general). We can also
try to organize based on who is workign with what - so for the papers
coming out of Europe, we can indicate which archives or universities
they are working with and perhaps who is connected with that, too.</div>
<div> </div>
<div>-Devin Monnens<br>
<br>
</div>
<div class="gmail_quote">On Thu, Apr 2, 2009 at 1:13 PM, Andrew
Armstrong <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:andrew@aarmstrong.org">andrew@aarmstrong.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0px 0px 0px 0.8ex; padding-left: 1ex;">Hey
all,<br>
<br>
I'll probably get the other projects' ideas more fleshed out in the
coming weeks (people who take over a project can sort their own parts
though of course :) ), but this one is immediately in my mind and could
use some good comments early on.<br>
<br>
Basically, me and Devin discussed a Bibliography - a list of resources,
from the normal books to web articles to other media. It would replace
our current "Resources" list, which is a nightmare to edit and check
though!<br>
<br>
If anyone has any thoughts on these points, or anything I've forgotten,
would be ace:<br>
* What kind of fields would be useful to have for each entry (author,
name, URL, ISBN/ISSN and keywords are obvious, any others?)<br>
* Categories of resources<br>
** by type - such as "book", "news article", "opinion article"...?<br>
** and also content - "game history", "game culture", "legal",
"preview", "review", "discussion"...? not sure...<br>
* Should I add in a way to reference the game(s) the article might
refer to?<br>
* Should there be a facility to either add the entire text of an
article (so it is searchable, ala google books) or at perhaps at least
an extract to the entry?<br>
* Should there be a "importance" field - basically our opinion on how
"useful" some resource is? This might help pick out the "Must
reference" resources perhaps.<br>
* I think there should be a facility to have an editor-added comment on
the content of the article - the description, as it were. Thoughts?<br>
* Who wants to help add entries? :) it'll be editor run (with, I hope,
publicly hidden histories kinda like a wiki) perhaps with some facility
to have users submit entries. Editing with ease is going to be the
priority.<br>
<br>
I was going to build a basic site to accommodate this for the mean time
(it won't be on the IGDA's own server, I'd rather not fight to get
webspace right now with Jason leaving who was the webmaster ;) ), and
just basically get it up and running so people can add items. So, a
simple PHP site, since I know some basic PHP :) I'd build it
"correctly" since I want to expand this if it is useful, but I hope
it'll be quick - so the layout will start absolutely horribly at first
of course, heh.<br>
<br>
Andrew<br>
_______________________________________________<br>
game_preservation mailing list<br>
<a moz-do-not-send="true" href="mailto:game_preservation@igda.org"
target="_blank">game_preservation@igda.org</a><br>
<a moz-do-not-send="true"
href="http://six.pairlist.net/mailman/listinfo/game_preservation"
target="_blank">http://six.pairlist.net/mailman/listinfo/game_preservation</a><br>
</blockquote>
</div>
<br>
<br clear="all">
<br>
-- <br>
The sleep of Reason produces monsters.<br>
<br>
"Until next time..."<br>
Captain Commando<br>
<pre wrap=""><hr size="4" width="90%">
_______________________________________________
game_preservation mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:game_preservation@igda.org">game_preservation@igda.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://six.pairlist.net/mailman/listinfo/game_preservation">http://six.pairlist.net/mailman/listinfo/game_preservation</a>
</pre>
</blockquote>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
game_preservation mailing list
<a class="moz-txt-link-abbreviated" href="mailto:game_preservation@igda.org">game_preservation@igda.org</a>
<a class="moz-txt-link-freetext" href="http://six.pairlist.net/mailman/listinfo/game_preservation">http://six.pairlist.net/mailman/listinfo/game_preservation</a>
</pre>
</blockquote>
</body>
</html>