[open-archaeology] Bibliography and Best Practices
Jessica Ogden
jessogdogg at googlemail.com
Wed Dec 8 12:56:04 UTC 2010
Dear all,
I second the motion for a bibliography on the wiki. Having had to recently
gather my thoughts on the subject, it would have been nice to have a
reference list to get me started..!
Cheers,
Jess
Jessica Ogden
Digital Specialist
L - P: Archaeology, Ltd.
London, UK
On Wed, Dec 8, 2010 at 12:46 PM, Matthew Law <matt at kidvinyl.co.uk> wrote:
> Dear all,
>
> Seeing Stefano's comment from earlier today in the 'Best practices'
>
> > Publishing your data on the
> > Web makes it easier for researchers to find and cite it [there
> > are reliable figures about this kind of benefits from open
> > access]
>
> and recalling my own research into this for a paper I presented at the ICAZ
> (International Council for Archaeo-Zoology) conference in Paris in August
> leads me to wonder if it might be an idea to maintain a bibliography on the
> group wiki (I couldn't see one there, perhaps I missed it though?) both of
> group members' (relevant) publications (with links of course because all our
> publications are gold or green OA where permitted, right?), and a wider
> range of pertinent publications about open data.
>
> What do you think?
>
> Matt
>
> Matt Law
> PhD Student, Archaeology
>
> PEACE - Postgraduate Environmental Archaeology and Community Engagement
> http://peacecardiff.tumblr.com
>
> School of History, Archaeology and Religion
> Cardiff University
> Humanities Building
> Colum Drive
> Cardiff
> CF10 3EU
>
> http://www.cardiff.ac.uk/share/contactsandpeople/postgraduatestudents/law-matt-overview_new.html
>
> LawMJ at cardiff.ac.uk
> ----- original message --------
>
> Subject: open-archaeology Digest, Vol 12, Issue 2
> Sent: Wed, 08 Dec 2010
> From: open-archaeology-request at lists.okfn.org
>
> > Send open-archaeology mailing list submissions to
> > open-archaeology at lists.okfn.org
> >
> > To subscribe or unsubscribe via the World Wide Web, visit
> > http://lists.okfn.org/mailman/listinfo/open-archaeology
> > or, via email, send a message with subject or body 'help' to
> > open-archaeology-request at lists.okfn.org
> >
> > You can reach the person managing the list at
> > open-archaeology-owner at lists.okfn.org
> >
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of open-archaeology digest..."
> >
> >
> > Today's Topics:
> >
> > 1. Re: BoneCommons open material (Eric C. Kansa)
> > 2. best practices (Stefano Costa)
> > 3. Re: BoneCommons open material (Stefano Costa)
> > 4. Re: best practices (Anthony Beck)
> >
> >
> > ----------------------------------------------------------------------
> >
> > Message: 1
> > Date: Tue, 07 Dec 2010 08:48:58 -0800
> > From: "Eric C. Kansa" <ekansa at ischool.berkeley.edu>
> > Subject: Re: [open-archaeology] BoneCommons open material
> > To: open-archaeology at lists.okfn.org
> > Message-ID: <4CFE657A.30105 at ischool.berkeley.edu>
> > Content-Type: text/plain; charset=UTF-8; format=flowed
> >
> > Hi All,
> >
> > Exporting Dublin Core metadata should be easy. As Stefano noted, we're
> > using Omeka which publishes machine-readable data by default:
> >
> > http://omeka.org/codex/Response_Formats
> >
> > As far as the content goes, it's mainly a grab-bag of varia published by
> > different members of the ZooArch community. There are paper offprints,
> > conference presentations, images, and newsletters. Wide dissemination is
> > useful, but the material isn't necessarily easy to remix (hence calling
> > this "sorta" open). Nevertheless, I think BoneCommons has helped get
> > researchers comfortable with CC licenses (esp. the more open variants)
> > and the open Web in general. Because it's sponsored by ICAZ, it has a
> > professional society behind CC licensing and open sharing too, so that
> > makes it feel more acceptable.
> >
> > Thanks for circulating this Stefano!
> > -Eric
> >
> >
> >
> >
> > On 12/7/2010 3:07 AM, Stefano Costa wrote:
> > > Hi all,
> > > a few weeks ago Eric Kansa pointed me to an interesting collection of
> > > open material from the BoneCommons initiative:
> > >
> > >> I wanted to let you know that BoneCommons has some more
> > >> open (sorta) material here:
> > >>
> > >>
> >
> http://www.alexandriaarchive.org/bonecommons/items/browse/tag/presentation+s
> > hared
> > >>
> > >> Unfortunately, most of the files aren't in nice open formats, PDF and
> > >> powerpoint dominate. But at least they can all be used by open source
> > >> software, and most content is under a CC-BY-SA license.
> > > I've now added a CKAN package for this collection (it would be great if
> > > we could mass-import from Omeka by means of RDF or DC metadata):
> > >
> > > http://ckan.net/package/bonecommons
> > >
> > > Improve it at as you like.
> > >
> > > Ciao
> > > steko
> > >
> >
> >
> >
> >
> > ------------------------------
> >
> > Message: 2
> > Date: Wed, 08 Dec 2010 10:57:09 +0100
> > From: Stefano Costa <stefano.costa at okfn.org>
> > Subject: [open-archaeology] best practices
> > To: Open Data in Archaeology Working Group
> > <open-archaeology at lists.okfn.org>
> > Message-ID: <1291802229.1892.52.camel at ganymede>
> > Content-Type: text/plain; charset="utf-8"
> >
> > Hello,
> > a few days ago I started to sketch some very simple best practices for
> > publishing open archaeological data. I'd like to share those here and
> > possibly start a collaboratively-edited set of best practices.
> >
> > A. Explicit is better than implicit [*]. Describe your data and
> > models. You can do that using a graphic or SQL schema, and
> > explaining the meaning and rationale of your database fields.
> > B. Use open formats. If unsure, keep it simple. CSV is better than
> > XLS. Anything is better than DOC or PDF.
> > C. Attach an open license to your work. Open Data Commons created 2
> > good licenses for open data.
> > D. Are you using proprietary software? Try to avoid proprietary
> > formats like DWG or MDB, and opt for simpler, transparent
> > formats like SQL.
> > E. Are you afraid of losing your work? Publishing your data on the
> > Web makes it easier for researchers to find and cite it [there
> > are reliable figures about this kind of benefits from open
> > access]
> > F. Are you afraid of posing cultural heritage at risk? Start with
> > unencumbered data, like analyses of artifacts, records of safely
> > stored items, fuzzy location coordinates.
> >
> > This short list might look simplistic in that it doesn't take into
> > account some of the problems that might arise in opening archaeological
> > data, but it could be a good start. I'm open to discussion and I would
> > be happy if we could publish a first public draft before the end of this
> > year.
> >
> > Ciao
> > Stefano
> >
> > [*] Python fans will spot the "import this" citation ;)
> >
> > --
> > Stefano Costa
> > Coordinator, Working Group on Open Data in Archaeology
> > http://wiki.okfn.org/wg/archaeology
> > The Open Knowledge Foundation
> > http://www.okfn.org ? http://opendefinition.org/
> > -------------- next part --------------
> > A non-text attachment was scrubbed...
> > Name: not available
> > Type: application/pgp-signature
> > Size: 198 bytes
> > Desc: This is a digitally signed message part
> > URL:
> > <
> http://lists.okfn.org/pipermail/open-archaeology/attachments/20101208/2ea1d
> > 032/attachment-0001.pgp>
> >
> > ------------------------------
> >
> > Message: 3
> > Date: Wed, 08 Dec 2010 11:18:18 +0100
> > From: Stefano Costa <stefano.costa at okfn.org>
> > Subject: Re: [open-archaeology] BoneCommons open material
> > To: open-archaeology at lists.okfn.org
> > Message-ID: <1291803498.1892.62.camel at ganymede>
> > Content-Type: text/plain; charset="utf-8"
> >
> > Il giorno mar, 07/12/2010 alle 08.48 -0800, Eric C. Kansa ha scritto:
> > >
> > > Exporting Dublin Core metadata should be easy. As Stefano noted, we're
> > > using Omeka which publishes machine-readable data by default:
> > >
> > > http://omeka.org/codex/Response_Formats
> >
> > Eric,
> > it's a lot more than I expected! Two minor questions:
> > * are you exposing machine-readable formats in the document
> > source? I can only find <link rel="alternate to the RSS2 feed
> > * the Omeka XML has info about pagination, but is there a way to
> > go through many pages of content without parsing XML of the
> > first page?
> >
> > > Nevertheless, I think BoneCommons has helped get researchers
> > > comfortable with CC licenses (esp. the more open variants) and the
> > > open Web in general. Because it's sponsored by ICAZ, it has a
> > > professional society behind CC licensing and open sharing too, so that
> > > makes it feel more acceptable.
> >
> > We need more professional societies adopting the same policies. I think
> > there could be some progress in this direction with the "ethics
> > statement" that Ant Beck has been discussing with a few organizations in
> > the UK.
> >
> > Ciao
> > Stefano
> >
> > --
> > Stefano Costa
> > Coordinator, Working Group on Open Data in Archaeology
> > http://wiki.okfn.org/wg/archaeology
> > The Open Knowledge Foundation
> > http://www.okfn.org ? http://opendefinition.org/
> > -------------- next part --------------
> > A non-text attachment was scrubbed...
> > Name: not available
> > Type: application/pgp-signature
> > Size: 198 bytes
> > Desc: This is a digitally signed message part
> > URL:
> > <
> http://lists.okfn.org/pipermail/open-archaeology/attachments/20101208/889b4
> > 6c5/attachment-0001.pgp>
> >
> > ------------------------------
> >
> > Message: 4
> > Date: Wed, 8 Dec 2010 11:30:29 +0000
> > From: Anthony Beck <A.R.Beck at leeds.ac.uk>
> > Subject: Re: [open-archaeology] best practices
> > To: Stefano Costa <stefano.costa at okfn.org>, Open Data in Archaeology
> > Working Group <open-archaeology at lists.okfn.org>
> > Message-ID:
> > <328C1883CC6BC643B02B589D66B5A16CBA2F915887 at HERMES8.ds.leeds.ac.uk
> >
> > Content-Type: text/plain; charset="iso-8859-1"
> >
> > Hi Steko,
> >
> > Agree with this.
> >
> > in reference to points:
> >
> > E: Provide examples of how to reference Open Data and to reinforce that
> > dataset citation is also a demonstration of impact which will also help
> > career progression (i.e. careers are no longer solely built around
> journal
> > articles)
> >
> > F: Still in a holding pattern on the "ethics" statement. The ball is
> still
> > rolling but slowly. A community statement that shifts the ethical onus
> from
> > the individual to the community (through agreed best practice) should
> remove
> > one more barrier to submission.
> >
> > A
> >
> >
> > ---------------------------------------
> > Anthony Beck
> > Research Fellow
> > DART Project
> > School of Computing
> > University of Leeds
> >
> > Follow me on Twitter: AntArch
> > Follow DART on Twitter: DART_Project
> >
> > The DART project website is continually updated
> www.comp.leeds.ac.uk/dart
> > ________________________________________
> > From: open-archaeology-bounces at lists.okfn.org
> > [open-archaeology-bounces at lists.okfn.org] On Behalf Of Stefano Costa
> > [stefano.costa at okfn.org]
> > Sent: 08 December 2010 09:57
> > To: Open Data in Archaeology Working Group
> > Subject: [open-archaeology] best practices
> >
> > Hello,
> > a few days ago I started to sketch some very simple best practices for
> > publishing open archaeological data. I'd like to share those here and
> > possibly start a collaboratively-edited set of best practices.
> >
> > A. Explicit is better than implicit [*]. Describe your data and
> > models. You can do that using a graphic or SQL schema, and
> > explaining the meaning and rationale of your database fields.
> > B. Use open formats. If unsure, keep it simple. CSV is better than
> > XLS. Anything is better than DOC or PDF.
> > C. Attach an open license to your work. Open Data Commons created 2
> > good licenses for open data.
> > D. Are you using proprietary software? Try to avoid proprietary
> > formats like DWG or MDB, and opt for simpler, transparent
> > formats like SQL.
> > E. Are you afraid of losing your work? Publishing your data on the
> > Web makes it easier for researchers to find and cite it [there
> > are reliable figures about this kind of benefits from open
> > access]
> > F. Are you afraid of posing cultural heritage at risk? Start with
> > unencumbered data, like analyses of artifacts, records of safely
> > stored items, fuzzy location coordinates.
> >
> > This short list might look simplistic in that it doesn't take into
> > account some of the problems that might arise in opening archaeological
> > data, but it could be a good start. I'm open to discussion and I would
> > be happy if we could publish a first public draft before the end of this
> > year.
> >
> > Ciao
> > Stefano
> >
> > [*] Python fans will spot the "import this" citation ;)
> >
> > --
> > Stefano Costa
> > Coordinator, Working Group on Open Data in Archaeology
> > http://wiki.okfn.org/wg/archaeology
> > The Open Knowledge Foundation
> > http://www.okfn.org ? http://opendefinition.org/
> >
> >
> > ------------------------------
> >
> > _______________________________________________
> > open-archaeology mailing list
> > open-archaeology at lists.okfn.org
> > http://lists.okfn.org/mailman/listinfo/open-archaeology
> >
> >
> > End of open-archaeology Digest, Vol 12, Issue 2
> > ***********************************************
> >
>
> --- original message end ----
>
>
> _______________________________________________
> open-archaeology mailing list
> open-archaeology at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/open-archaeology
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/open-archaeology/attachments/20101208/79c8fe9e/attachment-0001.html>
More information about the open-archaeology
mailing list