Closed jehlers closed 8 years ago
From chat:
@jehlers
I just added this issue: Anyone else have better ideas? and should it be added to this sprint?
@cmc333333
we won't know the tracking number at pdf generation time, so if we can avoid it, we skip a step can we use the title of the proposal (say 15 chars of it)?
@jehlers
That’s why I was thinking eManifest...
@tadhg-ohiggins
well, the title for this rule is "Hazardous Waste Management System; ..."[trimmed by ed] So first 15 would be
hazardous waste
@cmc333333
PERFECT, roll it. what I'd like to avoid is having a configuration per notice, if that makes sense we've got a few pieces of meta data (the FR id, the docket id, the title, the agency, the url) that we could use automatically probably more
@tadhg-ohiggins
Right. Yes, the only thing I'd add to that is possibly a timestamp for the comment, so that multiple comments by the same user don't have the same filename.
Are we sure we want the 1st 15 characters of the title? We will end up with "DRAFT_comment_hazardous waste.pdf" and "Comment_hazardous waste.pdf". For the 1st 3 Proposed Rules in today's Federal Register, we would end up with:
My recommendation is to use the FR id
, which is compact, or the docket id
.
Are we sure we want the 1st 15 characters of the title?
I, for one, am not. I like the cleanliness of using one of the ids, but they are meaningless outside of the FR and regs.gov. When FR docs are cited, they use volume + page. Maybe we could use the agency name? Maybe the publish date of the proposal? We also have access to the FR citation if it'd be helpful.
Timestamps are ugly ... Shouldn't we leave it to the browsers?
I agree. The one caveat here is that if we use a very generic doc title (like the agency name alone), the browser-provided file name might not be enough to be distinguishing. To put it differently, I think it'd be fine to use one filename per proposal; we should try to avoid the same filename being reused by different proposals, however.
I like the FR citation... it definitely adds some specificity that's easier to plan for than the title of the rule. Not great for the general public, but good for all the lawyers who will probably be the first users on this tool.
Docket ID would be my second pick probably, only due to length and that it has less meaning off the bat. At least a citation has a use in that I could more easily look up the rule. What do you all think?
Third pick would be the agency acronym. Then we would have "comment_EPA.pdf" or "DRAFT_comment_EPA.pdf" which would work well for us now, but might have issues in the future if EPA has 2 rules up and open for comment.
Right now when I download a draft document, the file is named comment.pdf. I'm not sure what happens when its the final comment. Can/should we do the following:
Draft:
Final: