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  April 2015

CODE4LIB April 2015

Subject:

Re: Managing internal documentation

From:

Jenny Jing <[log in to unmask]>

Reply-To:

Code for Libraries <[log in to unmask]>

Date:

Fri, 10 Apr 2015 14:00:17 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (138 lines)

I am interested in the demo too. A webinar would be good.

Thanks.

Jenny

Jenny Jing
Information Systems Librarian
Discovery Systems
Queen’s University Library
Kingston ON, K7L 5C4
[log in to unmask]
613-533-6000 x 75302


-----Original Message-----
From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of Doreen Herold
Sent: April-09-15 4:12 PM
To: [log in to unmask]
Subject: Re: [CODE4LIB] Managing internal documentation

Hi Gary,

I'd be interested in a demo of it.  And I think I have a couple of staff that would also be inspired by your model.  I wonder if that could be a good webinar to provide?  Does CODE4LIB ever host such events?

Doreen

On Thu, Apr 9, 2015 at 3:32 PM, Gary Thompson <[log in to unmask]> wrote:

> The Digital Initiatives and IT (DIIT) department at the UCLA Library 
> transformed the way we work over the last 6 years after implementing 
> Confluence.  We've got two teams of developers (3 focused on the 
> Digital Library, 6 on everything else), a team of 4 Digital Library 
> project managers, and an operations staff of 18,; we all rely on the 
> wiki. It has proved essential after a couple of recent staff departures.
>
> Confluence supports the basic wiki model of linked and tagged 
> documents, but allows people who like to hierarchy to organize content 
> in a tree. We make heavy use of the /metadata-list/ macro to format 
> the structure, and generate views or lists of content (e.g., lists of 
> serves, vendors, projects, etc) controlled by labels (i.e., tags) 
> using the /metadata-report/ macro. We use tagging to indicate project 
> status (definition, planning, execution), type of content 
> (server-logs, specifications), or technology (voyager, drupal).
>
> We're running our own service; Atlassian on-demand was not an option 
> when we started. If we weren't using local LDAP authentication, we 
> might consider migrating to a hosted service. I suspect that we will 
> eventually move to hosted Confluence, but it's not currently a priority.
>
> The wiki became so integral to the way we work that we decided to 
> replace our old ticketing system (FootPrints) with Jira to take 
> advantage of the integration.
>
> Our DIIT implementation was so successful that other Library 
> departments and locations are starting to use it, some in very 
> sophisticated ways. For example, a cross-department digitization team 
> uses it to accept requests, prioritize the work, and track progress.
>
> I would be happy to show anyone who is interested how we use it. A 
> colleague and I considered writing a Code4Lib Journal article on our 
> project management methodology, but that article didn't get focus. 
> This question -- and my answer -- may motivate me to get it done.
>
> Cheers,
>
> /-- -- Gary Thompson
> -- Head of Software Development & Project Management
> -- Digital Initiatives & Information Technology
> -- UCLA Library
> -- 390 Powell
> -- voice: 310.206.5652
> --/
>
>
>
> On 4/9/2015 11:40 AM, Scott Williams wrote:
>
>> Apologizes for cross-posting
>> ###
>>
>> Hi all --
>>
>> We are investigating several software platforms for creating and 
>> managing internal documentation and wanted to see what experiences 
>> others have had with these packages.
>>
>> We are evaluating
>> * MadCap Flare
>> * Adobe RoboHelp
>> * Confluence
>>
>> Our initial goals for these systems are to replace or augment our 
>> existing documentation strategy, which is a mix of private Google 
>> sites, SharePoint and Word docs. We are starting with our IT 
>> department but hope to include other user groups over time.
>>
>> Things we like:
>> * SVN control with MapCap and RoboHelp. However, we have run into 
>> problems with both of their implementations
>> * Write once publish everywhere functionality
>> * HTML5 support with WebHelp Plus
>> * Context aware searching
>> * Easily export and share documentation externally (PDF)
>> * Consistent theming and styling across all the documentation
>> * User/group security management for hiding more sysadmin 
>> documentation
>>
>> Things we don't like
>> * Windows only (MadCap and RoboHelp)
>> * WebHelp requires IIS (?)
>> * Limited functionality with the hosted version of Confluence
>>
>>
>> What are people using to manage their internal 
>> systems/architecture/application documentation? Are there other 
>> products we should be considering?
>>
>> Many thanks,
>> Scott
>>
>> ----
>> Scott Williams
>> Data & Database Administrator
>> Yale University Art Gallery
>>
>


--
Doreen Herold
Manager, Library Technical Services
Lehigh University
Library & Technology Services
30 Library Drive - Bethlehem, PA - 18015
610.758.3040 - [log in to unmask]
http://library.lehigh.edu
Library Technical Services Wiki <https://confluence.cc.lehigh.edu/x/SQAR>

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

January 2020
December 2019
November 2019
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