Search results

Jump to: navigation, search

Page title matches

Page text matches

  • ...ns why on a wiki, so you can hand it off or review at a later date. Follow documentation standards whenever possible. Make readme.txt files so your future self or a ...estion: different environments all on the same repo or keep them separate? Documentation seems focused on beginners or mega experts - need steps 2, 3, 4.
    4 KB (615 words) - 15:01, 14 February 2013
  • = Documentation = == Documentation Interest Group ==
    9 KB (1,431 words) - 14:25, 18 March 2014
  • ...th a focus on sharing, synthesizing, and improving workflow strategies and documentation for software-based approaches to wrangling and providing access to audio an
    26 KB (3,987 words) - 16:57, 6 September 2014
  • ...kground to implement a similar system on their own servers. Implementation documentation and genericized code will also be shared, as available. *Generating a proactive response to the above issues through documentation, issue reporting, and standardized Memoranda of Understanding
    99 KB (15,230 words) - 19:45, 27 May 2016
  • ...//wiki.code4lib.org/index.php/Code4Lib_2014_Conference_Planning_Volunteers|documentation and timelines] for 2014 volunteer committees.
    12 KB (1,920 words) - 12:48, 3 July 2014
  • '''Why:''' Let's share, synthesize, and improve workflow strategies and documentation for wrangling and providing access to audio and video content.
    512 bytes (70 words) - 20:25, 18 March 2014
  • ...4 @phette23] "If we afforded greater status to writing we would get better documentation" @vaurora echoes Tuesday's keynote re devaluing design/UX #c4l14
    51 KB (7,908 words) - 02:01, 6 August 2015
  • Question about new installation: additional resources aside from documentation ...asis is asked to review the documentation and will do sanity checks on the documentation
    13 KB (2,064 words) - 22:07, 3 April 2014
  • ...p://georgetown-university-libraries.github.io/File-Analyzer/ File Analyzer Documentation]
    6 KB (867 words) - 22:30, 14 October 2014
  • = Documentation = == Documentation Interest Group ==
    6 KB (944 words) - 19:31, 14 September 2015
  • We currently have documentation from the Spring 2017 event about how the conference was planned. This docu
    4 KB (666 words) - 15:53, 11 June 2024
  • * Streamline documentation so that it is using best practices and make it user friendly - Lisa Rabey
    18 KB (2,911 words) - 15:15, 1 December 2014
  • <br> 4:30pm - 5pm -- Return to smaller groups, make suggested edits, finalize documentation ...Other Teams on the Subcommittee are working on PBCore outreach, education, documentation, and a new website.
    10 KB (1,509 words) - 00:26, 9 February 2015
  • ...PHP coding standards, testing, and popular PHP tools including PHPDoc for documentation, Composer for smooth installations, and using GitHub and Packagist to manag '''Event page where you can find the latest information and... documentation(!) at [http://wiki.code4lib.org/Code4lib/Write_The_Docs_barcamp]'''
    20 KB (2,997 words) - 22:07, 9 February 2015
  • ...hat combines the FRBR model with CIDOC-CRM, the the object-oriented museum documentation ontology. These modules being developed will allow other researchers to cre ...documentation, and achieving that delicate balance of adequately thorough documentation that doesn’t pose the risk of information avalanche. These processes ofte
    102 KB (15,718 words) - 01:03, 8 November 2014
  • We share common issues surrounding documentation, but we also have unique perspectives and expertise that both sides can sha Remember, like metadata, documentation is a love note to the future.
    3 KB (423 words) - 21:44, 6 February 2015
  • This group will focus on content strategy (in collaboration with the Documentation Committee) and feature implementations to improve the overall user experien
    10 KB (1,435 words) - 13:54, 8 March 2016
  • .../17C5BGX62JmOXtNrVstROwD-bMCMeuokf7tp76L5Htss/edit#heading=h.da50bjnv3ujy| Documentation Group Recommendations]]
    512 bytes (62 words) - 15:19, 2 September 2015
  • * Shared space for documentation - Getting lists of registrants to the workshop leaders ## Say we're working on core space for documentation and they will be notified.
    21 KB (3,253 words) - 16:21, 23 February 2016
  • ...//wiki.code4lib.org/index.php/Code4Lib_2014_Conference_Planning_Volunteers|documentation and timelines] for 2014 volunteer committees.
    15 KB (2,365 words) - 14:29, 19 November 2015

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)