LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  February 2006

CODE4LIB February 2006

Subject:

Re: A code4lib journal proposal

From:

Art Rhyno <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Wed, 22 Feb 2006 23:54:18 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (68 lines)

Wow, lots of great ideas coming in on this. I wonder if fleshing out a
test case would be useful for the class of materials that might have
trouble finding a home in standard publications. For example, Roy's
MODS<->MPEG DIDL shootout. Let's say that Roy put a digitized book on the
code4lib server (maybe one of his own :-), and enough descriptive metadata
to kick things off. Roy then challenges the world to do something
impressive with the results, maybe directly contacting some MODS and DIDL
folks. Those of you who have ever seen Sun's blueprints know that this is
sort of the intent behind their blueprint series, define what seems to be
a agreed-upon problem and let the "best of breed" solutions emerge.

So far, any of this could happen in either the lead-up to a traditional
article (groundwork for "a comparison of MODS and MPEG DIDL") or this kind
of task could be described and offered out on any blog. Now a group like
the folks working on Evergreen do a heck of a lot with MODS and maybe they
decide to take up the banner for it. This leads to the first of a couple
of TPMDPs (Traditional Publishing Model Departure Point):

TPMDP #1: Some sort of step by step capturing mechanism kicks in for
recording how the Evergreen folks approach the task and start to build a
solution. Maybe something as low barrier as a link to their development
blog. This needs to be unobtrusive but is an important layer. It always
looks like divine design after a solution is presented, and Roy's right
that no one ever wants to talk about the wrong turns they make in the path
to a solution, but these are often the most instructive parts.

TPMDP #2: A level of comments is made available for each step of the
process. Peter's noted that comments are really hard to do well, and it
would be great if this could be done in some sort of threaded RSS model.
Jon Udell once wrote about a researcher trying to model network events as
chirping sounds so that someone monitoring hundreds of systems would
instantly notice when something was astray, and be able to instantly grasp
which system it was by the chirp that had changed. So maybe  we need a
comment chirp plugin or something, but the smart money is still on an RSS
comments feed for now. Still, it would be nice to see if comments could be
layered in more elegantly than they usually are.

TPMDP #3: An IRC bridge is made available. I once wrote a hook for IRC to
snag insults from a supybot in cocoon so that a dynamic bit of content
could appear in an S5 slide. I didn't realize until afterwards that
supybots often have incredibly foul mouths and didn't do much with the
results, but I am convinced there is something in the conversational model
in IRC that could do a lot in other spaces. The koha folks do town halls
with IRC, what if an article, or story posting, or whatever this thing is,
shows who is online in code4lib and has some sort of entry point into the
channel with a nick like "reader_wants_to_talk_about_shootout" or
something similar? Or maybe the posting itself is some sort of bot that
can be asked to record parts of discussion? Maybe there could be some sort
of scheduling mechanism, so that someone could say "discuss this solution
with the creators at 10 am on Tuesday" and a log of the discussion could
be kept with the posting. Panizzi, Ed Summers' bot, could probably be
convinced to do something like this.

TPMDP #4: Some sort of presentation tools are always an option. Most
projects have a point where you want to get some feedback before you
proceed further or you suspect a quick reality check might save you grief
later on. Again, this would have to be extremely low barrier, but it would
be invaluable in understanding the information flow and final direction
within a project.

TPMDP #5: A spin-off "traditional" publication would still be possible
downstream. A lot of people only want to find out more about the innards
of a project after seeing its final results, so nothing precludes a more
neatly packaged version at some point in the process and, in fact, this is
where a lot of this would lead. But they key to me is that the messy
"bits" would also be available if there was interest.

art

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager