1 / 27

Internet Publication of Geneva Justice Decisions

Internet Publication of Geneva Justice Decisions. A case study laurent.dami@justice.ge.ch. Agenda. context presentation justice.ge.ch/jurisprudence : short tour technical information some lessons about Perl in the enterprise. Context presentation. A justice decision.

sawyer
Download Presentation

Internet Publication of Geneva Justice Decisions

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Internet Publication of Geneva Justice Decisions A case study laurent.dami@justice.ge.ch

  2. LD, PJ-GE, july 2006 Agenda • context presentation • justice.ge.ch/jurisprudence : short tour • technical information • some lessons aboutPerl in the enterprise

  3. Context presentation

  4. LD, PJ-GE, july 2006 A justice decision • is a structured document • header / facts / law / conclusion • may have a 2nd, anonymous version • has a unique identifier (e.g. ACJC/123/2005) • has a context (metadata) • date / names / topic / keywords / summary / etc. • is archived into a collection • minutes du TA / CJC / TPI / etc.

  5. LD, PJ-GE, july 2006 Lifecycle clerk judge college receivecase investigate deliberate write project send finalize supplycontext archive

  6. LD, PJ-GE, july 2006 Electronic archive : requirements • store document • multiple formats • fulltext indexing • store metadata • structured fields • quick search (unstructured!) • intelligent presentation • automatic hyperlinks • offline / CDROM copies per collection

  7. LD, PJ-GE, july 2006 Some figures • Intranet : 20 – 30 collections • Internet : only 2 collections for the moment • 500 to 50000 decisions per collection • for about 10 years of data • 2 – 50 pages per document

  8. LD, PJ-GE, july 2006

  9. LD, PJ-GE, july 2006

  10. Short tour http://justice.geneve.ch/jurisprudence

  11. LD, PJ-GE, july 2006

  12. LD, PJ-GE, july 2006

  13. LD, PJ-GE, july 2006 metadata search fulltext search

  14. LD, PJ-GE, july 2006

  15. LD, PJ-GE, july 2006 Qualité pour agir

  16. LD, PJ-GE, july 2006

  17. Technical information

  18. LD, PJ-GE, july 2006 Which kind of solution ? • Electronic Doc. Management System • not well suited for multiple disjoint collections • approval / workflow not relevant • Database • many fields : too much structure for easy searches (SQL not well suited) see CPAN SQL::KeywordSearch !

  19. LD, PJ-GE, july 2006 Storage of a collection config.txt words.bdb metadata.txt file.{doc,html,pdf} file.{doc,html,pdf} w2docs.bdb file.{doc,html,pdf} positions.bdb fulltext indexin BerkeleyDB format flat file documents

  20. LD, PJ-GE, july 2006 Phases for a search Parse request Metadata search Fulltext search Merge results Sort & slice Contextual excerpts Display

  21. LD, PJ-GE, july 2006 Main Modules ModPerl::Registry CGI AppConfig File::Tabular::Web Search::QueryParser not (yet) on CPAN Search::Indexer File::Tabular BerkeleyDB Template toolkit

  22. Some lessons aboutPerl in the Enterprise

  23. LD, PJ-GE, july 2006 Context : Geneva Justice • finished phase 1 (collaborative software, document management) • ongoing phase 2 : rewrite the old COBOL application for case management using • mod_perl • Catalyst • DHTML + Ajax • smooth transition • COBOL and Perl must live side-by-side for several years

  24. LD, PJ-GE, july 2006 Acceptance • strong internal resistance • bad image : low-tech, hacking, scripting • Perl5 features not known • objects, namespaces, closures, etc. • not "standard" (i.e. not Java) • fear not to be able to maintain and industrialize • cheap means "not serious" • but: Perl productivity wins !

  25. LD, PJ-GE, july 2006 Perl Job Market • found more people than expected. But • all coming from US / UK • used Perl several years ago,now on Java / PHP • missing other skills (modeling, communication, project management) • apparently not enough "average profiles" • few top stars • many low-level geeks • Perl not taught at school !

  26. LD, PJ-GE, july 2006 Industrialization • Release management : granularity mismatch • production guys want • big tarballs • few updates • strict release process • development guys want • small and frequent updates using cpan / cpanplus / minicpan • fast release process, short feedback loop

  27. LD, PJ-GE, july 2006 Development • TMTOWTDI • yet developers need guidance • many thanks to Damian Conway ! • IDE • CPAN : how to manage proliferation • cpanratings not exhaustive/reliable enough • which modules were rated by <some_guru> ? • inverse dependencies

More Related