Export Journal

[vlion]

I have a draft design for solving Bug 32 up here:

http://wiki.dwscoalition.org/notes/Export_Journal_Notes

It looks like it is a medium-sized project with three areas of expertise(DW server configuration, programming and graphic design).

There are several open questions about how an export should look, and I've left those for someone who is good at graphic design to write.

I would appreciate comments and review.

Comments

[denise]

I think it should be a combination paid user/non-paid user feature: "export all contents in the journal in a single format (.pdf) once per year" should be something everyone can do, while "export more frequently/whenever you want", "export in html/latex/other esoteric formats", "export by privacy level", "export by tag", etc etc, should be a paid user feature.

[zvi]

Er, do you mean that whoever is running the site should be able to peg how often exports of what kind are done by each account level? Dreamwidth really needs to keep heavy use cases to paid (although I do think an annual free export is an awesome idea!), but somebody's special purpose install may not need to be that restrictive and somebody's completely hobbyist site may want to forbid it all together.

[denise]

Yeah, sorry, that was what I meant -- controlled by config options, with dual "how many times per {month/year} someone could export" and "can use advanced export tools" caps.