I had to document the servers i use and i don't know what to use to hold the data. Could you sugest the best way to keep the server documentation? Do i create a data base that holds the harware and software documentation, or do i use wiki pages or SVN? Or if ther is a tool that holds the documentation could you please provide the link.
I am looking for a system to prepare internal technical documents that has the following basic features:
- source files should be human-readable text files, so they play well with revision control
- supports basic formatting (e.g. images, tables, boldface, etc.)
- works with both English and Chinese characters
- outputs to PDF
I could, for example, users to write HTML pages and print the pages to PDF, but this seems complicated and error-prone, and HTML is only barely "human-readable". LaTeX is also very complicated, and it has a lot of dependencies that might make it hard to process documents that are several years old.
Does anyone have any better suggestions?
I have been tasked with migrating a Laserfiche repository to Alfresco (Records Management module).
The Laserfiche implementation is hugely underutilized - They've scanned in about 60Gb in the last 9 years, and simply do infrequent lookups based on the full-text OCR. Only two meta-data fields are tracked: Account Type, and Client Name. That's it - no other features are utilized.
I have Googled the heck out of "migration tools", and found nothing that reads from Laserfiche. I find that Laserfiche does not support any standard export format or APIs such as CMIS or JCR.
Certainly, there are firms that do nothing more than migrate documents, but for enterprise / fortune-1000 clients; this is a small workgroup. I'm hoping for a software migration tool, or an import path available in Alfresco.
We are looking for ways in which to further enhance our documentation and our ability to allow easy access to the information as well as editing the information. With these ideas in mind, we created an internal wiki based upon the MediaWiki platform for our Tier 1 (Help Desk). This has been a huge success for the Help Desk and they use this extensively for their daily operations. Now, we are looking at ways in which to document things for our Tier 2 (Systems Administrators). We need to have the information for Tier 2 separate from the information for Tier 1 due to the sensitivity of the information and the fact that it will contain steps for how we build our servers, etc.
I am looking for ideas and suggestions in relation to how we can accomplish the following aims:
- Centralized documentation based upon the MediaWiki platform
- Separated content between Tier 1 and Tier 2
- We like the look and feel that we have for Tier 1 and that could be used for Tier 2
- Can this be ran on the same server if we were to run two different installations of MediaWiki? Is this even a good idea to run multiple installations of MediaWiki on the same machine?
- Support for FQDN and SSL certificates for each documentation installation
- Is there a way to slice or keep separate part of the Tier 1 MediaWiki installation based upon user or group membership?
Thank you in advance and I look forward to your ideas and suggestions.
My team has a need to publish documentation internally. At the moment, it's spread all over the place and this means we often have to search everywhere to find something.
We'd like to publish everything in one place. The main thing that stops us is access control - the wikis in place don't belong to us and we can't do it.
What is the best tool for publishing docs, ideally fitting these requirements:
- web front end - readers access docs using browser
- single place to put docs
- access control by individual doc or by sets of docs (folders, branch of 'site', ...)
- if you don't have access to a doc, you don't see the link to that page/doc/folder.
- either built-in editor or something my users are familiar with (e.g. Word)
- built-in version control would be nice
Also, can you think of other criteria I should've specified?