Importing - dreamwidth/dreamwidth GitHub Wiki

Table of Contents TODO Other Ideas Importing Comments Email templates Could not access account Possible failure messages Journal transferred Possible issue texts Icon import Entries import Comments import Ways to enter a service name Compatibility LiveJournal DeadJournal JournalFen InsaneJournal

• Get it compiling after some changes merged in from test tool.
• Userpics
  • Need to fail cleaner if this is missing (like on DJ)
• Entries Almost done
  • Probably need to scrub a few more things.

  <lj-template name="qotd" id="..." /> for instance

• Friends
  • I think this is wanted, import them as OpenID?
• Comments
  • I need to find a proper "insert comment and metadata in the same instant" command, as I don't want a possible instant where someone can see a comment that is supposed to be screened.

• <ljuser>exor674</ljuser> I think one of the things we'd need to add for the import feature is a external-logid logprop, so if somebody tries to import twice you won't get twice of the entries -- AND the systen can know "oh DW entry 1 was originally livejournal.com-exor674-5827377212221211"
• "Imported from" tag and link
• Options: "import tags, tag prefix, tag suffix" "import comments"? "import friend groups, tag prefix, tag suffix" "import all as *security*"

• Copyright issues. Idea from <ljuser>azurelunatic</ljuser>:

Supposing comments belonging to others were imported and privately posted, and comments belonging to the user were imported and posted according to their current screening setting in proper threads with the private comments. This would allow a maximum amount of the user's own content to show up.

Supposing also that the comment screening mechanism were modified to handle privately-posted imported comments. This would be done according to the screening settings on the original post: if unscreened on the original, someone OpenID-authenticated as the original comment poster could elect to own and unprivatescreen comments belonging to them.

After this point, the journal owner could screen/unscreen the comment at will.

To make this work better, imported comments should be listed somewhere that the OpenID owner of the comments could find them and possibly mass-unprivatescreen/take ownership.

[Business]

These email templates will be sent out when we manage or fail to transfer a journal.

Title

Could not transfer your journal from SERVICE to your account USERNAME on Dreamwidth

Body

Hi, USERNAME--

We were unable to transfer your journal OTHERNAME from SERVICE to your account USERNAME on Dreamwidth. FAILURE MESSAGE.

We apologize for the problem and hope things can be resolved.

--Dreamwidth

• The username and password you gave us for SERVICE was rejected, so we couldn't download any information.
• SERVICE does not seem to be LiveJournal-based.
• SERVICE does not seem to exist. If you are sure the service exists pleae check the service URL you gave us and try again later.

Title

About your journal transfer from SERVICE to your account USERNAME on Dreamwidth

Body

Congratulations, USERNAME!

Your journal OTHERNAME on SERVICE has been transferred to your account USERNAME on Dreamwidth.

(OPTIONAL ISSUE/NOTIFICATION TEXT INSERTS: Things you might want to look at:)

HAPPY STATEMENT GOES HERE

-- Dreamwidth

• Because you have more icons on SERVICE than we can import, we have imported your default icon. You can choose which other icons you wish to import at URL.
• Unfortunately, SERVICE doesn't support icon importing. You will have to manually upload your icons from this service.

• Some entries couldn't be imported. You can view a list and the reasons at URL.
• We can't automatically transfer polls. You can view a list of entries with polls so you can manually recreate them at URL.
• We can't automatically transfer embedded content, such as YouTube videos. You can view a list of those entries containing embedded content and manual re-insert the item at URL.

• Unfortunately, SERVICE doesn't support comment importing, so we won't be able to import your comments.
• We're not sure why we weren't able to import a comment on POST, but it's missing and so we can't import it or any of its replies.

(these provided by <ljuser>cheyinka</ljuser>)

• www.somejournal.com WORKS
• http://www.somejournal.com WORKS
• username.somejournal.com WORKS
• http://username.somejournal.com WORKS
• somejournal.com WORKS
• somejournal can't work
• SJ can't work
• username (the ever-popular "didn't read the directions" option) can't work
• internet explorer / semagic / &c. (probably indistinguishable from 'username' as far as the code's concerned) can't work

From John:

• on somejournal can't work
• somejorunal or similar misspellings, though no idea how to fix that. can't work
• AOL (:D) can't work
• username at/on somejournal can't work
• [email protected] WORKS
• username at somejournal dot com WORKS
• SJ (where there are two services with the same initials. Perhaps not so much a consideration now, but in the event of super-federation Dreamwidth extreeeme, a possibility) can't work

From Janine:

• http://www.somejournal.com/users/username WORKS
• http://www.somejournal.com/~username WORKS
• http://users.somejournal.com/username WORKS
• A link to a particular entry in the journal, or really any other page within the journal WORKS

Output from test tool found here: http://linode2.andreanall.com/~anall/hidden/check_compat.txt

Works just fine.

          Cannocalize: OK (www.deadjournal.com)
      SessionGenerate: OK
              UserURL: OK ('''redacted''')
             Userpics: FAIL
               Groups: OK
                 Tags: OK
                  Bio: OK (downloaded)
            SyncItems: OK
            GetEvents: OK
          CommentMeta: FAIL
          CommentMeta: FAIL
 www.deadjournal.com Compatible: FAIL

DeadJournal appears to be rejecting my ljsession cookie for some reason.

Seems to be all OKs

All OK.

Category:Design specs