I noticed that creating the layout galleys is not a job for a common user. And it seems that for someone unfamiliar with OJS will have terrible issues when uploading the images for an article, because of the addressing.
This brings a question I´ve sent to Kevin and John about the whole archiving of OJS. It seems to me a bit easier for maintenance and coding (not sure how easy it is to create directories..) to have a folder for each issue, with separate folders for each article, with an image folder in it... something like:
- Code: Select all
I realise that the current structure protects the content, so there are references to the articles and images. However, in the HTML code, the editor needs to change the HTML code of image tags to something like:
Having a structured file system like the one suggested could allow to separate the Administration area from the Visualization/Reader area, which in turn allows for one Administration to control multiple journals, in different servers altogether.