Code4Lib - User contributions [en]

View architecture and control flow

2009-12-23T16:32:29Z

174.142.104.57: /* Control flow: Points of intervention for a Service */

Part of [[Umlaut Technical Overview]]

door11.txt;10;15

door11.txt;10;15

View architecture and control flow

2009-12-23T16:29:57Z

174.142.104.57: /* Accessing response data */

Part of [[Umlaut Technical Overview]]

door11.txt;10;15

=Control flow: Points of intervention for a Service=

==view_data generation==

When you call ServiceType.view_data, there is actually a somewhat indirected process that happens. This is to give the Service several points of intervention to customize the process of looking at the actual data stored in a ServiceResponse, and turn it into the conventional key/value pairs for view_data dictionary. There are actually probably more points of intervention than needed, some are legacy. The standard easiest thing to do is to let the ServiceResponse itself -be- that hash-like collection of keys and values, since ServiceResponse implements []. But there are several control points where this behavior can be customized.

ServiceType.view_data is actually just a convenience, it really calls service.view_data_from_service_type(self).

Service#view_data_from_service_type(service_type_join) will not normally be overridden by a subclass, although it could be for completely custom handling. But most service adaptor classes inherit the implementation from Service. Service#view_data_from_service_type will first look for a method in the Service adaptor subclass that is named to_[service type name] for the type in question, eg to_fulltext, or to_help. If such a method exists, it will be called, and is expected to return a hash-like object. So this is one place a Service can put custom logic for creating that hash-like object.

But if not found, the default implementation of Service#view_data_from_service_type will instead call Service#response_to_view_data( service_response ) (Note the argument is a ServiceResponse, not a ServiceType). So this is another method an individual service class ''can'' override to provide a custom implementation--in this case, a custom implementation that isn't worried about the particular type, since that information isn't available here.

And if ''that'' isn't provided, there is still an ultimate default action, which is just to return the ServiceResponse itself, which does implement the [] method to be a (duck-typed) hash-like object.

So the point of all this is that an individual Service adaptor doesn't ''need'' to implement any of these methods, it can just store a ServiceResponse with the appropriate keys. For the majority of services, that will be sufficient. But if instead, manipulation at the point of display is convenient, there are various control points where the Service can be asked to create the hash-like view data object on the fly, instead of just using the ServiceResponse.

==url generation==

Clicks on service resposnes are sent through the [http://umlaut.rubyforge.org/api/classes/LinkRouterController.html LinkRouterController], with the id of the ServiceType involved.

Again, the default behavior is for LinkRouterController to simply look at the view data under the key :url, and redirect the user to the value found there. But there are again points of intervention where the individual Service sub-class can customize this behavior--perhaps to only calculate the url at the point of need, not at the point of ServiceResponse generation.

The controller actually calls Service#response_url( service_response ). The individual Service subclass can over-ride this method, which should return a url, to provide custom url generation.

C4L2010planning: wishlist

2009-07-27T21:09:18Z

174.142.104.57: /* Critical things that must work */

Planning for Code4Lib 2010 in Asheville, NC

ert wdefr <a href=" http://www.viddler.com/explore/allinder/ ">free xxx movies</a> wdefsdrgvfb <a href=" http://www.viddler.com/explore/alline/ ">teens</a>

=== Internet ===

* Host local mirror of #code4lib IRC - http://www.tummy.com/Community/Articles/pycon2007-network/
* Rent G3 line for dedicated access for speakers (?)
* Have a contingency aircard so at least speakers can go online (?)
* Hook up to UNCA's Internet connection from the hotel (?)
* bridge server (between outside and local wireless)?
* forwarding server?
* VPN needs to work
* higher ports need to work
* some wired access in room?

=== Technology (non-internet) ===
* Multi-platform computer for presenters--mbklein has Mac/Windows, Ubuntu, Ctrl-key to swich beteween them
* One person suggests a google docs acct to pull presentations together (still need them offline and downloadable)
* Encourage those doing demos to do screencast backups
* Post all info in several places. Emailed info needs to be posted to website

=== Social Activities ===

* Signup sheet for nightly dinner activities
** pick out, say, 5 restaurants, encourage new attendees to connect
** make reservations!
* code4lib revue?
* Big enough hospitality suite/spare room for evening/break activities
* Provide paper maps for participants, info on places to go
* Game night (esp. board games and games like Werewolf)
* Bess' brother-in-law works at a microbrewery. Possible tour?

=== Food & Drink ===
* solicit info about dietary needs
** vegan
** vegetarian
** other needs specified on registration forms

* Requests
** sweet tea
** more beer (code4lib brew for the hospitality suite?)
** more happy hours (possibly a HH before LT?)
** hot breakfast
** candy
** hot soft pretzels & mustard

=== Sponsorship ===

* Potential sponsor and contact list
* Conference scholarships
** Consider scholarship for LIS graduate students, CS undergrads
* Andrew Nagy says: vendors want value, something tangible; can hit them up for more $

=== Choosing speakers ===
* Ask people to write why they nominated keynote speakers
* Do we need more gender diversity of keynote & 20 minute talks? (Is this important to us?)
* Do we want to limit the number of speakers from any one organization?
* Do we want topic-based categories when voting?
** e.g. 5 high-geekiness talks
** e.g. 5 theory talks
** e.g. 5 UI/usability/design-centered talks
* Voting needs 2 criteria: geekiness and vote preference. (In 2008 the sum of these was the total IIRC)
* Reserve 1-2 spots in 20-minute talks for cutting edge speakers
* How do we ensure we get fresh topics?
* Do we combine pre-voting to avoid duplication?

=== Attendees ===
* Who gets to come and how do we decide?
** Some suggestions included: require involvement if not previous attendance
** Some suggestions included: open to previous attendees a day before the main conference
** Some suggestions included: keep it as is
* How do we encourage international participation when we're not in the same town as an international airport?
* Can it be bigger? Do we want it to be? Or do we value the smaller crowd and the more personal, professional connections it affords?
* Who is the conference for?
** library systems
** software engineers
** programmers
** librarians
** designers
** ???
* "This is the only conference for coders"; "Saw no code, so I'm here to give a LT"
* Do-it-yourself crowd

=== Choosing 2011 venue ===
* Announce the process early in the conference so that people can get set up with logins
* Reminder during the last day of voting
* Evaluate internet from 2010: do we need to be at a university for internet conference support?

=== Integration with IRC, twitter stream, and other backstreams ===
* Is IRC the 'backchannel'? OR is the conference the once-yearly 'frontchannel'?
* Consider suggestions from http://pistachioconsulting.com/twitter-presentations/ regarding integration with backchannel.
** e.g. offer speakers help monitoring the channel ('an ombudsman for the audience')
* Advice from dev8 via BenO:
** @davetaz setup projection/feed of the twittered #dev8d tags + @andymcg set up a netvibe channel to follow the tags elsewhere @jschneider Twitter feed screen in bkgd of these photos: http://is.gd/jOwW http://is.gd/jOxd & see @jvvw review of event: http://is.gd/jOxy
* Make it easier for people to find IRC
** "code4lib station" with signup info and help?
* Not everybody multistreams. Would multiple rooms help (reduce volume)? Or...?
* Publish backchannel, e.g. http://reallywow.com/c4l09/logslice/20090225/14:00-14:20

=== Openness & transparency, getting to know people ===
* a code4lib program/conference committee providing support and accumulated wisdom to the organizing committee
* Wordle nametags (popular at dev8. what happens if people don't have blogs/twitterstreams/friendfeed/etc?)

=== Video ===
* Sync the timecode in the video with the IRC logs
* 3rd camera for IRC?
* Highlights reel from previous year at end of 2010 conference?

=== Lightning Talks Do's and Don'ts ===

* Have an MC/cat herder lined up in advance
* Don't have one entity do two LTs back to back
* Ask those who've already spoken to "go last"
** e.g. only present if there's time)-- "share the air"
** Do we need a policy or clarity on expectations? (e.g. no repeats)
* Create a LT do's and dont's page in the conference webspace
** link to existing LT advice
* 2 projectors, minimum. 3 if possible (3rd to display backchannels)
* make transitions to LT during coffeebreak or other downtime

=== Advice for speakers ===
* Font up
* Speak up
* Introduce yourself

=== Breakouts ===
* Consider setting 2-3 breakouts in advance
* Have 1-2 'unbreakout' sessions
* 11 is too many, IMO
* Trouble when different people are at different levels with a software discussed
** how to know in advance?
** Fedora access controls

=== List of Interesting things in Asheville, for future reference ===
''see also [http://maps.google.com/maps/ms?ie=UTF&msa=0&msid=107701218656997471821.00046117cc493635eebc1 Google Map], [http://digital.library.appstate.edu/code4lib2010.html proposal]''
* The Chocolate Fetish
* Woolworth Gallery (collaborative arts and crafts sale space in an old Woolworth's, with intact, functional lunch bar and a Swedish furniture shop in the basement)

[[Category: Code4Lib2010]]