Alan Burlison wrote:
The original version of the script included the text that triggered the redaction in the REDACTED.txt file. I was asked to remove that information.

At present there are only 2 redacted cases, so I don't think it is correct to say that information which was previously open is now being hidden.

If you read my reply to Glenn on arc-discuss, I believe that I have a solution that would address the particular problem with your opinion.ms file.

I think maybe you've missed my intent. I'm getting tired of spelunking to discover what things I can and can't do with regard to documents I produce for the ARC community. This is the second occasion where a document I produced was put on an internal file system and resulted in the case becoming obscured on the web site -- either through redaction or files being ignored. This is the second time that a case that had its entire materials published as externally available became completely unavailable by content of a document I produced. This is the second time that information was available one day, and then completely unavailable the next. Yes, you've got a proposal for /this/ instance. But I'm still in the dark, and have to guess. And worse, when I get blindsided by these things, I have to beg for help from folks on the inside who can twiddle the bits. Then I get to whinge about it long enough and hard enough on this list to get something just a single clue as to what happened /that/ time. I tire of chasing the hidden rules. I tire of having to rely on the help of folks on SWAN to help tweak my stuff because I wasn't able to get it right before it got put in those directories.

I fully intend to understand what the rules are for why files are ignored. What are the extensions? What are the filenames? I fully intend to understand which expressions will cause a case redaction under the current tool(s), and then avoid those terms. I, like many others, don't agree with the current implementation of how the tool is working with regard to *open* cases, but I also clearly don't even fully understand it and am being told I do not have the right to know it. So I also intend to continue to campaign to change that implementation so that it is usable by external contributors. Or for that matter, internal contributors as well, as I suspect not many (if any) internal ARC members or licensees know all the rules.
_______________________________________________
website-discuss mailing list
[email protected]

Reply via email to