Difference between revisions of "Talk:Export wiki content"
(reasoning for workshop units vs. procedures supplied, then applied to example given) |
m |
||
| Line 1: | Line 1: | ||
| − | |||
| − | |||
Having had a good think about how workshops relate to procedures and best practices, and after a few chats with Aran about same, here is what I think about integrating the units: | Having had a good think about how workshops relate to procedures and best practices, and after a few chats with Aran about same, here is what I think about integrating the units: | ||
| − | The rationale is that the workshop links in with actual live procedures and best practices and is the way to implement them, that way we achieve reuse, and the workshop is how those things are implemented, say if we set up and organisational system for a client. Whether we change the css and/or make the units into individual pages is not so important, however the reuse and coherence, the way the workshops relate to the existing bp and procedures, are. The potential problem I see here is that we need to go create all these things (workshop learning units?) that aren't procedures, but "kind of are" procedures and result in a doubling up of content. | + | The rationale is that the workshop links in with actual live procedures and best practices and is the way to implement them, that way we achieve reuse, and the workshop is how those things are implemented, say if we set up and organisational system for a client. Whether we change the css and/or make the units into individual pages is not so important, however the reuse and coherence, the way the workshops relate to the existing bp and procedures, are. The potential problem I see here is that we need to go create all these things (workshop learning units?) that aren't procedures, but "kind of are" procedures and result in a doubling up of content.--[[User:Milan|Milan]] 00:57, 13 January 2009 (NZDT) |
This reasoning is described in further detail [[Workshop|here]] and [[Talk:Procedure#Procedures_and_Workshops|here]]. I suggest we develop our discussion on these pages, that way we can come to a shared understanding of what these things are and how they relate to each other. You can see that in doing the content for the workshop, we are having to get pretty clear on a whole range of definitions and how things relate to each other, which although it is hard work is still a pretty good outcome for future project work. | This reasoning is described in further detail [[Workshop|here]] and [[Talk:Procedure#Procedures_and_Workshops|here]]. I suggest we develop our discussion on these pages, that way we can come to a shared understanding of what these things are and how they relate to each other. You can see that in doing the content for the workshop, we are having to get pretty clear on a whole range of definitions and how things relate to each other, which although it is hard work is still a pretty good outcome for future project work. | ||
Revision as of 11:57, 12 January 2009
Having had a good think about how workshops relate to procedures and best practices, and after a few chats with Aran about same, here is what I think about integrating the units: The rationale is that the workshop links in with actual live procedures and best practices and is the way to implement them, that way we achieve reuse, and the workshop is how those things are implemented, say if we set up and organisational system for a client. Whether we change the css and/or make the units into individual pages is not so important, however the reuse and coherence, the way the workshops relate to the existing bp and procedures, are. The potential problem I see here is that we need to go create all these things (workshop learning units?) that aren't procedures, but "kind of are" procedures and result in a doubling up of content.--Milan 00:57, 13 January 2009 (NZDT)
This reasoning is described in further detail here and here. I suggest we develop our discussion on these pages, that way we can come to a shared understanding of what these things are and how they relate to each other. You can see that in doing the content for the workshop, we are having to get pretty clear on a whole range of definitions and how things relate to each other, which although it is hard work is still a pretty good outcome for future project work.
So if we apply the reasoning to the example provided, that gives us, in the body of the workshop article:
Contents
Unit 1: Export MediaWiki Pages
Objective
To learn how to export and import pages using MediaWiki by updating the training here on this wiki.
Example
- example goes here....(btw, I don't necessarily see the need for examples, but am open to being convinced otherwise...)--Milan 00:55, 13 January 2009 (NZDT)
- Link to procedure (open in tab!), which contains
Prerequisites
- Logged in as WikiSysop or user with Sysop status
Procedure
Download from source Wiki
- Go to http://www.organicdesign.co.nz/Special:Export
- The category we want to export is http://www.organicdesign.co.nz/Category:MediaWiki_Workshop
- Download the file and save it as Training.xml
- Download images (if any have been updated)
Upload to target Wiki
- Go to http://localhost/wiki/Special:Import (you must be logged in as a sysop)
- Browse to the file you download above
- Go ahead and import it
- Upload images (if any have been updated)
- Following the link to procedure comes this bit, although I can now see this is closely related to Cleanup/Finish off or Contingency plans respectively, which normally also form part of the procedure
Bonus Learning
- How does it know if it should overwrite a file or not (time date stamp)
- How can you change that (edit xml file, search and replace, then upload)
