Fwd: Image include problem
19 views
Skip to first unread message
Julie Meloni
Aug 3, 2010, 3:53:55 PM8/3/10
to antholo...@googlegroups.com
Moving this from anthologize-users. This does look like a path problem.
Steve?
---------- Forwarded message ----------
From: Christiann <csm...@gmail.com>
Date: Tue, Aug 3, 2010 at 3:52 PM
Subject: Image include problem
To: anthologize-users <antholog...@googlegroups.com>
I just thought I'd make a quick test anthology with 12 posts from my
webcomic and got an image error. Looks like a bad path.
Here's the error message:
Warning: Invalid argument supplied for foreach() in /home/xiann/
stickycomics3/wpsite/wp-content/plugins/anthologize/includes/class-tei-
dom.php on line 196
TCPDF ERROR: [Image] Unable to get image: /home/xiann/stickycomics3/
wpsite/wp-content/plugins/anthologize/includes/tcpdf//wp-content/
uploads/oyster_tumor.jpg
Thanks,
Christiann
http://stickycomics.com
Boone B. Gorges
Aug 3, 2010, 3:54:57 PM8/3/10
to antholo...@googlegroups.com
This is the same old path concatenation problem. path_to_tcpdf//wp-content... is not the correct image path; it should just be /wp-content/uploads...
Mark Sample
Aug 3, 2010, 6:53:58 PM8/3/10
to anthologize-dev
It looks like this thread is dedicated to the tcpdf problem, but I've
noticed that none of my images are being published, no matter what
format I use. Neither epub nor rtf exports have included my images.
On Aug 3, 3:54 pm, "Boone B. Gorges" <boonebgor...@gmail.com> wrote:
> This is the same old path concatenation problem.
> path_to_tcpdf//wp-content... is not the correct image path; it should just
> be /wp-content/uploads...
>
noticed that none of my images are being published, no matter what
format I use. Neither epub nor rtf exports have included my images.
On Aug 3, 3:54 pm, "Boone B. Gorges" <boonebgor...@gmail.com> wrote:
> This is the same old path concatenation problem.
> path_to_tcpdf//wp-content... is not the correct image path; it should just
> be /wp-content/uploads...
>
Patrick Murray-John
Aug 3, 2010, 8:06:30 PM8/3/10
to antholo...@googlegroups.com
Mark,
Hmm...could I ask you to try to do a TEI export, and email the results
to me? That's the lowest level of processing, and will let me take a
look at the most basic output.
Thanks!
Patrick
--
Patrick Murray-John
Instructional Technology Specialist
University of Mary Washington
540-654-1510
http://cv.patrickgmj.net
Mark Sample
Aug 4, 2010, 12:25:59 PM8/4/10
to anthologize-dev
Patrick, it looks like I don't have privileges on the Google Group to
upload a file, so I'm going to paste it right here. This is my TEI
export:
<?xml version="1.0" encoding="UTF-8" ?>
- <TEI xmlns="http://www.tei-c.org/ns/1.0">
- <teiHeader>
- <fileDesc>
- <titleStmt>
<title>Own Your Ideas.</title>
</titleStmt>
- <editionStmt>
<edition />
</editionStmt>
- <publicationStmt>
- <availability>
<p>Copyright 2010,</p>
<p>Creative Commons By</p>
</availability>
<date>2010</date>
</publicationStmt>
- <sourceDesc>
- <bibl>
- <ident>
- <![CDATA[ http://www.samplereality.com/project/own-your-ideas/
]]>
</ident>
</bibl>
</sourceDesc>
</fileDesc>
- <!-- I think the right place to gather metadata will be in the
encodingDesc. Would appreciate it if others with TEI skill commented
about that.
-->
- <outputParams xmlns="http://www.anthologize.org/ns">
<param name="paper-type">letter</param>
<param name="page-width">8.5in</param>
<param name="page-height">11in</param>
<param name="font-size">12</param>
<param name="font-family">times</param>
</outputParams>
- <encodingDesc>
- <refsDecl>
- <ab type="metadata" subtype="authors">
- <!-- the anonymous block might be the best way hold metadata about
people (and more?) without making TEI mad
-->
- <listPerson>
- <person xml:id="admin" role="administrator">
- <persName>
<forename xmlns:tei="http://www.tei-c.org/ns/1.0">Mark</forename>
<surname xmlns="http://www.tei-c.org/ns/1.0">Sample</surname>
- <ident xmlns="http://www.tei-c.org/ns/1.0" type="url">
- <![CDATA[ http://www.samplereality.com
]]>
</ident>
</persName>
</person>
</listPerson>
</ab>
</refsDecl>
- <appInfo>
- <application ident="anthologize" version="0.3">
<label>Anthologize</label>
<desc>Bits to Bookshelf</desc>
- <p>
<graphic url="http://anthologize.org/wp-content/themes/anthologize/
images/anthologize_web_final.png" />
</p>
</application>
</appInfo>
</encodingDesc>
</teiHeader>
- <text>
- <front>
- <titlePage>
- <docTitle>
<titlePart type="main">Own Your Ideas.</titlePart>
<titlePart type="sub" />
</docTitle>
<docAuthor>,</docAuthor>
<docDate>2010-08-03 11:44:30</docDate>
<docEdition />
</titlePage>
- <div xml:id="f1">
- <head>
<title>Dedication</title>
</head>
- <body xmlns="http://www.w3.org/1999/xhtml">
<p />
</body>
</div>
- <div xml:id="f2">
- <head>
<title>Acknowledgements</title>
</head>
- <body xmlns="http://www.w3.org/1999/xhtml">
<p />
</body>
</div>
</front>
- <body>
- <div type="part">
- <head>
<title>What Your Readers Will Never Read</title>
- <ident type="guid">
- <![CDATA[ http://www.samplereality.com/?post_type=parts&p=1390
]]>
</ident>
- <bibl>
<author ref="admin" />
</bibl>
</head>
- <div type="libraryItem" subtype="html">
- <head>
<title>One Week, One Tool, Many Anthologies</title>
- <ident type="guid">
- <![CDATA[
http://www.samplereality.com/library_item/own-your-ideas/what-your-readers-will-never-read/one-week-one-tool-many-anthologies/
]]>
</ident>
- <bibl>
<author ref="admin" />
</bibl>
</head>
- <body xmlns="http://www.w3.org/1999/xhtml">
- <p>
Many of you have already heard about
<a id="aptureLink_v9RgCNyd70" href="http://
anthologize.org/">Anthologize</a>
, the blog-to-book publishing tool created in
<a href="http://oneweekonetool.org/">one week</a>
by a crack team of
<a href="http://oneweekonetool.org/people/">twelve digital
humanists</a>
, funded by the NEH's
<a href="http://www.neh.gov/ODH/ODHUpdate/tabid/108/EntryId/140/
Report-from-ODH-Institute-One-Week-One-Tool.aspx">Office of Digital
Humanities</a>
, and shepherded by George Mason University's
<a id="aptureLink_Oi1ZGALAL6" href="http://chnm.gmu.edu/">Center for
History and New Media</a>
. Until the moment of the tool's unveiling on Tuesday, August 3,
very few people knew what the tool was going to be. That would include
me. So, it was entirely coincidental that the night before
Anthologize's release, I tweeted:
</p>
- <p style="text-align: center;">
- <a href="http://www.samplereality.com/wp-content/uploads/
2010/08/1stdraftscholarship.jpg">
<img class="aligncenter size-medium wp-image-1397"
title="1stdraftscholarship" src="http://www.samplereality.com/wp-
content/uploads/2010/08/1stdraftscholarship-450x257.jpg" alt=""
width="360" height="206" />
</a>
</p>
I had no idea that the One Week Team was working on a WordPress
plugin that could take our blogs and turn them into formats suitable
for e-readers or publishers like
<a id="aptureLink_MAxQplr6WF" href="http://www.lulu.com/">Lulu.com</
a>
(the exportable formats include ePub, PDF, RTF, and TEI...so far).
When I got a sneak preview of Anthologize via the outreach team's
press kit, it was only natural that I revisit my previous night's
tweet, with this update:
- <p style="text-align: center;">
- <a href="http://www.samplereality.com/wp-content/uploads/2010/08/
betterbinding.jpg">
<img class="aligncenter size-medium wp-image-1398"
title="betterbinding" src="http://www.samplereality.com/wp-content/
uploads/2010/08/betterbinding-450x234.jpg" alt="" width="360"
height="187" />
</a>
</p>
I'm willing to stand behind this statement---Twitter and Blogs are
the first drafts of scholarship. All they need are better binding---
and I'm even more willing to argue that Anthologize can provide that
binding. But the genius of Anthologize isn't that it lets you turn
blog posts into PDFs. They are already many ways to do this. The
genius of the tool is the way it lets you
<em>remix</em>
a blog into a bound object. A quick look at the manage project page
(
<a href="http://www.samplereality.com/wp-content/uploads/2010/08/
ManageProject.jpg">larger image</a>
) will show how this works:
- <a href="http://www.samplereality.com/wp-content/uploads/2010/08/
ManageProject.jpg">
<img class="aligncenter size-medium wp-image-1400"
title="ManageProject" src="http://www.samplereality.com/wp-content/
uploads/2010/08/ManageProject-450x258.jpg" alt="" width="450"
height="258" />
</a>
All of your blog's posts are listed in the left column, and you can
filter them by tag or category. Then you drag-and-drop specific posts
into the "Parts" column on the right side of the page. Think of each
Part as a separate section or chapter of your final anthology. You can
easily create new parts, and rearrange the parts and posts until
you've found the order you're looking for. Using the "Import Content"
tool that's built into Anthologize, you aren't even limited to your
own blog postings. You can import anything that has an RSS feed, from
Twitter updates to feeds from entirely different blogs and blogging
platforms (such as Movable Type or Blogger). You can
<em>remix</em>
from a countless number of sources, and then compile it all together
into one slick file. This remixing isn't simply an afterthought of
Anthologize. It defines the plugin and has enormous potential for
scholars and teachers alike, ranging from organizing tenure material
to building student portfolios. Something else that's neat about how
Anthologize pulls in content is that draft (i.e. unpublished) posts
show up alongside published posts in the left hand column. In other
words, drafts can be published in your Anthologize project, even if
they were never actually published on your blog. This feature makes it
possible to create Anthologize projects without even making the
content public first (though why would you want to?).
<h3>From Alpha to Beta to You</h3>
As excited as I am about the possibilities of Anthologize, don't be
misled into thinking that the tool is a ready-to-go, full-fledged
publishing solution. Make no mistake about Anthologize: this is an
extremely alpha version of the final plugin. If the Greeks had a
letter that came before alpha, Anthologize would be it. There are
several major
<a href="http://anthologize.org/download-plugin/">known issues</a>
, and there are many features yet to add. But don't forget:
<em>Anthologize was developed in under 200 hours.</em>
There were no months-long team meetings, no protracted management
decisions, no obscene Gantt charts. The team behind Anthologize came
and saw and coded, from brainstorm to repository in one week.
<h2 class="insertright">The team behind Anthologize came and saw and
coded, from brainstorm to repository in one week.</h2>
The week is over, and they're still working, but now it's your turn
too. Try it out, and let the team know what works, what doesn't, what
you might use it for, and what you'd like to see in the next version.
There's an
<a href="http://groups.google.com/group/anthologize-
users">Anthologize Users Group</a>
you can join to share with other users and the official outreach
team, and there's also the
<a href="http://groups.google.com/group/anthologize-dev">Anthologize
Development Group</a>
, where you can share your bugs and issues directly with the
development team. As for me, I'm already working on a wishlist of what
I'd like to see in Anthologize. Here are just a few thoughts:
- <ul>
<li>More use of metadata. I imagine future releases will allow user-
selected metadata to be included in the Anthologized content. For
example, it'd be great to have the option of including the original
publication date.</li>
<li>Cover images. It's already possible to include custom
acknowledgments and dedications in the opening pages of the
Anthologized project, but it'll be crucial to be able to include a
custom image as the anthology front cover.</li>
<li>Preservation of formatting. Right now quite a bit of formatting
is stripped away when posts are anthologized. Block quotes, for
example, become indistinguishable from the rest of the text, as do
many headers and titles.</li>
<li>Fine-grained image control. A major bug prevents many blog post
images from showing up in the Anthologize-generated book. Once this is
fixed, it'd be wonderful to have even greater control of images (such
as image resolution, alignment, and captions).</li>
<li>I haven't experimented with Anthologize on WordPressMU or
BuddyPress yet, but it's a natural fit. Imagine each user being able
to cull through tons of posts on a multi-user blog, and publishing a
custom-made portfolio, comprised of posts that come from different
users and different blogs.</li>
</ul>
As I play with Anthologize, talk with the developers, and share with
other users, I'm sure I'll come up with more suggestions for features,
as well as more ways Anthologize can be used
<em>right now, as is</em>
. I encourage you to do the same. You'll join a growing contingent
of researchers, teachers, archivists, librarians, and students who are
part of an open-source movement, but more importantly, part of a
movement to change the very nature of how we construct and share
knowledge in the 21st century.
</body>
</div>
- <div type="libraryItem" subtype="html">
- <head>
<title>Haunts: Place, Play, and Trauma</title>
- <ident type="guid">
- <![CDATA[
http://www.samplereality.com/library_item/own-your-ideas/what-your-readers-will-never-read/haunts-place-play-and-trauma/
]]>
</ident>
- <bibl>
<author ref="admin" />
</bibl>
</head>
- <body xmlns="http://www.w3.org/1999/xhtml">
- <p>
Foursquare and its brethren (Gowalla, Brightkite, Loopt, and so on)
are the latest social media darlings, but honestly, are they really
all that useful? Sharing your location with your friends is not very
compelling when you spend your life in the same four places (home,
office, classroom, coffee shop). Are these apps really even
<em>fun</em>
? Does becoming the Mayor of a
<a href="http://foursquare.com/venue/677464">Shell</a>
filling station or earning the Crunked badge for checking into four
different airport terminals on the same night* count as fun? I hope
not. In truth,
<a id="aptureLink_nqiUnfUBbv" href="http://twitter.com/samplereality/
statuses/8233069460">making fun of Foursquare</a>
is more fun than actually using Foursquare.
<em>*The Crunked badge is for checking into four separate locations
during a single evening. They don't all have to be airport terminals.
That's just my own quirk.</em>
</p>
- <p style="text-align: left;">
- <em>
<img class="aligncenter size-medium wp-image-1172" style="border:
0pt none; margin-top: 5px; margin-bottom: 5px;" title="Foursquare
Crunked Badge" src="http://www.samplereality.com/wp-content/uploads/
2010/05/Crunked-450x179.jpg" alt="" width="450" height="179" />
</em>
Aside from the free chips I got for checking into a
<a href="http://foursquare.com/venue/46542">California Tortilla</a>
, the only redeeming value of these geolocation apps is that they
offer the slightest glimmer---
<em>a glimmer!</em>
---of creative and pedagogical use. While some of the benefits of
geolocation have been immediately seized upon by museums and
historians---think of the partnership between
<a href="http://techcrunch.com/2010/04/22/foursquare-history-
channel/">Foursquare and the History Channel</a>
---very few people have considered using geolocation in a literary
context. Even less attention has been paid to the ways geolocation can
foster critical and creative thinking. So I've been pondering re-
purposing Foursquare and its ilk in ways unintended and unforeseen by
their creators.
</p>
<h2 class="insertright">Let's turn locative media into platforms for
renegotiating space and telling stories</h2>
Following Rob MacDougall's call for
<a href="http://www.robmacdougall.org/index.php/2010/03/playful-
historical-thinking/">playful historical thinking</a>
, I've been imagining what you could call playful geographic
thinking. Let's turn locative media from gimmicky Entertainment coupon
books and glorified historical guidebooks into platforms for
renegotiating space and telling stories. Let's turn them into
something that truly resembles play. And here I'll use
<a id="aptureLink_7JdY40qLl9" href="http://www.amazon.com/gp/product/
0262240459?tag=sampreal-20">Eric Zimmerman and Katie Salen's concept
of play</a>
:
<em>free movement within a more rigid structure.</em>
In this case, that rigid structure comes from the core mechanics of
the different geolocation apps: checking in and tagging specific
places with tips or comments. What's
<em>supposed to happen</em>
is that users check in to bars or restaurants and then post tips on
the best drinks or bargains. But what
<em>can</em>
<em>happen</em>
, given the free movement within this structure, is that users can
define their own places and add tips that range from lewd to absurd.
This is exactly what Dean Terry is doing. Along with his colleagues
and students at the
<a href="http://emac.utdallas.edu/about/">Emerging Media and
Communication</a>
program at the University of Texas at Dallas, Dean has been renaming
spaces and
<a href="http://www.deanterry.com/blog/index.php/location-literacy-
foursquare-in-the-classroom/">making his own places</a>
. Even better, Dean and his group at the MobileLab at UT Dallas are
not only testing the limits of existing geolocation apps, they're
<a href="http://www.placethings.com/">building one</a>
of their own. I'm not designing my own app, but I am playing with
the commercial apps. And again, by
<em>playing</em>
,
<em />
I mean moving freely within a larger, more constrained structure.
For instance, within my dully named campus office building, Robinson
A, I've created my own space,
<a href="http://foursquare.com/venue/1867417">The Office of
Incandescent Light and Industrial Runoff</a>
. Which is pretty much how I think of my office. And I'm mayor
there, thank you very much. Likewise, when I'm home, I often check
into the
<a href="http://foursquare.com/venue/3715999">Treehouse of Sighs</
a>
. I have an actual
<a id="aptureLink_VAjFEaiL4o" href="http://www.flickr.com/photos/
samplereality/4648624179/">treehouse</a>
there, but the Treehouse of Sighs is not that one. The Treehouse of
Sighs exists only in my mind. It's a metaphysical Hotel California.
You can check in any time you like, but you can never be there. Just
as evocative as creating your own space is tagging existing spaces
with virtual graffiti, which you can use to create a counter-factual
history of a place. Anyone who checks into the Starbucks on my campus
can see my advice regarding
<a id="aptureLink_xRqhtx4QvG" href="http://apture.s3.amazonaws.com/
00000128e25ea0127e7784ce007f000000000001.Starbucks.jpg">the fireplace
there</a>
. Also on GMU's campus, I've uncovered Fenwick Library's
<a id="aptureLink_lE3mZDNKNG" href="http://apture.s3.amazonaws.com/
00000128f3c7ad96e2afaee8007f000000000001.Fenwick%20Tacos.jpg">dirty
little secret</a>
. And sometimes I leave surrealist tips in public places, like this
epigram in yet another airport terminal:
- <p style="text-align: center;">
- <a href="http://foursquare.com/item/791648">
<img class="aligncenter size-medium wp-image-1185" style="border:
0pt none;" title="ZGate" src="http://www.samplereality.com/wp-content/
uploads/2010/05/ZGate-450x117.jpg" alt="" width="450" height="117" />
</a>
</p>
All of this play has led me to think about using geolocative media
with my students. Next spring I'm teaching an undergraduate class
called "Textual Media," a vague title that I've taken to describing as
post-print fiction. My initial idea for using Foursquare was to have
students add new venues to the app's database, with the stipulation
that these new venues be Foucauldian "Other Spaces"---parking decks,
overpasses, bus depots, etc.---that stand in sharp contrast to the
officially sanctioned places on Foursquare (coffee shops, restaurants,
bars, etc.). One of the points I'd like to make is that much of our
lives are actually spent in these nether-places that are neither here
nor there. Tracking our movements in these unglamorous but not
unimportant unplaces could be a revelation to my students. It might
actually be one of the best uses of geolocation---to defamiliarize our
daily surroundings. I recently participated in a geolocation session
at
<a href="http://thatcamp.org/about/">THATCamp</a>
that helped me refine some of these ideas. We had about fifteen
historians, librarians, archivists, literary scholars, and other
humanists at the session. We broke off into groups, with the mission
of hacking existing geolocation apps for teaching or learning. I
worked with
<a href="http://twitter.com/cwillifo">Christa Willaford</a>
and
<a href="http://twitter.com/jenksbyjenks">Christina Jenkins</a>
, and as befits brainstorming about space, we left the windowless
room, left the building entirely, and stood out near a small field
(that's not even on the
<a id="aptureLink_1gU3GpXesZ" href="http://maps.google.com/maps?
om=0&iwloc=addr&f=q&ll=38.827748%2C-77.305416&t=k&hl=en&z=18&ie=UTF8">outdated
satellite image</a>
of the place) and came up with the idea we called
<em>Haunts</em>
.
<em>Haunts</em>
is about the secret stories of spaces.
<em>Haunts</em>
is about locative trauma.
<em>Haunts</em>
is about the production of what Foucault calls "heterotopias"---a
single real place in which incompatible counter-sites are layered upon
or juxtaposed against one another. The general idea behind
<em>Haunts</em>
is this: students work in teams, visiting various public places and
tagging them with fragments of either a real life-inspired or
fictional trauma story. Each team will work from an overarching
traumatic narrative that they've created, but because the place-based
tips are limited to text-message-sized bits, the story will emerge
only in glimpses and traces, across a series of spaces.
<h2 class="insertleft">They've stumbled upon a fictional world
haunting the real one.</h2>
Emerge for whom? For the other teams in the class. But also for
random strangers using the apps, who have no idea that they've
stumbled upon a fictional world augmenting the real one. A fictional
world haunting the real one. There are several twists that make
<em>Haunts</em>
more than simple place-based creative writing. For starters, most
fiction doesn't require any kind of breadcrumb trail more complicated
than sequential page numbers. In
<em>Haunts</em>
, however, students will need to create clues to act as what Marc
Ruppel calls
<a href="http://things.wordherders.net/archives/
005458.html">migratory cues</a>
---nudging participants from one locale to the next, from one medium
to the next. These cues might be suggestive references left in a tip,
or perhaps obliquely embedded in a photograph taken at the check-in
point. (Most geolocation apps allow photographs to be associated with
a place; Foursquare is a holdout in this regard, though third-party
services like
<a href="http://picplz.com/">picplz</a>
offer a work-around.) Another twist subverts the tendency of
geolocation apps to reward repeat visits to a single locale. Check in
enough times at your coffee shop with Foursquare and you become
"mayor" of the place.
<em>Haunts</em>
disincentivizes multiple visits. Check in too many times at the same
place and you become a "ghost." No longer among the living, you are
stuck in a single place, barred from leaving tips anywhere else. Like
a ghost, you haunt that space for the rest of the game. It's a fate
players would probably want to avoid, yet players will nonetheless be
compelled to revisit destinations, in order to fill in narrative gaps
as either writers or readers.
<h2 class="insertright">Imagine the same traumatic kernel, being
told again and again, from different points of views.</h2>
The final twist is that
<em>Haunts</em>
does not rely only upon Foursquare. All of the geolocative apps have
the same core functionality. This means that one team can use
Foursquare, while another team uses Gowalla, and yet another
Brightkite. Each team will weave parallel yet diverging stories across
the same series of spaces. Each Haunt hosts a number of haunts. The
narrative and geographic path of a single team's story should alone be
engaging enough to follow, but even more promising is a kind of cross-
pollination between haunts, in which each team builds upon one or two
shared narrative events,
<a id="aptureLink_P3xE4GR05X" href="http://en.wikipedia.org/wiki/
Exquisite%20corpse">exquisite corpse</a>
style. Imagine the same traumatic kernel, being told again and
again, from different points of views. Different narrative
<em>and</em>
geographic points of views. Eventually these multiple paths could be
aggregated onto a master narrative---or more likely, a master
database---so that
<em>Haunts</em>
could be seen (if not experienced) in its totality. There is still
much to figure out with
<em>Haunts</em>
. But I find the project compelling, and even necessary. The
endeavor turns a consumer-based model of mobile computing into an
authorship-based model. It is a uniquely collaborative activity, but
also one that invites individual introspection. It imagines trauma as
both private and public, deeply personal yet situated within shared
semiotic domains. It operates at the intersection between game and
story, between reading and writing, between the real and the virtual.
And it might finally make geolocation worth paying attention to.
</body>
</div>
</div>
</body>
<back />
</text>
</TEI>
upload a file, so I'm going to paste it right here. This is my TEI
export:
<?xml version="1.0" encoding="UTF-8" ?>
- <TEI xmlns="http://www.tei-c.org/ns/1.0">
- <teiHeader>
- <fileDesc>
- <titleStmt>
<title>Own Your Ideas.</title>
</titleStmt>
- <editionStmt>
<edition />
</editionStmt>
- <publicationStmt>
- <availability>
<p>Copyright 2010,</p>
<p>Creative Commons By</p>
</availability>
<date>2010</date>
</publicationStmt>
- <sourceDesc>
- <bibl>
- <ident>
- <![CDATA[ http://www.samplereality.com/project/own-your-ideas/
]]>
</ident>
</bibl>
</sourceDesc>
</fileDesc>
- <!-- I think the right place to gather metadata will be in the
encodingDesc. Would appreciate it if others with TEI skill commented
about that.
-->
- <outputParams xmlns="http://www.anthologize.org/ns">
<param name="paper-type">letter</param>
<param name="page-width">8.5in</param>
<param name="page-height">11in</param>
<param name="font-size">12</param>
<param name="font-family">times</param>
</outputParams>
- <encodingDesc>
- <refsDecl>
- <ab type="metadata" subtype="authors">
- <!-- the anonymous block might be the best way hold metadata about
people (and more?) without making TEI mad
-->
- <listPerson>
- <person xml:id="admin" role="administrator">
- <persName>
<forename xmlns:tei="http://www.tei-c.org/ns/1.0">Mark</forename>
<surname xmlns="http://www.tei-c.org/ns/1.0">Sample</surname>
- <ident xmlns="http://www.tei-c.org/ns/1.0" type="url">
- <![CDATA[ http://www.samplereality.com
]]>
</ident>
</persName>
</person>
</listPerson>
</ab>
</refsDecl>
- <appInfo>
- <application ident="anthologize" version="0.3">
<label>Anthologize</label>
<desc>Bits to Bookshelf</desc>
- <p>
<graphic url="http://anthologize.org/wp-content/themes/anthologize/
images/anthologize_web_final.png" />
</p>
</application>
</appInfo>
</encodingDesc>
</teiHeader>
- <text>
- <front>
- <titlePage>
- <docTitle>
<titlePart type="main">Own Your Ideas.</titlePart>
<titlePart type="sub" />
</docTitle>
<docAuthor>,</docAuthor>
<docDate>2010-08-03 11:44:30</docDate>
<docEdition />
</titlePage>
- <div xml:id="f1">
- <head>
<title>Dedication</title>
</head>
- <body xmlns="http://www.w3.org/1999/xhtml">
<p />
</body>
</div>
- <div xml:id="f2">
- <head>
<title>Acknowledgements</title>
</head>
- <body xmlns="http://www.w3.org/1999/xhtml">
<p />
</body>
</div>
</front>
- <body>
- <div type="part">
- <head>
<title>What Your Readers Will Never Read</title>
- <ident type="guid">
- <![CDATA[ http://www.samplereality.com/?post_type=parts&p=1390
]]>
</ident>
- <bibl>
<author ref="admin" />
</bibl>
</head>
- <div type="libraryItem" subtype="html">
- <head>
<title>One Week, One Tool, Many Anthologies</title>
- <ident type="guid">
- <![CDATA[
http://www.samplereality.com/library_item/own-your-ideas/what-your-readers-will-never-read/one-week-one-tool-many-anthologies/
]]>
</ident>
- <bibl>
<author ref="admin" />
</bibl>
</head>
- <body xmlns="http://www.w3.org/1999/xhtml">
- <p>
Many of you have already heard about
<a id="aptureLink_v9RgCNyd70" href="http://
anthologize.org/">Anthologize</a>
, the blog-to-book publishing tool created in
<a href="http://oneweekonetool.org/">one week</a>
by a crack team of
<a href="http://oneweekonetool.org/people/">twelve digital
humanists</a>
, funded by the NEH's
<a href="http://www.neh.gov/ODH/ODHUpdate/tabid/108/EntryId/140/
Report-from-ODH-Institute-One-Week-One-Tool.aspx">Office of Digital
Humanities</a>
, and shepherded by George Mason University's
<a id="aptureLink_Oi1ZGALAL6" href="http://chnm.gmu.edu/">Center for
History and New Media</a>
. Until the moment of the tool's unveiling on Tuesday, August 3,
very few people knew what the tool was going to be. That would include
me. So, it was entirely coincidental that the night before
Anthologize's release, I tweeted:
</p>
- <p style="text-align: center;">
- <a href="http://www.samplereality.com/wp-content/uploads/
2010/08/1stdraftscholarship.jpg">
<img class="aligncenter size-medium wp-image-1397"
title="1stdraftscholarship" src="http://www.samplereality.com/wp-
content/uploads/2010/08/1stdraftscholarship-450x257.jpg" alt=""
width="360" height="206" />
</a>
</p>
I had no idea that the One Week Team was working on a WordPress
plugin that could take our blogs and turn them into formats suitable
for e-readers or publishers like
<a id="aptureLink_MAxQplr6WF" href="http://www.lulu.com/">Lulu.com</
a>
(the exportable formats include ePub, PDF, RTF, and TEI...so far).
When I got a sneak preview of Anthologize via the outreach team's
press kit, it was only natural that I revisit my previous night's
tweet, with this update:
- <p style="text-align: center;">
- <a href="http://www.samplereality.com/wp-content/uploads/2010/08/
betterbinding.jpg">
<img class="aligncenter size-medium wp-image-1398"
title="betterbinding" src="http://www.samplereality.com/wp-content/
uploads/2010/08/betterbinding-450x234.jpg" alt="" width="360"
height="187" />
</a>
</p>
I'm willing to stand behind this statement---Twitter and Blogs are
the first drafts of scholarship. All they need are better binding---
and I'm even more willing to argue that Anthologize can provide that
binding. But the genius of Anthologize isn't that it lets you turn
blog posts into PDFs. They are already many ways to do this. The
genius of the tool is the way it lets you
<em>remix</em>
a blog into a bound object. A quick look at the manage project page
(
<a href="http://www.samplereality.com/wp-content/uploads/2010/08/
ManageProject.jpg">larger image</a>
) will show how this works:
- <a href="http://www.samplereality.com/wp-content/uploads/2010/08/
ManageProject.jpg">
<img class="aligncenter size-medium wp-image-1400"
title="ManageProject" src="http://www.samplereality.com/wp-content/
uploads/2010/08/ManageProject-450x258.jpg" alt="" width="450"
height="258" />
</a>
All of your blog's posts are listed in the left column, and you can
filter them by tag or category. Then you drag-and-drop specific posts
into the "Parts" column on the right side of the page. Think of each
Part as a separate section or chapter of your final anthology. You can
easily create new parts, and rearrange the parts and posts until
you've found the order you're looking for. Using the "Import Content"
tool that's built into Anthologize, you aren't even limited to your
own blog postings. You can import anything that has an RSS feed, from
Twitter updates to feeds from entirely different blogs and blogging
platforms (such as Movable Type or Blogger). You can
<em>remix</em>
from a countless number of sources, and then compile it all together
into one slick file. This remixing isn't simply an afterthought of
Anthologize. It defines the plugin and has enormous potential for
scholars and teachers alike, ranging from organizing tenure material
to building student portfolios. Something else that's neat about how
Anthologize pulls in content is that draft (i.e. unpublished) posts
show up alongside published posts in the left hand column. In other
words, drafts can be published in your Anthologize project, even if
they were never actually published on your blog. This feature makes it
possible to create Anthologize projects without even making the
content public first (though why would you want to?).
<h3>From Alpha to Beta to You</h3>
As excited as I am about the possibilities of Anthologize, don't be
misled into thinking that the tool is a ready-to-go, full-fledged
publishing solution. Make no mistake about Anthologize: this is an
extremely alpha version of the final plugin. If the Greeks had a
letter that came before alpha, Anthologize would be it. There are
several major
<a href="http://anthologize.org/download-plugin/">known issues</a>
, and there are many features yet to add. But don't forget:
<em>Anthologize was developed in under 200 hours.</em>
There were no months-long team meetings, no protracted management
decisions, no obscene Gantt charts. The team behind Anthologize came
and saw and coded, from brainstorm to repository in one week.
<h2 class="insertright">The team behind Anthologize came and saw and
coded, from brainstorm to repository in one week.</h2>
The week is over, and they're still working, but now it's your turn
too. Try it out, and let the team know what works, what doesn't, what
you might use it for, and what you'd like to see in the next version.
There's an
<a href="http://groups.google.com/group/anthologize-
users">Anthologize Users Group</a>
you can join to share with other users and the official outreach
team, and there's also the
<a href="http://groups.google.com/group/anthologize-dev">Anthologize
Development Group</a>
, where you can share your bugs and issues directly with the
development team. As for me, I'm already working on a wishlist of what
I'd like to see in Anthologize. Here are just a few thoughts:
- <ul>
<li>More use of metadata. I imagine future releases will allow user-
selected metadata to be included in the Anthologized content. For
example, it'd be great to have the option of including the original
publication date.</li>
<li>Cover images. It's already possible to include custom
acknowledgments and dedications in the opening pages of the
Anthologized project, but it'll be crucial to be able to include a
custom image as the anthology front cover.</li>
<li>Preservation of formatting. Right now quite a bit of formatting
is stripped away when posts are anthologized. Block quotes, for
example, become indistinguishable from the rest of the text, as do
many headers and titles.</li>
<li>Fine-grained image control. A major bug prevents many blog post
images from showing up in the Anthologize-generated book. Once this is
fixed, it'd be wonderful to have even greater control of images (such
as image resolution, alignment, and captions).</li>
<li>I haven't experimented with Anthologize on WordPressMU or
BuddyPress yet, but it's a natural fit. Imagine each user being able
to cull through tons of posts on a multi-user blog, and publishing a
custom-made portfolio, comprised of posts that come from different
users and different blogs.</li>
</ul>
As I play with Anthologize, talk with the developers, and share with
other users, I'm sure I'll come up with more suggestions for features,
as well as more ways Anthologize can be used
<em>right now, as is</em>
. I encourage you to do the same. You'll join a growing contingent
of researchers, teachers, archivists, librarians, and students who are
part of an open-source movement, but more importantly, part of a
movement to change the very nature of how we construct and share
knowledge in the 21st century.
</body>
</div>
- <div type="libraryItem" subtype="html">
- <head>
<title>Haunts: Place, Play, and Trauma</title>
- <ident type="guid">
- <![CDATA[
http://www.samplereality.com/library_item/own-your-ideas/what-your-readers-will-never-read/haunts-place-play-and-trauma/
]]>
</ident>
- <bibl>
<author ref="admin" />
</bibl>
</head>
- <body xmlns="http://www.w3.org/1999/xhtml">
- <p>
Foursquare and its brethren (Gowalla, Brightkite, Loopt, and so on)
are the latest social media darlings, but honestly, are they really
all that useful? Sharing your location with your friends is not very
compelling when you spend your life in the same four places (home,
office, classroom, coffee shop). Are these apps really even
<em>fun</em>
? Does becoming the Mayor of a
<a href="http://foursquare.com/venue/677464">Shell</a>
filling station or earning the Crunked badge for checking into four
different airport terminals on the same night* count as fun? I hope
not. In truth,
<a id="aptureLink_nqiUnfUBbv" href="http://twitter.com/samplereality/
statuses/8233069460">making fun of Foursquare</a>
is more fun than actually using Foursquare.
<em>*The Crunked badge is for checking into four separate locations
during a single evening. They don't all have to be airport terminals.
That's just my own quirk.</em>
</p>
- <p style="text-align: left;">
- <em>
<img class="aligncenter size-medium wp-image-1172" style="border:
0pt none; margin-top: 5px; margin-bottom: 5px;" title="Foursquare
Crunked Badge" src="http://www.samplereality.com/wp-content/uploads/
2010/05/Crunked-450x179.jpg" alt="" width="450" height="179" />
</em>
Aside from the free chips I got for checking into a
<a href="http://foursquare.com/venue/46542">California Tortilla</a>
, the only redeeming value of these geolocation apps is that they
offer the slightest glimmer---
<em>a glimmer!</em>
---of creative and pedagogical use. While some of the benefits of
geolocation have been immediately seized upon by museums and
historians---think of the partnership between
<a href="http://techcrunch.com/2010/04/22/foursquare-history-
channel/">Foursquare and the History Channel</a>
---very few people have considered using geolocation in a literary
context. Even less attention has been paid to the ways geolocation can
foster critical and creative thinking. So I've been pondering re-
purposing Foursquare and its ilk in ways unintended and unforeseen by
their creators.
</p>
<h2 class="insertright">Let's turn locative media into platforms for
renegotiating space and telling stories</h2>
Following Rob MacDougall's call for
<a href="http://www.robmacdougall.org/index.php/2010/03/playful-
historical-thinking/">playful historical thinking</a>
, I've been imagining what you could call playful geographic
thinking. Let's turn locative media from gimmicky Entertainment coupon
books and glorified historical guidebooks into platforms for
renegotiating space and telling stories. Let's turn them into
something that truly resembles play. And here I'll use
<a id="aptureLink_7JdY40qLl9" href="http://www.amazon.com/gp/product/
0262240459?tag=sampreal-20">Eric Zimmerman and Katie Salen's concept
of play</a>
:
<em>free movement within a more rigid structure.</em>
In this case, that rigid structure comes from the core mechanics of
the different geolocation apps: checking in and tagging specific
places with tips or comments. What's
<em>supposed to happen</em>
is that users check in to bars or restaurants and then post tips on
the best drinks or bargains. But what
<em>can</em>
<em>happen</em>
, given the free movement within this structure, is that users can
define their own places and add tips that range from lewd to absurd.
This is exactly what Dean Terry is doing. Along with his colleagues
and students at the
<a href="http://emac.utdallas.edu/about/">Emerging Media and
Communication</a>
program at the University of Texas at Dallas, Dean has been renaming
spaces and
<a href="http://www.deanterry.com/blog/index.php/location-literacy-
foursquare-in-the-classroom/">making his own places</a>
. Even better, Dean and his group at the MobileLab at UT Dallas are
not only testing the limits of existing geolocation apps, they're
<a href="http://www.placethings.com/">building one</a>
of their own. I'm not designing my own app, but I am playing with
the commercial apps. And again, by
<em>playing</em>
,
<em />
I mean moving freely within a larger, more constrained structure.
For instance, within my dully named campus office building, Robinson
A, I've created my own space,
<a href="http://foursquare.com/venue/1867417">The Office of
Incandescent Light and Industrial Runoff</a>
. Which is pretty much how I think of my office. And I'm mayor
there, thank you very much. Likewise, when I'm home, I often check
into the
<a href="http://foursquare.com/venue/3715999">Treehouse of Sighs</
a>
. I have an actual
<a id="aptureLink_VAjFEaiL4o" href="http://www.flickr.com/photos/
samplereality/4648624179/">treehouse</a>
there, but the Treehouse of Sighs is not that one. The Treehouse of
Sighs exists only in my mind. It's a metaphysical Hotel California.
You can check in any time you like, but you can never be there. Just
as evocative as creating your own space is tagging existing spaces
with virtual graffiti, which you can use to create a counter-factual
history of a place. Anyone who checks into the Starbucks on my campus
can see my advice regarding
<a id="aptureLink_xRqhtx4QvG" href="http://apture.s3.amazonaws.com/
00000128e25ea0127e7784ce007f000000000001.Starbucks.jpg">the fireplace
there</a>
. Also on GMU's campus, I've uncovered Fenwick Library's
<a id="aptureLink_lE3mZDNKNG" href="http://apture.s3.amazonaws.com/
00000128f3c7ad96e2afaee8007f000000000001.Fenwick%20Tacos.jpg">dirty
little secret</a>
. And sometimes I leave surrealist tips in public places, like this
epigram in yet another airport terminal:
- <p style="text-align: center;">
- <a href="http://foursquare.com/item/791648">
<img class="aligncenter size-medium wp-image-1185" style="border:
0pt none;" title="ZGate" src="http://www.samplereality.com/wp-content/
uploads/2010/05/ZGate-450x117.jpg" alt="" width="450" height="117" />
</a>
</p>
All of this play has led me to think about using geolocative media
with my students. Next spring I'm teaching an undergraduate class
called "Textual Media," a vague title that I've taken to describing as
post-print fiction. My initial idea for using Foursquare was to have
students add new venues to the app's database, with the stipulation
that these new venues be Foucauldian "Other Spaces"---parking decks,
overpasses, bus depots, etc.---that stand in sharp contrast to the
officially sanctioned places on Foursquare (coffee shops, restaurants,
bars, etc.). One of the points I'd like to make is that much of our
lives are actually spent in these nether-places that are neither here
nor there. Tracking our movements in these unglamorous but not
unimportant unplaces could be a revelation to my students. It might
actually be one of the best uses of geolocation---to defamiliarize our
daily surroundings. I recently participated in a geolocation session
at
<a href="http://thatcamp.org/about/">THATCamp</a>
that helped me refine some of these ideas. We had about fifteen
historians, librarians, archivists, literary scholars, and other
humanists at the session. We broke off into groups, with the mission
of hacking existing geolocation apps for teaching or learning. I
worked with
<a href="http://twitter.com/cwillifo">Christa Willaford</a>
and
<a href="http://twitter.com/jenksbyjenks">Christina Jenkins</a>
, and as befits brainstorming about space, we left the windowless
room, left the building entirely, and stood out near a small field
(that's not even on the
<a id="aptureLink_1gU3GpXesZ" href="http://maps.google.com/maps?
om=0&iwloc=addr&f=q&ll=38.827748%2C-77.305416&t=k&hl=en&z=18&ie=UTF8">outdated
satellite image</a>
of the place) and came up with the idea we called
<em>Haunts</em>
.
<em>Haunts</em>
is about the secret stories of spaces.
<em>Haunts</em>
is about locative trauma.
<em>Haunts</em>
is about the production of what Foucault calls "heterotopias"---a
single real place in which incompatible counter-sites are layered upon
or juxtaposed against one another. The general idea behind
<em>Haunts</em>
is this: students work in teams, visiting various public places and
tagging them with fragments of either a real life-inspired or
fictional trauma story. Each team will work from an overarching
traumatic narrative that they've created, but because the place-based
tips are limited to text-message-sized bits, the story will emerge
only in glimpses and traces, across a series of spaces.
<h2 class="insertleft">They've stumbled upon a fictional world
haunting the real one.</h2>
Emerge for whom? For the other teams in the class. But also for
random strangers using the apps, who have no idea that they've
stumbled upon a fictional world augmenting the real one. A fictional
world haunting the real one. There are several twists that make
<em>Haunts</em>
more than simple place-based creative writing. For starters, most
fiction doesn't require any kind of breadcrumb trail more complicated
than sequential page numbers. In
<em>Haunts</em>
, however, students will need to create clues to act as what Marc
Ruppel calls
<a href="http://things.wordherders.net/archives/
005458.html">migratory cues</a>
---nudging participants from one locale to the next, from one medium
to the next. These cues might be suggestive references left in a tip,
or perhaps obliquely embedded in a photograph taken at the check-in
point. (Most geolocation apps allow photographs to be associated with
a place; Foursquare is a holdout in this regard, though third-party
services like
<a href="http://picplz.com/">picplz</a>
offer a work-around.) Another twist subverts the tendency of
geolocation apps to reward repeat visits to a single locale. Check in
enough times at your coffee shop with Foursquare and you become
"mayor" of the place.
<em>Haunts</em>
disincentivizes multiple visits. Check in too many times at the same
place and you become a "ghost." No longer among the living, you are
stuck in a single place, barred from leaving tips anywhere else. Like
a ghost, you haunt that space for the rest of the game. It's a fate
players would probably want to avoid, yet players will nonetheless be
compelled to revisit destinations, in order to fill in narrative gaps
as either writers or readers.
<h2 class="insertright">Imagine the same traumatic kernel, being
told again and again, from different points of views.</h2>
The final twist is that
<em>Haunts</em>
does not rely only upon Foursquare. All of the geolocative apps have
the same core functionality. This means that one team can use
Foursquare, while another team uses Gowalla, and yet another
Brightkite. Each team will weave parallel yet diverging stories across
the same series of spaces. Each Haunt hosts a number of haunts. The
narrative and geographic path of a single team's story should alone be
engaging enough to follow, but even more promising is a kind of cross-
pollination between haunts, in which each team builds upon one or two
shared narrative events,
<a id="aptureLink_P3xE4GR05X" href="http://en.wikipedia.org/wiki/
Exquisite%20corpse">exquisite corpse</a>
style. Imagine the same traumatic kernel, being told again and
again, from different points of views. Different narrative
<em>and</em>
geographic points of views. Eventually these multiple paths could be
aggregated onto a master narrative---or more likely, a master
database---so that
<em>Haunts</em>
could be seen (if not experienced) in its totality. There is still
much to figure out with
<em>Haunts</em>
. But I find the project compelling, and even necessary. The
endeavor turns a consumer-based model of mobile computing into an
authorship-based model. It is a uniquely collaborative activity, but
also one that invites individual introspection. It imagines trauma as
both private and public, deeply personal yet situated within shared
semiotic domains. It operates at the intersection between game and
story, between reading and writing, between the real and the virtual.
And it might finally make geolocation worth paying attention to.
</body>
</div>
</div>
</body>
<back />
</text>
</TEI>
Mark Sample
Aug 4, 2010, 12:37:52 PM8/4/10
to anthologize-dev
And, a follow-up. I've just re-exported my project as an epub, and the
images showed up this time. I disabled the shortcodes, so I guess that
was the problem?
Like everyone else, though, PDFs are still not working.
images showed up this time. I disabled the shortcodes, so I guess that
was the problem?
Like everyone else, though, PDFs are still not working.
Reply all
Reply to author
Forward
0 new messages