* Locked storage room for paper(tape) storage
* Virtual Machine image off-site
* Local office file server
*) Scan and process documents in the local office storing the documents on the local server.
*) Make sure your local and remote server are running an encrypted filesystem on top of a RAID with mirroring.
*) Set up an rsync cron job to sync your virtual machine to the local office fileserver
*) Then archive the paper documents daily or weekly or monthy (you could even in parallel do tape backups)
This sort of set up would not be expensive for a small amount of storage (i.e. office) and will cover you on fire protection, original retention, etc.
p.s. I don't want to here any of this Perl is ugly crap either - it's not my fault I don't need my language to -make- me write readable code. A good Perl programmers code is readable anyways.
Before jumping into some gauntlet of distributed (or aggregated or what ever you want to call it) JavaScript testing. Shouldn't there be a FOSS [cross]platform for unit testing JavaScript under multiple "rendering kits/engines" that can be plugged into Rake, TAP or Nose or any other unit testing harness.
For most applications things like Selenium are more trouble or cost to much money then they are worth.
I would like to see something that would allow me to test my JS code across multiple browsers with a simple "make test" within my build environment.
Of course there are things like JSLint and Rhino etc... but they don't really handle the issue of making the tests easy to write and run (which means dev's will actually write the tests) on top of Rhino not really representing an actual or even a mock of a particular browsers DOM.
I don't relish the idea of having to build an special application into my test harness and then direct my browser to a URL in order to run my JavaScript unit tests.
There are plenty of systems out there that compile test reports across multiple platforms from a standard harness (CPAN Testers for one).
The problem is not test reporting - it's having an easy way to write and run the tests.
With CentOS or RHEL (fundamentally the same, but still two different entities) the sysadmins should setup a central yum repository for in-house and custom built software. Developers should be building in-house packages into RPMS with dependencies for the correct build of Perl.
I ran into this problem a while ago building a DBIC API on the stock CentOS 5 perl build. DBIC really complains about the slow Perl bug...
So, I build an rpm for Perl 5.10 and setup a yum repo. Also I deploy my Perl applications through yum+rpm as well - all my app rpms depend on my in-house perl rpm which keeps dependency issues to a minimum. If you are worried about CPAN dependencies just make sure the applications install spec does the correct stuff with your Makefile.PL and you are using a perl build environment that does CPAN require+installs (that way you don't have to build rpms for each CPAN module:).
I doubt if I was using RHEL with a support contract that they would give me any guff what I've done.
The upside of this method is that if the sysadmins are motivated enough they can build entire kickstart installs that install groups of home-grown software for specific business purposes.
Well the phrase search could be implemented by first using indexed "word relations and scores" to slim down the search set:
-> break phrase into "words"
-> do join query for documents containing those words
-> search for phrase inside of documents that contain those words
I'm certainly not an expert in search engines or even relation databases for that matter. It just struck me as bad practice to-do query killing.
Maybe something on the query level would work in your case: limit -> page -> timeout
Limit your results to 50 per set if set exceeds limit implement paging and if the query exceeds a timeout (implemented in web app) the application kills the query on the client side and returns a meaningful "Query timeout, please try a less generic search term" message.
Killing other queries that seems like a bad idea...
Why not index and and rate all the words in all the documents...
A dictionary (think Websters) table with a many to many indexed relationship would I think improve your results.
Just split all the words in the document (upon insert) sort for unique with count (turn in into a hash) then under the documents "meta" table you link to the "word id" from the dictionary table and sort by "count" (number of times the word occurs in the document + maybe rate of popularity for the document)
That way the frequency for any common dictionary word is already calculated for in a search-able way for any document uploaded.
Save the full-text search for deep searches.
I think the true cospiracy was to make public sub subconsciously connotate the term "conspiracy theorist" as something negative.
Anyways joking aside, you are right.
Reluctance to test a result is simply bad sience. Ff everyone was reluctant to test then we (as a culture) would still assume the world was flat.
Speaking of which, damn those flat earthers.
Walking down the street with a NES controller strapped to your belt: Yep, that's gonna be a good look... Why is it I can't picture anyone but Steve Irkle doing this?
a) "Tech" workers don't dress nice.
b) "Tech" workers tend to be the one group within an organization that doesn't have to make up reasons why their jobs exist.
Example of other groups making up work so they have a job:
Marketing = I need to dress nice in order to confuse potential buyers by my "flashy" style in order to put them in subdued state in which they will be stupid enough to buy our over priced product.
Human Resources = I need to have you fill out all this paper work so that we can review it and then give our office assistants something to-do by filing said paper work
Management = I need to make illogical business decisions that create loads of work for those down the hierarchy. Then when my "minions" eventually figure it out and simplify the whole process, I can take credit for it as my whole idea to begin with.
Even though a system such as this would seem to have the logical result of killing the art of music, it simply can not.
As a musician I have noticed that the more I study music theory (theory is really just the language to describe music) the more I come to realize that almost all music is the same. You can spot similarities between four hundred year old classics and current "Indie"/Pop/Rock/Whatever, the connection is there.
So what might you ask makes it different?
The style makes it different. The way the individual artist performs/arranges/records a piece. Not to mention that lyrical content adds a whole new dimension?
Saying something like this will ruin the art of music is like saying that the grammar checker in any document editor ruins the art of writing. Though it is neat that a program could possible sort out "popular" music, which just means it's able to emulate the human ear just a little bit.
Ooh it's AJAX, OMG it's going to change the world!!!
Is it just me or did this post feel like an advertisement for a bunch of organizations that like to sell simple things packaged in a fancy wrapper?
This may be slightly off topic however I would like to make a clarification; Police do not have the authority to "levy punishment" for any non-convicted criminal.
The court/justice system does, the role of police is to enforce law through investigation and apprehension.
So the should process should go like this:
Student does something questionable out side of school.
School administration files a complaint with the Police.
Police then investigate and apprehend the student if the complaint is founded in police-able law.
The student then faces the justice system...
I just wanted to make this point as it seems like a common misconception that police are the law, they are in fact not the law only the face/hand of the law.
And, just for my juvenile edification I would like to point out the police motto is "To Project and Serve" something that is increasingly being ignored.
Well, you are correct in assuming I'm not in school.
Blogs like phone numbers (voluntary) can be moderated (even more so than phone numbers) and to tell you the truth I would much rather face public ridicule on an internet forum then in real life.
At least you can't get punched in the nose on a Blog.
If you don't want to have people read your entries then don't post publicly, if you do post publicly then be prepared to defend your point of views. I think this stands true with any form of communication that can be accessed publicly.
If I were to print up a couple hundred "zines" stating my point of view (let's say local politics) and then proceeded to distribute them around the city I lived in, I would then be forced to defend my perspective. On the other side of that, if I were to write in my personal journal that I kept as private property I would not expect to have to defend what I write.
How 'bout someone gather up all of the commercial interests and start the A.A.S.C (American Aeronautics and Space Co-operation) and give NASA a bit of internal competition.
Maybe then they would be a bit more careful with their resources!
p.s. Is there such a thing as a non-government space agency(yet)?
Slashdot Mirror
DON'T PANIC.
Ok, how about this:
3 locations in different areas:
* Locked storage room for paper(tape) storage
* Virtual Machine image off-site
* Local office file server
*) Scan and process documents in the local office storing the documents on the local server.
*) Make sure your local and remote server are running an encrypted filesystem on top of a RAID with mirroring.
*) Set up an rsync cron job to sync your virtual machine to the local office fileserver
*) Then archive the paper documents daily or weekly or monthy (you could even in parallel do tape backups)
This sort of set up would not be expensive for a small amount of storage (i.e. office) and will cover you on fire protection, original retention, etc.
Perl would be better.
p.s. I don't want to here any of this Perl is ugly crap either - it's not my fault I don't need my language to -make- me write readable code. A good Perl programmers code is readable anyways.
sorry for the poor formatting - I hit submit instead of "continue editing" :)
Before jumping into some gauntlet of distributed (or aggregated or what ever you want to call it) JavaScript testing. Shouldn't there be a FOSS [cross]platform for unit testing JavaScript under multiple "rendering kits/engines" that can be plugged into Rake, TAP or Nose or any other unit testing harness.
For most applications things like Selenium are more trouble or cost to much money then they are worth. I would like to see something that would allow me to test my JS code across multiple browsers with a simple "make test" within my build environment. Of course there are things like JSLint and Rhino etc... but they don't really handle the issue of making the tests easy to write and run (which means dev's will actually write the tests) on top of Rhino not really representing an actual or even a mock of a particular browsers DOM. I don't relish the idea of having to build an special application into my test harness and then direct my browser to a URL in order to run my JavaScript unit tests. There are plenty of systems out there that compile test reports across multiple platforms from a standard harness (CPAN Testers for one). The problem is not test reporting - it's having an easy way to write and run the tests.
I rather save the $$$ :)
With CentOS or RHEL (fundamentally the same, but still two different entities) the sysadmins should setup a central yum repository for in-house and custom built software. Developers should be building in-house packages into RPMS with dependencies for the correct build of Perl.
:).
I ran into this problem a while ago building a DBIC API on the stock CentOS 5 perl build. DBIC really complains about the slow Perl bug... So, I build an rpm for Perl 5.10 and setup a yum repo. Also I deploy my Perl applications through yum+rpm as well - all my app rpms depend on my in-house perl rpm which keeps dependency issues to a minimum. If you are worried about CPAN dependencies just make sure the applications install spec does the correct stuff with your Makefile.PL and you are using a perl build environment that does CPAN require+installs (that way you don't have to build rpms for each CPAN module
I doubt if I was using RHEL with a support contract that they would give me any guff what I've done.
The upside of this method is that if the sysadmins are motivated enough they can build entire kickstart installs that install groups of home-grown software for specific business purposes.
Well the phrase search could be implemented by first using indexed "word relations and scores" to slim down the search set: -> break phrase into "words" -> do join query for documents containing those words -> search for phrase inside of documents that contain those words I'm certainly not an expert in search engines or even relation databases for that matter. It just struck me as bad practice to-do query killing. Maybe something on the query level would work in your case: limit -> page -> timeout Limit your results to 50 per set if set exceeds limit implement paging and if the query exceeds a timeout (implemented in web app) the application kills the query on the client side and returns a meaningful "Query timeout, please try a less generic search term" message.
Killing other queries that seems like a bad idea... Why not index and and rate all the words in all the documents... A dictionary (think Websters) table with a many to many indexed relationship would I think improve your results. Just split all the words in the document (upon insert) sort for unique with count (turn in into a hash) then under the documents "meta" table you link to the "word id" from the dictionary table and sort by "count" (number of times the word occurs in the document + maybe rate of popularity for the document) That way the frequency for any common dictionary word is already calculated for in a search-able way for any document uploaded. Save the full-text search for deep searches.
I think the true cospiracy was to make public sub subconsciously connotate the term "conspiracy theorist" as something negative. Anyways joking aside, you are right. Reluctance to test a result is simply bad sience. Ff everyone was reluctant to test then we (as a culture) would still assume the world was flat. Speaking of which, damn those flat earthers.
In order to do that someone would have to create an Infinite Improbability Drive and we all know how unlikely that is.
Walking down the street with a NES controller strapped to your belt: Yep, that's gonna be a good look... Why is it I can't picture anyone but Steve Irkle doing this?
You have obviously never seen a hipster...
b) "Tech" workers tend to be the one group within an organization that doesn't have to make up reasons why their jobs exist.
Example of other groups making up work so they have a job:
Marketing = I need to dress nice in order to confuse potential buyers by my "flashy" style in order to put them in subdued state in which they will be stupid enough to buy our over priced product.
Human Resources = I need to have you fill out all this paper work so that we can review it and then give our office assistants something to-do by filing said paper work
Management = I need to make illogical business decisions that create loads of work for those down the hierarchy. Then when my "minions" eventually figure it out and simplify the whole process, I can take credit for it as my whole idea to begin with.
Even though a system such as this would seem to have the logical result of killing the art of music, it simply can not.
As a musician I have noticed that the more I study music theory (theory is really just the language to describe music) the more I come to realize that almost all music is the same. You can spot similarities between four hundred year old classics and current "Indie"/Pop/Rock/Whatever, the connection is there.
So what might you ask makes it different?
The style makes it different. The way the individual artist performs/arranges/records a piece. Not to mention that lyrical content adds a whole new dimension?
Saying something like this will ruin the art of music is like saying that the grammar checker in any document editor ruins the art of writing. Though it is neat that a program could possible sort out "popular" music, which just means it's able to emulate the human ear just a little bit.
Ooh it's AJAX, OMG it's going to change the world!!! Is it just me or did this post feel like an advertisement for a bunch of organizations that like to sell simple things packaged in a fancy wrapper?
This may be slightly off topic however I would like to make a clarification; Police do not have the authority to "levy punishment" for any non-convicted criminal. The court/justice system does, the role of police is to enforce law through investigation and apprehension.
So the should process should go like this:
I just wanted to make this point as it seems like a common misconception that police are the law, they are in fact not the law only the face/hand of the law.
And, just for my juvenile edification I would like to point out the police motto is "To Project and Serve" something that is increasingly being ignored.
I here you. Does anyone else remember when you had to use frames to exchange data between browser and server with out a page refresh?
Failed to compile: Mixed types in context of comparison!
Well, you are correct in assuming I'm not in school. Blogs like phone numbers (voluntary) can be moderated (even more so than phone numbers) and to tell you the truth I would much rather face public ridicule on an internet forum then in real life. At least you can't get punched in the nose on a Blog.
If you don't want to have people read your entries then don't post publicly, if you do post publicly then be prepared to defend your point of views. I think this stands true with any form of communication that can be accessed publicly.
If I were to print up a couple hundred "zines" stating my point of view (let's say local politics) and then proceeded to distribute them around the city I lived in, I would then be forced to defend my perspective. On the other side of that, if I were to write in my personal journal that I kept as private property I would not expect to have to defend what I write.
In short don't make your self a target.
So, power to the people?
How 'bout someone gather up all of the commercial interests and start the A.A.S.C (American Aeronautics and Space Co-operation) and give NASA a bit of internal competition.
Maybe then they would be a bit more careful with their resources!
p.s. Is there such a thing as a non-government space agency(yet)?