[brlug-general] open source document management?
Hmm... this looks simple enough that it might work: http://www.opendocman.com/ No bloat, dead simple interface. -Shannon
[brlug-general] open source document management?
On Nov 21, 2007 9:35 AM, Dustin Puryear wrote: > I was just thinking about posting a similar note. Seems to me if a true > document management system is overkill then a wiki would work great. > Just create a hierarchy of pages and each leaf page would be dedicated > to a document (attached) and metadata (wiki notes). > > main > -dept1 > -proj1 >-doc1 >-doc2 >-doc3 > > Here at Puryear IT we actually use a mixture of systems. Not ideal, but > it's working so far. Basically, for project management we use a > web-based system which allows us to attach versioned documents to a > project and/or project tasks. For documents not specific to a project we > either dump then on network storage or we write them directly as text in > an internal wiki. > Dustin, Over here the main barrier to adoption (and refinement) is simply, use. Too Busy... to do...this...got..to..code.can't..use this... don't know howdon't have time figure it out.gotta code... gotta get my fix inI didn't come up with this documentation system it sucksit gets in the way of my processcan't find anything.I'll just stub it out and put in the specifics later (never) .. are the developer impressions I get in general when I've seen developers forced onto a rigid system. Most developers have a split personality when it comes to using the keyboard : they like to churn out code and get things done; they hate to commit to anything specifically NOT code. (The same goes for completion dates, estimates, requirement analysis, etc) I find this quite amusing since I play both sides of the development cycle. :-) Developers, as a class, are die-hard perfectionists have a magnificent work-ethic for code specific work; they love to be working hard. They live for this stuff. This slanted effort feeds the "excuse" for the more drudge work avoidance. That most developers have an overwhelming workload, gives validity to this "excuse".In the end, stuff either gets done or not. Whether it gets done timely or results in a useful solution is another issue entirely. A documentation system that only causes pain (real or perceived) will not be usefull. Ease of use...hey man this really works for mewow, cool! neat trickI can do this are the impressions my ideal documentation system should make. Perhaps I should be referring to "Document Generation & Maintenance" as "refactoring the project's English codebase. Any guidance on what works and the context use is/has been appreciated.Lots of good stuff to think about. Thanks fellow luggers.
[brlug-general] open source document management?
Openfiler is a linux distro aimed at being a SAN/NAS server. I'm running it here as an iSCSI target for my virtual machine servers, and it's working very well. Early this week I had some issues with it, and decided to pay the maintainers for help with it. They ended up logging into my system, fixing the problems, and then sent me detailed messages about what they fixed. Good experience all around Karthik Poobalasubramanian wrote: > Shannon, > I kind of lost track of this thread and too lazy to see if somebody > mentioned this before. > > Anyway came across this on /. but may work for our purpose. > > http://www.openfiler.com/about/ > > > > > Karthik > > > ___ > General mailing list > General at brlug.net > http://mail.brlug.net/mailman/listinfo/general_brlug.net >
[brlug-general] open source document management?
A good pilot for a wiki in your environment may be to use the wiki for scratch work and more note-oriented information, e.g., howto's, common tasks. We rely heavily on ours for that. If people take to it, and they will, then you can start pushing it harder for places where it fits. After reading this thread I wonder if we could plug our wiki into our project management solution.. The wiki is great for notes and general comments but, for us, not so good for really good project management. You can plot out a timeline in a wiki, sure, but you have to do a lot of the grunt work yourself to watch what's going on if you do it that way. -- Puryear Information Technology, LLC Baton Rouge, LA * 225-706-8414 http://www.puryear-it.com Author, "Best Practices for Managing Linux and UNIX Servers" http://www.puryear-it.com/pubs/linux-unix-best-practices Identity Management, LDAP, and Linux Integration CM Banker wrote: > On Nov 20, 2007 6:38 PM, Scott Harney wrote: > >> You know, you would think that, but in practical use, we really haven't >> found that to be true. I suppose if your organization has strict >> documentation format requirements, this wouldn't be a good fit. And you >> could break up a twiki into multiple "webs" each with its own groups of >> authors/editors who control the content underneath. > > My organization is in the formative stage of document management. > We're in two groups : one that has an effective, predictable but > inefficient means of documentation ( document templates & directory > structure for projects) and the other that is becoming more formal in > its process due to project growth and team growth. (Very small shop > growing fast in work and talent) > > The first group's documentation style/need/contents reflect a > predictable process by capturing named rigid artifacts and > correspondences. They do the same thing-ish over and over. On the > other hand, the formative group is a development group trying to : > insure all developers understand what they're working on (background & > constantly shifting requirements), keep track of projects (project > management), manage defects, and feed the process that generates user > documentation. Our biggest challenge is a huge critical mass of > domain & system knowledge is required just to start doing any > practical development. > > The systems we deal with are complex (but not that complicated), and > the nature of the information is difficult to chain in an exposed > predictable manner. (I feel tired just thinking about it).(Now > that I think of it, a wiki, with clonable sections and some initial > organization is looking good for this stuff). Maintaining proper > currency with the documents and schedules is a bear. > >> We've been using twiki (http://twiki.org) on our team for about two >> years now. Our team consists of unix, mainframe and storage >> administrators and engineers. We have a multitude of projects as well >> as daily operational responsibilities to keep track of and while people >> in the group have their particular points of focus, we all need to be >> aware of how to pick up some of the other responsibilities. >> >> We use numerous add-ons, some of which shipped with it, and some of >> which we added after the fact > > I looked over the url - this impresses me as a fairly mature > implementation of a wiki.Even a doxy plugin. > > Of course, making developers churn out useful, appropriately detailed > documents is like pulling teeth from a mule, and this, of course, is > easier than making them use a formal system. :-) > > Scott, Do you mind if I contact you off list for a couple of other questions? > > Thanks, > > -CMB > > ___ > General mailing list > General at brlug.net > http://mail.brlug.net/mailman/listinfo/general_brlug.net
[brlug-general] open source document management?
I was just thinking about posting a similar note. Seems to me if a true document management system is overkill then a wiki would work great. Just create a hierarchy of pages and each leaf page would be dedicated to a document (attached) and metadata (wiki notes). main -dept1 -proj1 -doc1 -doc2 -doc3 Here at Puryear IT we actually use a mixture of systems. Not ideal, but it's working so far. Basically, for project management we use a web-based system which allows us to attach versioned documents to a project and/or project tasks. For documents not specific to a project we either dump then on network storage or we write them directly as text in an internal wiki. Like I said, not ideal but damn it seems to work. I have a ticket assigned internally I think for someone to find a Google appliance-like open source package so we can find documents and notes across all of our systems more easily. One day.. ;) -- Puryear Information Technology, LLC Baton Rouge, LA * 225-706-8414 http://www.puryear-it.com Author, "Best Practices for Managing Linux and UNIX Servers" http://www.puryear-it.com/pubs/linux-unix-best-practices Identity Management, LDAP, and Linux Integration Scott Harney wrote: > Shannon Roddy wrote: >> I'm debating on punting and just setting up a table updated by hand. >> It would be *really* nice to find something that would allow other >> users to post docs and metadata about the doc... I guess I just need >> to find time to evaluate the ones google brings up. not enough hours >> in the day >> > I'm not exactly sure what you're usage scenario is, but if it's just > internal documentation, we use TWiki in my shop. most people write > straight into the Wiki which does automatic version control. We hooked > authentication into LDAP, of course. some people do upload non-html > attachment, eg Word docs, pdf, etc. > > It's simple, but it works. > >> On Nov 20, 2007 3:08 PM, Tim Fournet wrote: >> >>> We're using Plone right now as kind of a documentation repository. I >>> like it and wanted to use it as a DMS, but I didn't find it that handy >>> for uploaded files >>> >>> >>> CM Banker wrote: >>> Plone is a CMS but has most of the elements of a DMS with the exception of integrated scanning & tagging (ala Paragon Filenet). It is multi-platform. On Nov 20, 2007 9:00 AM, Tim Fournet wrote: > There are a couple that I know of that you may want to consider: > knowledgeTree and Alfresco. Alfresco is more of a CMS, but is built to > work well for document management > I haven't chosen one for myself yet, but it is on my to-to list. > > > > > Shannon Roddy wrote: > > >> I can't remember if this has come up before, but anyone know of a good >> open source document management package out there? Hopefully with the >> ability to specify different access controls per file. Yes, this >> would be running on Linux/Apache. ;-) >> >> While I am at it... any suggestions on web based calendaring? >> >> -Shannon >> >> ___ >> General mailing list >> General at brlug.net >> http://mail.brlug.net/mailman/listinfo/general_brlug.net >> >> >> > ___ > General mailing list > General at brlug.net > http://mail.brlug.net/mailman/listinfo/general_brlug.net > > > ___ General mailing list General at brlug.net http://mail.brlug.net/mailman/listinfo/general_brlug.net >>> ___ >>> General mailing list >>> General at brlug.net >>> http://mail.brlug.net/mailman/listinfo/general_brlug.net >>> >>> >> ___ >> General mailing list >> General at brlug.net >> http://mail.brlug.net/mailman/listinfo/general_brlug.net >> >> > > > ___ > General mailing list > General at brlug.net > http://mail.brlug.net/mailman/listinfo/general_brlug.net
[brlug-general] open source document management?
Shannon, I kind of lost track of this thread and too lazy to see if somebody mentioned this before. Anyway came across this on /. but may work for our purpose. http://www.openfiler.com/about/ Karthik
[brlug-general] open source document management?
CM Banker wrote: > > documentation. Our biggest challenge is a huge critical mass of > domain & system knowledge is required just to start doing any > practical development. > That was one of our problems as well. > Of course, making developers churn out useful, appropriately detailed > documents is like pulling teeth from a mule, and this, of course, is > easier than making them use a formal system. :-) > The way I figured it, people were filling up notebooks and such with information. I just wanted them to put it online and share it. Some people are better documenters than others. I tried to make it both simple and flexible. some people will just cut and paste text with no formatting at all and that's fine. Most, however, actually use the mini wiki markup language to build reasonably well organized documentation. You really just need one or two people to lead the way by example. the informal nature of it helps a LOT with a group like this. > Scott, Do you mind if I contact you off list for a couple of other questions? > sure > Thanks, > > -CMB > > ___ > General mailing list > General at brlug.net > http://mail.brlug.net/mailman/listinfo/general_brlug.net > >
[brlug-general] open source document management?
On Nov 20, 2007 6:38 PM, Scott Harney wrote: > > You know, you would think that, but in practical use, we really haven't > found that to be true. I suppose if your organization has strict > documentation format requirements, this wouldn't be a good fit. And you > could break up a twiki into multiple "webs" each with its own groups of > authors/editors who control the content underneath. My organization is in the formative stage of document management. We're in two groups : one that has an effective, predictable but inefficient means of documentation ( document templates & directory structure for projects) and the other that is becoming more formal in its process due to project growth and team growth. (Very small shop growing fast in work and talent) The first group's documentation style/need/contents reflect a predictable process by capturing named rigid artifacts and correspondences. They do the same thing-ish over and over. On the other hand, the formative group is a development group trying to : insure all developers understand what they're working on (background & constantly shifting requirements), keep track of projects (project management), manage defects, and feed the process that generates user documentation. Our biggest challenge is a huge critical mass of domain & system knowledge is required just to start doing any practical development. The systems we deal with are complex (but not that complicated), and the nature of the information is difficult to chain in an exposed predictable manner. (I feel tired just thinking about it).(Now that I think of it, a wiki, with clonable sections and some initial organization is looking good for this stuff). Maintaining proper currency with the documents and schedules is a bear. > We've been using twiki (http://twiki.org) on our team for about two > years now. Our team consists of unix, mainframe and storage > administrators and engineers. We have a multitude of projects as well > as daily operational responsibilities to keep track of and while people > in the group have their particular points of focus, we all need to be > aware of how to pick up some of the other responsibilities. > > We use numerous add-ons, some of which shipped with it, and some of > which we added after the fact I looked over the url - this impresses me as a fairly mature implementation of a wiki.Even a doxy plugin. Of course, making developers churn out useful, appropriately detailed documents is like pulling teeth from a mule, and this, of course, is easier than making them use a formal system. :-) Scott, Do you mind if I contact you off list for a couple of other questions? Thanks, -CMB
[brlug-general] open source document management?
CM Banker wrote: > Scott, I'd like a backgrounder on the TWIKI thing as well. I > experimented with a wiki setup and simply had issues or putting it > into practical use. It seems that for a wiki to work, one would have > to define it in excruciating detail or risk it coming scattered in > normal usage. > You know, you would think that, but in practical use, we really haven't found that to be true. I suppose if your organization has strict documentation format requirements, this wouldn't be a good fit. And you could break up a twiki into multiple "webs" each with its own groups of authors/editors who control the content underneath. We've been using twiki (http://twiki.org) on our team for about two years now. Our team consists of unix, mainframe and storage administrators and engineers. We have a multitude of projects as well as daily operational responsibilities to keep track of and while people in the group have their particular points of focus, we all need to be aware of how to pick up some of the other responsibilities. When I got here, they had a system of formal documentation through word documents. They were version controlled in the sense that you stuck a version number in the header and there was a rigid corporate standard for how they should be formatted. It didn't work because most of the procedures were out of date. Things simply change to fast Also, a lot of the expected format items really didn't make sense. And so they were hard for people to write. Despite this, people were keeping documentation. They were just doing it in their own home directories. Lots of little, "howtoaddadisk.txt" files and the like all scattered about. I wanted to do something about that and I looked at Wiki solutions as well as some CMS stuff like Zope and plone.I settled on TWiki. 1) no database - it uses built unix rcs and diff tools for version control 2) perl. yeah, I like python too, but I knew perl better and could implement mod_perl for performance benefits at the time we stood this up. That said, I've done no coding for this. 3) I figured out how to hook apache into corporate ldap. So all company users could see our documentation (except for documents we might want to explicitly limit) but only users configured to do so within twiki could author/edit content. As part of becoming a member of our group, part of the checklist (maintained in the wiki, of course) is to add the user into the twiki environment. 4) the server was a spare. the software was free. Originally, my thought was that this would not replace the original formal documentation standards, but augment things so we'd have some real useful documentation that we could refer to to get our jobs done. The reality is, we don't use the formal documentation anymore. When its required, I can supply a direct link into a document in our TWiki which is visible inside the company and thus other folks can review it. Again, the version control is built in so if a version changes, it's very easy to see within twiki what changed, by whom, and when. We use numerous add-ons, some of which shipped with it, and some of which we added after the fact 1) I found a macro set for word that converts a word doc into the twiki shorthand. this allowed me to import several documents easily 2) There is a WYSIWYG editor that you can cut and paste to and from Word. 3) we can export to PDF easily for "static" documents 4) there is a Q&A component which allows users to post questions so we can build up FAQ pages 5) We use an add-on call PublishContrib that exports the entire twiki to static html. We then replicate that for Disaster Recovery. The documentation is not pretty much critical to day to day operations. 6) every day we mail the "changes" out to the group so everyone can see what's been added or updated that day. Organization of the content was originally a big concern for my boss. So we laid out the front page a little bit with some basic thoughts on how we thought it should be organized. It was pretty straightforward. The front page is essentially a page of links into other subtopics. Those are typically organizational pages as well. It's only at the third level that you get to the "meat" so to speak. And of course, it's all searchable. For example, we do a lot of Project work. so on the front page there is a link to a front page for the project, eg, FooDeploymentProject The FooDeploymentProject page then is well organized with some sub-pages containing items you would expect such as a description of the project, contact list, contract and support details, links to project manuals. Following that on the same page, are links to procedures we've written up. We came up with a template for projects and items and pages that we expect to see for every project. It's easy to cut and paste the intial template and create the expected project pages. After that, it's pretty
[brlug-general] open source document management?
Scott, I'd like a backgrounder on the TWIKI thing as well. I experimented with a wiki setup and simply had issues or putting it into practical use. It seems that for a wiki to work, one would have to define it in excruciating detail or risk it coming scattered in normal usage. -Craig On Nov 20, 2007 5:36 PM, Scott Harney wrote: > Shannon Roddy wrote: > > I'm debating on punting and just setting up a table updated by hand. > > It would be *really* nice to find something that would allow other > > users to post docs and metadata about the doc... I guess I just need > > to find time to evaluate the ones google brings up. not enough hours > > in the day > > > I'm not exactly sure what you're usage scenario is, but if it's just > internal documentation, we use TWiki in my shop. most people write > straight into the Wiki which does automatic version control. We hooked > authentication into LDAP, of course. some people do upload non-html > attachment, eg Word docs, pdf, etc. > > It's simple, but it works. > > > > On Nov 20, 2007 3:08 PM, Tim Fournet wrote: > > > >> We're using Plone right now as kind of a documentation repository. I > >> like it and wanted to use it as a DMS, but I didn't find it that handy > >> for uploaded files > >> > >> > >> CM Banker wrote: > >> > >>> Plone is a CMS but has most of the elements of a DMS with the > >>> exception of integrated scanning & tagging (ala Paragon Filenet). > >>> > >>> It is multi-platform. > >>> > >>> On Nov 20, 2007 9:00 AM, Tim Fournet wrote: > >>> > >>> > There are a couple that I know of that you may want to consider: > knowledgeTree and Alfresco. Alfresco is more of a CMS, but is built to > work well for document management > I haven't chosen one for myself yet, but it is on my to-to list. > > > > > Shannon Roddy wrote: > > > > I can't remember if this has come up before, but anyone know of a good > > open source document management package out there? Hopefully with the > > ability to specify different access controls per file. Yes, this > > would be running on Linux/Apache. ;-) > > > > While I am at it... any suggestions on web based calendaring? > > > > -Shannon > > > > ___ > > General mailing list > > General at brlug.net > > http://mail.brlug.net/mailman/listinfo/general_brlug.net > > > > > > > ___ > General mailing list > General at brlug.net > http://mail.brlug.net/mailman/listinfo/general_brlug.net > > > > >>> ___ > >>> General mailing list > >>> General at brlug.net > >>> http://mail.brlug.net/mailman/listinfo/general_brlug.net > >>> > >>> > >> ___ > >> General mailing list > >> General at brlug.net > >> http://mail.brlug.net/mailman/listinfo/general_brlug.net > >> > >> > > > > ___ > > General mailing list > > General at brlug.net > > http://mail.brlug.net/mailman/listinfo/general_brlug.net > > > > > > > ___ > General mailing list > General at brlug.net > http://mail.brlug.net/mailman/listinfo/general_brlug.net >
[brlug-general] open source document management?
>From all descriptions, plone seems pretty good. I think it beats the ms cms buzzword du jour - share point. I'm genuinely curious in how you guys are using it; i.e. context, organization, how much effort it took to set up.How software such as this is used is as important as why it is used. I'm looking to find a great excuse to sidestep sharepoint, which I find lacking and extremely annoying. Personally, I've played with plone but have not had a chance to really use it formally. In the past, I mostly dealt with Zope sites and applications. As John said, Xinco looks to be worth looking at too. On Nov 20, 2007 3:08 PM, Tim Fournet wrote: > We're using Plone right now as kind of a documentation repository. I > like it and wanted to use it as a DMS, but I didn't find it that handy > for uploaded files > > > CM Banker wrote: > > Plone is a CMS but has most of the elements of a DMS with the > > exception of integrated scanning & tagging (ala Paragon Filenet). > > > > It is multi-platform. > > > > On Nov 20, 2007 9:00 AM, Tim Fournet wrote: > > > >> There are a couple that I know of that you may want to consider: > >> knowledgeTree and Alfresco. Alfresco is more of a CMS, but is built to > >> work well for document management > >> I haven't chosen one for myself yet, but it is on my to-to list. > >> > >> > >> > >> > >> Shannon Roddy wrote: > >> > >>> I can't remember if this has come up before, but anyone know of a good > >>> open source document management package out there? Hopefully with the > >>> ability to specify different access controls per file. Yes, this > >>> would be running on Linux/Apache. ;-) > >>> > >>> While I am at it... any suggestions on web based calendaring? > >>> > >>> -Shannon > >>> > >>> ___ > >>> General mailing list > >>> General at brlug.net > >>> http://mail.brlug.net/mailman/listinfo/general_brlug.net > >>> > >>> > >> ___ > >> General mailing list > >> General at brlug.net > >> http://mail.brlug.net/mailman/listinfo/general_brlug.net > >> > >> > > > > ___ > > General mailing list > > General at brlug.net > > http://mail.brlug.net/mailman/listinfo/general_brlug.net > > > > > ___ > General mailing list > General at brlug.net > http://mail.brlug.net/mailman/listinfo/general_brlug.net >
[brlug-general] open source document management?
Shannon Roddy wrote: > I'm debating on punting and just setting up a table updated by hand. > It would be *really* nice to find something that would allow other > users to post docs and metadata about the doc... I guess I just need > to find time to evaluate the ones google brings up. not enough hours > in the day > I'm not exactly sure what you're usage scenario is, but if it's just internal documentation, we use TWiki in my shop. most people write straight into the Wiki which does automatic version control. We hooked authentication into LDAP, of course. some people do upload non-html attachment, eg Word docs, pdf, etc. It's simple, but it works. > On Nov 20, 2007 3:08 PM, Tim Fournet wrote: > >> We're using Plone right now as kind of a documentation repository. I >> like it and wanted to use it as a DMS, but I didn't find it that handy >> for uploaded files >> >> >> CM Banker wrote: >> >>> Plone is a CMS but has most of the elements of a DMS with the >>> exception of integrated scanning & tagging (ala Paragon Filenet). >>> >>> It is multi-platform. >>> >>> On Nov 20, 2007 9:00 AM, Tim Fournet wrote: >>> >>> There are a couple that I know of that you may want to consider: knowledgeTree and Alfresco. Alfresco is more of a CMS, but is built to work well for document management I haven't chosen one for myself yet, but it is on my to-to list. Shannon Roddy wrote: > I can't remember if this has come up before, but anyone know of a good > open source document management package out there? Hopefully with the > ability to specify different access controls per file. Yes, this > would be running on Linux/Apache. ;-) > > While I am at it... any suggestions on web based calendaring? > > -Shannon > > ___ > General mailing list > General at brlug.net > http://mail.brlug.net/mailman/listinfo/general_brlug.net > > > ___ General mailing list General at brlug.net http://mail.brlug.net/mailman/listinfo/general_brlug.net >>> ___ >>> General mailing list >>> General at brlug.net >>> http://mail.brlug.net/mailman/listinfo/general_brlug.net >>> >>> >> ___ >> General mailing list >> General at brlug.net >> http://mail.brlug.net/mailman/listinfo/general_brlug.net >> >> > > ___ > General mailing list > General at brlug.net > http://mail.brlug.net/mailman/listinfo/general_brlug.net > >
[brlug-general] open source document management?
I'm debating on punting and just setting up a table updated by hand. It would be *really* nice to find something that would allow other users to post docs and metadata about the doc... I guess I just need to find time to evaluate the ones google brings up. not enough hours in the day On Nov 20, 2007 3:08 PM, Tim Fournet wrote: > We're using Plone right now as kind of a documentation repository. I > like it and wanted to use it as a DMS, but I didn't find it that handy > for uploaded files > > > CM Banker wrote: > > Plone is a CMS but has most of the elements of a DMS with the > > exception of integrated scanning & tagging (ala Paragon Filenet). > > > > It is multi-platform. > > > > On Nov 20, 2007 9:00 AM, Tim Fournet wrote: > > > >> There are a couple that I know of that you may want to consider: > >> knowledgeTree and Alfresco. Alfresco is more of a CMS, but is built to > >> work well for document management > >> I haven't chosen one for myself yet, but it is on my to-to list. > >> > >> > >> > >> > >> Shannon Roddy wrote: > >> > >>> I can't remember if this has come up before, but anyone know of a good > >>> open source document management package out there? Hopefully with the > >>> ability to specify different access controls per file. Yes, this > >>> would be running on Linux/Apache. ;-) > >>> > >>> While I am at it... any suggestions on web based calendaring? > >>> > >>> -Shannon > >>> > >>> ___ > >>> General mailing list > >>> General at brlug.net > >>> http://mail.brlug.net/mailman/listinfo/general_brlug.net > >>> > >>> > >> ___ > >> General mailing list > >> General at brlug.net > >> http://mail.brlug.net/mailman/listinfo/general_brlug.net > >> > >> > > > > ___ > > General mailing list > > General at brlug.net > > http://mail.brlug.net/mailman/listinfo/general_brlug.net > > > > > ___ > General mailing list > General at brlug.net > http://mail.brlug.net/mailman/listinfo/general_brlug.net >
[brlug-general] open source document management?
We're using Plone right now as kind of a documentation repository. I like it and wanted to use it as a DMS, but I didn't find it that handy for uploaded files CM Banker wrote: > Plone is a CMS but has most of the elements of a DMS with the > exception of integrated scanning & tagging (ala Paragon Filenet). > > It is multi-platform. > > On Nov 20, 2007 9:00 AM, Tim Fournet wrote: > >> There are a couple that I know of that you may want to consider: >> knowledgeTree and Alfresco. Alfresco is more of a CMS, but is built to >> work well for document management >> I haven't chosen one for myself yet, but it is on my to-to list. >> >> >> >> >> Shannon Roddy wrote: >> >>> I can't remember if this has come up before, but anyone know of a good >>> open source document management package out there? Hopefully with the >>> ability to specify different access controls per file. Yes, this >>> would be running on Linux/Apache. ;-) >>> >>> While I am at it... any suggestions on web based calendaring? >>> >>> -Shannon >>> >>> ___ >>> General mailing list >>> General at brlug.net >>> http://mail.brlug.net/mailman/listinfo/general_brlug.net >>> >>> >> ___ >> General mailing list >> General at brlug.net >> http://mail.brlug.net/mailman/listinfo/general_brlug.net >> >> > > ___ > General mailing list > General at brlug.net > http://mail.brlug.net/mailman/listinfo/general_brlug.net >
[brlug-general] open source document management?
Did a little googling. I recommend either http://plone.org (Zope/Python based) or http://www.xinco.org (Java based). Xinco seems to provide the features you specified: * manages Documents / Files / Text / URLs / Contacts... * Full-Text Indexing and Search of Text, Adobe PDF, MS Word, MS Excel, HTML, ... * Graphical Search Query Builder * tree-based Folder / Data Object Hierarchy * native Support for organizing Multi-Language Data * direct preview / editing of Files, direct opening of Websites in default browser, direct opening of Contacts in default Email application * Standalone Java Client (multi-language), deployed via Java Web Start * Massive Data Import Tool (Multiple Files + Sub-Folders) * Access Control Lists for Users and Groups * FDA 21 CFR part 11 compliance (both XincoAdmin & XincoExplorer) * Checkin / Checkout, Version Control and preservation of previous Revisions * Data Commenting / Discussion * XincoPublisher for accessing public data (e.g. linking from external websites, browsing) * periodic File Archiving to external storage volumes * Client / Server - Communications via SOAP Web Services + SOAP with Attachments (SAAJ) * scalable Server and Web Service Engine built on Apache Axis * open to third-party Clients and direct Application Integration (Web Services + Open Source) * fast and reliable MySQL or PostgreSQL database backend * Storage Location of Files and Search Index on different volumes to optimize use of Network Storage Devices (NAS, SAN) * * xinco DMS? is growing to be a feature-rich, professional DMS for managing your critical Business Information. --- Shannon Roddy wrote: > On Nov 19, 2007 8:11 PM, John Hebert > wrote: > > Shannon, > > > > I've looked at a few open source Electronic > Document > > Management Systems a few years, but nothing was > really > > eye-catching then. > > > > A few questions: > > 1. How many total users of the system? > > Total possible users is ~500 if you count everyone, > however I don't > think everyone in the org will use it. I can see > maybe 20 people > posting docs. > > > 2. How many of those users will be using the > system at > > any one time? > > probably max of about 20 possible, more likely only > a couple - if that. > > > 3. Do you have a rough estimate of the number of > > documents you will be putting into the system over > say > > a month? > > 20+? > > 4. Any idea how large these documents will be on > the > > average? > > Everything from a small text file, to word docs, > ppt, and pdfs. > > > 5. What kind of documents will you be storing? > Images? > > PDFs? > > ^^^ > > 6. How will you be indexing the documents when put > > them in the system? By hand? Automation? > > > > Hmm... probably just user entered metadata at time > of posting. > > > Windows implementation. I am not recommending to > you > > however, as it is $$$. > > Yeah... this is a zero budget thing for a 501(c)3. > > ___ > General mailing list > General at brlug.net > http://mail.brlug.net/mailman/listinfo/general_brlug.net > Be a better pen pal. Text or chat with friends inside Yahoo! Mail. See how. http://overview.mail.yahoo.com/
[brlug-general] open source document management?
Plone is a CMS but has most of the elements of a DMS with the exception of integrated scanning & tagging (ala Paragon Filenet). It is multi-platform. On Nov 20, 2007 9:00 AM, Tim Fournet wrote: > There are a couple that I know of that you may want to consider: > knowledgeTree and Alfresco. Alfresco is more of a CMS, but is built to > work well for document management > I haven't chosen one for myself yet, but it is on my to-to list. > > > > > Shannon Roddy wrote: > > I can't remember if this has come up before, but anyone know of a good > > open source document management package out there? Hopefully with the > > ability to specify different access controls per file. Yes, this > > would be running on Linux/Apache. ;-) > > > > While I am at it... any suggestions on web based calendaring? > > > > -Shannon > > > > ___ > > General mailing list > > General at brlug.net > > http://mail.brlug.net/mailman/listinfo/general_brlug.net > > > > > ___ > General mailing list > General at brlug.net > http://mail.brlug.net/mailman/listinfo/general_brlug.net >
[brlug-general] open source document management?
There are a couple that I know of that you may want to consider: knowledgeTree and Alfresco. Alfresco is more of a CMS, but is built to work well for document management I haven't chosen one for myself yet, but it is on my to-to list. Shannon Roddy wrote: > I can't remember if this has come up before, but anyone know of a good > open source document management package out there? Hopefully with the > ability to specify different access controls per file. Yes, this > would be running on Linux/Apache. ;-) > > While I am at it... any suggestions on web based calendaring? > > -Shannon > > ___ > General mailing list > General at brlug.net > http://mail.brlug.net/mailman/listinfo/general_brlug.net >
[brlug-general] open source document management?
On Nov 19, 2007 8:11 PM, John Hebert wrote: > Shannon, > > I've looked at a few open source Electronic Document > Management Systems a few years, but nothing was really > eye-catching then. > > A few questions: > 1. How many total users of the system? Total possible users is ~500 if you count everyone, however I don't think everyone in the org will use it. I can see maybe 20 people posting docs. > 2. How many of those users will be using the system at > any one time? probably max of about 20 possible, more likely only a couple - if that. > 3. Do you have a rough estimate of the number of > documents you will be putting into the system over say > a month? 20+? > 4. Any idea how large these documents will be on the > average? Everything from a small text file, to word docs, ppt, and pdfs. > 5. What kind of documents will you be storing? Images? > PDFs? ^^^ > 6. How will you be indexing the documents when put > them in the system? By hand? Automation? > Hmm... probably just user entered metadata at time of posting. > Windows implementation. I am not recommending to you > however, as it is $$$. Yeah... this is a zero budget thing for a 501(c)3.
[brlug-general] open source document management?
Shannon, I've looked at a few open source Electronic Document Management Systems a few years, but nothing was really eye-catching then. A few questions: 1. How many total users of the system? 2. How many of those users will be using the system at any one time? 3. Do you have a rough estimate of the number of documents you will be putting into the system over say a month? 4. Any idea how large these documents will be on the average? 5. What kind of documents will you be storing? Images? PDFs? 6. How will you be indexing the documents when put them in the system? By hand? Automation? What most organizations want in a document management system is fast document retrieval performance combined with metadata indexing for those documents. Normal filesystems kinda suck when you have hundreds of thousands of documents and a lot of users all trying to access them at the same time, especially if there is revision control. I've managed FileNet (http://www.filenet.com) systems in the past, while not open source, is used by large corps and runs on UNIX, Linux and Windows. It was originally written for UNIX, which can be seen in the file structure and naming conventions, even on a Windows implementation. I am not recommending to you however, as it is $$$. FileNet is fast and scalable because it provides a custom filesystem (32GB "virtual platters", no blocks) with flat file indexing for storing the location and other file info (number of bytes in file, etc.) about the documents. User metadata document searches are handled via an RDBMS, which provides a document ID to the row in the flat file DB. Whatever you do, choose _very_ carefully, as converting from one EDMS to another is painful and slow. Let me know if you have any other questions. John Hebert --- Shannon Roddy wrote: > I can't remember if this has come up before, but > anyone know of a good > open source document management package out there? > Hopefully with the > ability to specify different access controls per > file. Yes, this > would be running on Linux/Apache. ;-) > > While I am at it... any suggestions on web based > calendaring? > > -Shannon > > ___ > General mailing list > General at brlug.net > http://mail.brlug.net/mailman/listinfo/general_brlug.net > Be a better pen pal. Text or chat with friends inside Yahoo! Mail. See how. http://overview.mail.yahoo.com/
[brlug-general] open source document management?
I can't remember if this has come up before, but anyone know of a good open source document management package out there? Hopefully with the ability to specify different access controls per file. Yes, this would be running on Linux/Apache. ;-) While I am at it... any suggestions on web based calendaring? -Shannon
