1,298
edits
Changes
Jump to navigation
Jump to search
initial observations
Notes about what will be required to convert from Datapages format to MediaWiki wikitext.
==Article information==
We will need to decide if we want to preserve book information. One approach is to build 'canonical' book content in a separate namespace. But this will effectively be obsolete as soon as the wiki version is edited (Nupedia/Wikipedia story). SPE did this. SEG have sort of done this too. It could be confusing for readers (two versions of everything).
The article info is semantically tagged (yay!). Everything after <code><nowiki><HR></nowiki></code> and before <code><CJSTEXT></code> is header information about the article — book name, volume number, page range, etc:
<pre>
<P><STRONG>Pub. Id:</STRONG> <CJSVOLUME>A095</CJSVOLUME> (<CJSYEAR>1992</CJSYEAR>)</P><P><STRONG>First Page:</STRONG> <CJSFIRSTPAGE>463</CJSFIRSTPAGE></P>
<P><STRONG>Last Page:</STRONG> <CJSLASTPAGE>468</CJSLASTPAGE></P>
<P><STRONG>Book Title:</STRONG> <CJSPUBTITLE>ME 10: Development Geology Reference Manual</CJSPUBTITLE></P>
<P><STRONG>Article/Chapter:</STRONG> <CJSTITLE>Well Completions: Part 9. Production Engineering Methods</CJSTITLE></P>
<P><STRONG>Subject Group:</STRONG> <CJSTOPIC>Oil--Methodology and Concepts</CJSTOPIC></P>
<P><STRONG>Spec. Pub. Type:</STRONG> <CJSTYPE>Methods in Exploration</CJSTYPE></P>
<P><STRONG>Pub. Year:</STRONG> <CJSVOLUMEYEAR>1992</CJSVOLUMEYEAR></P>
<P><STRONG>Author(s):</STRONG> <CJSAUTHOR>Stephen A. Holditch</CJSAUTHOR></P>
<P><STRONG>Text:</STRONG></P>
</pre>
==Technical content==
Everything after <code><CJSTEXT></code> and before <code></CJSTEXT></code> is the text of the article.
Some things need to be converted:
* Delete the <code><nowiki><P></nowiki></code> and <code><nowiki><BR></nowiki></code> tags
===Headings===
Headings can be interpreted, per these examples:
* H1, article name — <code><nowiki><P><STRONG>PERFORATING</STRONG></P></nowiki></code>
* H2, section name — <code><nowiki><P><STRONG>Types of Guns</STRONG></P></nowiki></code>
* H3, subsection name — <code><nowiki><P ALIGN=CENTER><STRONG>Expendable Gun</STRONG></P></nowiki></code>
They all need to be converted to sentence case.
===Figures===
First mention of a figure, e.g. '''Figure 1''', should trigger a file call:
: <code>[[File:<filename.jpg>|thumb|Fig. 1 — Caption.]]</code>
The actual figure references — which might come before or after the mention in the text, looks like this:
<pre>
<P><STRONG>Fig. 1. Wellbore diagram of (a) an open hole completion and (b) a slotted liner completion.</STRONG></P>
</pre>
If we're very cunning, we can gather the file calls, gather the actual figure references, and match them up, so that the figure caption is inserted into the file call.
An alternative approach, which would require us to write an extension I think (I can't find one), would be to upload the images using their captions as the file description (if available). Then we could ask for the description when we call the file, either with a magic word or via a template (less good, because it breaks the way to make an image call):
<pre>
[[File:Myfile.jpg|thumb|{{DESCRIPTION}}]]
</pre>
or
<pre>
{{fig | 3.2
| myfile.jpg
| Caption text.
| Smith et al. 2006
}}
</pre>
===Lists===
Horrible. Here's an example:
<pre>
<P>-- Slotted liner<BR>
-- Screen and liner<BR>
-- Cemented liner</P>
</pre>
This will become:
<pre>
* Slotted liner
* Screen and liner
* Cemented liner
</pre>
To do this:
* Interpret such a block as a list: perhaps lines that start with <code>--[SPACE]</code>
* Delete the <code><nowiki><P></nowiki></code> and <code><nowiki><BR></nowiki></code> tags.
* Replace <code>--</code> with <code>*</code>
Similar thing for ordered lists:
<pre>
<P>1. Expendable gun<BR>
2. Semi-expendable gun<BR>
3. Retrievable, hollow carrier gun</P>
</pre>
Some things can be removed:
* Everything in <code><nowiki><BLOCKQUOTE></nowiki></code> tags is page information we won't want in the wiki
==Article information==
We will need to decide if we want to preserve book information. One approach is to build 'canonical' book content in a separate namespace. But this will effectively be obsolete as soon as the wiki version is edited (Nupedia/Wikipedia story). SPE did this. SEG have sort of done this too. It could be confusing for readers (two versions of everything).
The article info is semantically tagged (yay!). Everything after <code><nowiki><HR></nowiki></code> and before <code><CJSTEXT></code> is header information about the article — book name, volume number, page range, etc:
<pre>
<P><STRONG>Pub. Id:</STRONG> <CJSVOLUME>A095</CJSVOLUME> (<CJSYEAR>1992</CJSYEAR>)</P><P><STRONG>First Page:</STRONG> <CJSFIRSTPAGE>463</CJSFIRSTPAGE></P>
<P><STRONG>Last Page:</STRONG> <CJSLASTPAGE>468</CJSLASTPAGE></P>
<P><STRONG>Book Title:</STRONG> <CJSPUBTITLE>ME 10: Development Geology Reference Manual</CJSPUBTITLE></P>
<P><STRONG>Article/Chapter:</STRONG> <CJSTITLE>Well Completions: Part 9. Production Engineering Methods</CJSTITLE></P>
<P><STRONG>Subject Group:</STRONG> <CJSTOPIC>Oil--Methodology and Concepts</CJSTOPIC></P>
<P><STRONG>Spec. Pub. Type:</STRONG> <CJSTYPE>Methods in Exploration</CJSTYPE></P>
<P><STRONG>Pub. Year:</STRONG> <CJSVOLUMEYEAR>1992</CJSVOLUMEYEAR></P>
<P><STRONG>Author(s):</STRONG> <CJSAUTHOR>Stephen A. Holditch</CJSAUTHOR></P>
<P><STRONG>Text:</STRONG></P>
</pre>
==Technical content==
Everything after <code><CJSTEXT></code> and before <code></CJSTEXT></code> is the text of the article.
Some things need to be converted:
* Delete the <code><nowiki><P></nowiki></code> and <code><nowiki><BR></nowiki></code> tags
===Headings===
Headings can be interpreted, per these examples:
* H1, article name — <code><nowiki><P><STRONG>PERFORATING</STRONG></P></nowiki></code>
* H2, section name — <code><nowiki><P><STRONG>Types of Guns</STRONG></P></nowiki></code>
* H3, subsection name — <code><nowiki><P ALIGN=CENTER><STRONG>Expendable Gun</STRONG></P></nowiki></code>
They all need to be converted to sentence case.
===Figures===
First mention of a figure, e.g. '''Figure 1''', should trigger a file call:
: <code>[[File:<filename.jpg>|thumb|Fig. 1 — Caption.]]</code>
The actual figure references — which might come before or after the mention in the text, looks like this:
<pre>
<P><STRONG>Fig. 1. Wellbore diagram of (a) an open hole completion and (b) a slotted liner completion.</STRONG></P>
</pre>
If we're very cunning, we can gather the file calls, gather the actual figure references, and match them up, so that the figure caption is inserted into the file call.
An alternative approach, which would require us to write an extension I think (I can't find one), would be to upload the images using their captions as the file description (if available). Then we could ask for the description when we call the file, either with a magic word or via a template (less good, because it breaks the way to make an image call):
<pre>
[[File:Myfile.jpg|thumb|{{DESCRIPTION}}]]
</pre>
or
<pre>
{{fig | 3.2
| myfile.jpg
| Caption text.
| Smith et al. 2006
}}
</pre>
===Lists===
Horrible. Here's an example:
<pre>
<P>-- Slotted liner<BR>
-- Screen and liner<BR>
-- Cemented liner</P>
</pre>
This will become:
<pre>
* Slotted liner
* Screen and liner
* Cemented liner
</pre>
To do this:
* Interpret such a block as a list: perhaps lines that start with <code>--[SPACE]</code>
* Delete the <code><nowiki><P></nowiki></code> and <code><nowiki><BR></nowiki></code> tags.
* Replace <code>--</code> with <code>*</code>
Similar thing for ordered lists:
<pre>
<P>1. Expendable gun<BR>
2. Semi-expendable gun<BR>
3. Retrievable, hollow carrier gun</P>
</pre>
Some things can be removed:
* Everything in <code><nowiki><BLOCKQUOTE></nowiki></code> tags is page information we won't want in the wiki