[JoPP-Public] New tips on uploading

Thu May 22 17:26:09 CEST 2014

From: Mathieu ONeil <mathieu.oneil at anu.edu.au>
Subject: [JoPP-Public] New tips on uploading (was: RE: request for staging area and report on progress)
Date: Thu, 22 May 2014 13:47:01 +0000

> Hi Maxigas
> 
> As admin you can create an account for Peter - go to accounts
> and it is very easy.

Good point.

> I don't know from staging websites and I can't help with that
> right now. I don't know if its a good idea or not. Currently
> you can choose to leave all your pages private - when you are
> ready you change the setting to public - is that not suitable,
> might be simpler. If you have the skills and no-one objects,
> you can set one up yourself. Then almost magically and by
> default you will have become (if only temporarily) our
> webmaster. ;-) So, there is no contact person. The P2P
> foundation helps if we have server issues but not with site
> questions. If anyone out there would like to help please make
> yourself known.

OK so basically what you say is that we have to liaise with the
P2P foundation about infrastructure issues. We will try to do
this and report on developments here.

> As a peace offering here are some pretty impressive notes Nate
> wrote after completing the recent issue on value. I (why always
> me?) was supposed to merge them in with the existing advice
> page but I didn't, so here they are for everyone's benefit
> until they go up.

Thanks for the documenation, I really appreciate it! It makes it
easier to understand the custom functions in the jopp theme and
how to put together an issue. I will merge it into the advice
page when I get the time to focus on webdev stuff.

> cheers
> 
> Mathieu
> 
> 
> ===----===---===---===----===---===---
> 
> Notes on the JoPP upload process
> 
> 
> Issue Structure
> 
> After you gain access to the back end of JoPP, the first thing you should do is have a look at the previous issues. Specifically, go to the 'pages' section of the dashboard, where all the pages from the previoius issues are located.
> 
> The important thing to pay attention to is the fact that every issue has its own hierarchical relationship between its pages. You need to replicate this hierarchy for your own issue. See issue zero for example: The home page for this issue (— Issue #0: Mass Peer Activism) is situated hierarchically underneath the 'Issues' page (the 'Issues' page is the 'parent'). The hyphens (e.g.: - - -) at the beginning of a page title indicate how far down it is in the journal issue hierachy. So, the '— Issue #0: Mass Peer Activism' page is the parent of 'Editorial Notes' and 'Peer reviewed papers'. The '— — — The Origins and Impacts of Swedish Filesharing: A Case Study' page is the parent of three pages: 'Original Submission', 'Reviews' and 'Signals'. The reason that getting this structure right is important is because some of the issue content is generated automatically, based on the relationship between the pages.  You might even want to create the entire issue page structure before uploading any actual text (just leaving the pages blank).
> 
> When creating a new page ('add new'), you need to do three main things to make sure the 'hierarchy' is created. One, on the right hand side bar, under 'page attributes' you will see the 'parent' drop down box. Make sure you choose the corrent 'parent' for the current page you are creating. If in doubt, look at the previous issues. Second, besides one exception, every page you create will use the 'template' called 'page – full width'. The one exception is the 'peer reviewed papers' page, which will use the template called 'peer reviewed paper'. This is a special template the will drag content (metadata) from other pages and turn that data into an automated page. (You will never see any content for this page in the back end). Thirdly, once you have figured out the order of your articles for the issue, make sure this order is reflected in the 'order'  page attribute option (e.g. 1, 2, 3 etc.). As far as I can tell, this will determine the order of articles in the 'peer reviewed paper' page. For example, if you have a lead article, it will be numbered '1'.
> 
> Main Issue Page:
> make sure this page follows the style of the others. A good idea is to cut and paste the html from a previous issue main page and then change the content and the links. When doing this, though, it's always better to work with in the 'text' view of the page editor, rather than the 'visual' view. That way, you can see what the code is doing if needed.
> 
> Editorial Notes / Issue Introduction
> It's parent should be the issue main page (e.g. Issue #4 Currency and Value).
> 
> Invited Comments
> as these are not 'reviewed', they do not connect to the 'peer review papers' page.
> The 'invited comments' parent should be the issue main page (e.g. Issue #4 Currency and Value) and then the actual invited comments (i.e. the pages with the content) should have the 'invited comments' page as the parent.
> 
> Peer Review Papers page:
> the template for this page should be 'peer reviewed paper'.
> It's parent should be the main page for your issue (e.g. Issue #4 Currency and Value).
> No content is required for this page as it is all automatically generated from the 'custom fields' of the article pages (more on this below).
> 
> Article Pages:
> these are the pages that have the actual article content.
> Their parent page will be the 'peer reviewed paper' page
> their template will be 'page – full width'.
> When uploading the content, keep it as simple as possible. It's a good idea to work with plain text, rather than copy and pasting text from a more complicated word processor (e.g. Ms Work, Open Office etc.) as text from .docx or .odt files can have hidden code attached. 
> It's also a good idea to copy and paste your content using the 'text' view, so you can see what kind of formatting tags are present.
> Make sure you use the same styles/tags as previous issues. Again, keep it simple. The general heading tag is [h2] for example, and this should be used for all major headings.
> 
> Signal Pages, Review Pages and Original Submission Pages:
> for all of these pages, copy the text from the 'text' view of a previous issue of all of these pages and then alter the content as needed.
> The parent of all of these page will be the 'article page' that they refer to.
> For the 'orginal submission' page, you will need to upload the author's original submission. First, convert it to a pdf. Then, from the 'edit page' screen, click on 'add media' and then upload the content. A link shoul appear in the text box that looks like this: <a href="http://peerproduction.net/wp-content/uploads/2012/07/CSPP_Original-draft-Andersson-11.pdf">PDF: Original draft - Andersson</a>
> 
> Images:
> if you have images to upload, you should do this in the 'media' section on the left navigation bar.
> The images from this article are a good guide: http://peerproduction.net/issues/issue-4-value-and-currency/peer-reviewed-articles/the-politics-of-cryptography-bitcoin-and-the-ordering-machines/
> one thing to pay attention to is the image title box, which appears automatically underneath an image by using the title=“image title” attribute within the image tag. 
> 
> Custom Fields:
> these are crucial for the proper functioning of the 'peer review articles' page, but you 'add them' to the article pages.
> If you cannot see the 'custom fields' option beneath the regular text editing box in the edit page screen, click on the 'screen options' button on the top right of the page and tick the 'custom fields' box. There should now appear a custom field section below the text editing box (at the bottom of the page).
> You will need to add several different custom fields: paper-abstract, paper author, paper keywords, paper-signal, paper title, and so on. This information is what is fed into and effectively generates the 'peer reviewed papers' page. To be clear, the 'peer review papers page will not show any content until you have added info into the custom fields.
> 
> PDF versions:
> these are generated automatically from the html versions of all peer reviewed articles.
> If the pdf is only generating the meta-data (content from the custom fields) and not the actual article content, it could be because there is some code in the article page that the pdf converter doesn't like. One known such code is “&nbsp;”. Articles with this code cannot be converted, so do not include it in the html of your article pages.
> Another known issue with the pdf converter is that it pushes images that appear at the top-right of a  page over to the right and off the page. If this happens to you, try to adjust the spacing of the html version of the article page. For one image, I included a full stop on a separate line, in order to push the image down from the very top-right of the pdf. This is not an ideal tactic!
> 
> Links:
> once the issue is finished, make sure all the links go where they should. Sometimes if you are reusing code from old issues, you can forget to update all the links to the new issue.
> If a link should be going to one page (and you know that the pages does exist), but the link isn't working, check that the link address and the page URL are actually the same. The 'peer reviewed papers' page, for example, can automatically generate links that might be slightly different to the actual page URLs. It is possible to change the page URLs in the 'page edit' screen, under the page heading, where it says 'permalink' and 'edit'. Make sure if you change these that anything linking to this page is also updated.
> 
> ===----===---===---===----===---===---
> 
> ________________________________________
> From: jopp-public-bounces at lists.ourproject.org <jopp-public-bounces at lists.ourproject.org> on behalf of maxigas <maxigas at anargeek.net>
> Sent: Thursday, May 22, 2014 23:15
> To: jopp-public at lists.ourproject.org
> Subject: [JoPP-Public] request for staging area and report on progress
> 
> hello joppers,
> 
> we had a meeting yesterday about the upcoming special issue on
> shared machine shops.
> 
> we are a bit behind schedule and as you know we have a hard
> deadline because we want to release the issue in time with fab10
> [0]. the plan is to produce a hardcopy version of the journal and
> have a little release event during that gathering. we are
> currently looking for organisations to pay for the costs.
> 
> **meanwhile, we need some technical help in order to smooth the
> production process of the electronic journal.**
> 
> we started to think about how to get the articles onto the
> website and we arrived to the conclusion that we need a "staging"
> website, which looks like the original one but it is not public,
> so we can make mistakes and see how the release would look like
> before migrating the content to the production site. this is
> quite common practice in web development.
> 
> therefore, the question is if somebody could set up a clone of
> the current website for us, or at least provide us with the
> hosting account details, the codebase and the database of the
> current website. if somebody could do it for us it would be
> supercool because we are short on time. but if not, we can also
> do it ourselves provided that we get the resources mentioned
> above.
> 
> of course a staging website would be a contribution to the
> existing jopp infrastructure and it could be used by future
> editors to make a more smooth update when they are working on a
> new issue.
> 
> we thought about the update process like this:
> 
> * we plan to make the updates on the staging site
> * then ask for a backup of the live site to be made
> * then copy/paste the new entries to the live site
> + here have tech stand-by if roll-back needed!!!
> * then check the results and if not good revert
> * eventually, be happy
> 
> the timeline for this would look like this:
> 
> * late May: get codebase, database, hosting details
> * early June: install and configure staging site
> * June 20th: staging site content upload starts
> * June 27th: migrating content to live site
> * July 2nd or in the worst case July 4th: release!!!
> 
> is there somebody in particular we should be communicating with
> about this?
> 
> finally, we would of course need accounts on the website. i
> already have one and it works (thanks!), but my co-editor peter
> troxler would also need one. his email is trox at fabfolk.com
> 
> thanks for your consideration,
> 
> your editors.
> 
> [0] http://fab10.org/
> 
> --
> maxigas, kiberpunk
> FA00 8129 13E9 2617 C614 0901 7879 63BC 287E D166
> http://research.metatron.ai/
> 
> People the switches!
> 
> 
> 
> 
> 
> 
> _______________________________________________
> JoPP-Public mailing list
> JoPP-Public at lists.ourproject.org
> https://lists.ourproject.org/cgi-bin/mailman/listinfo/jopp-public
> _______________________________________________
> JoPP-Public mailing list
> JoPP-Public at lists.ourproject.org
> https://lists.ourproject.org/cgi-bin/mailman/listinfo/jopp-public
--
maxigas, kiberpunk
FA00 8129 13E9 2617 C614 0901 7879 63BC 287E D166
http://research.metatron.ai/

People the switches!