OJS OCS OMP OHS

You are viewing the PKP Support Forum | PKP Home Wiki



OJS File Structure

Are you an Editor, Author, or Journal Manager in need of help? Want to talk to us about workflow issues? This is your forum.

Moderators: jmacgreg, michael, vgabler, John

Forum rules
This forum is meant for general questions about the usability of OJS from an everyday user's perspective: journal managers, authors, and editors are welcome to post questions here, as are librarians and other support staff. We welcome general questions about the role of OJS and how the workflow works, as well as specific function- or user-related questions.

What to do if you have general, workflow or usability questions about OJS:

1. Read the documentation. We've written documentation to cover from OJS basics to system administration and code development, and we encourage you to read it.

2. take a look at the tutorials. We will continue to add tutorials covering OJS basics as time goes on.

3. Post a question. Questions are always welcome here, but if it's a technical question you should probably post to the OJS Technical Support subforum; if you have a development question, try the OJS Development subforum.

OJS File Structure

Postby ramon » Wed Mar 24, 2004 6:22 am

Fellows,
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
issue>article>images


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:
images/articleimages/+ojsarticlename+ojsimagename


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.

Just wondering... :D
ramon
 
Posts: 926
Joined: Wed Oct 15, 2003 6:15 am
Location: Brasí­lia/DF - Brasil

Postby kevin » Wed Mar 24, 2004 9:57 am

This component has not been developed yet, but are plans do include a filesystem layout similar to the one you've suggested.
kevin
 
Posts: 338
Joined: Tue Oct 14, 2003 8:23 pm

Postby mj » Fri Mar 26, 2004 11:20 am

I think the natural structure, from what we've been doing on JMIR, would be something like: /volume/issue/article/

This would allow galleys and similar files to be stored on a per-article basis, within the same directory. While having sub-levels (like an /images subfolder) is helpful for things like a webserver, it also adds a level of complexity - which I think should be optional, at most. (eg. does one use /images, /img, /app, /supp, etc?)

Because JMIR does HTML rendering from XML, we store files in a /volume/article/ structure, with the .xml file and all images, appendices, etc. in the /article folder. With a standardized filenaming convention (and extension), it's easy to know what files are where.

Another alternative would be to store files in the database as BLOBs, but I think that's probably fairly heavy for something like OJS, especially if multiple journals are being hosted on the same database.

M
mj
Site Admin
 
Posts: 304
Joined: Fri Mar 26, 2004 9:32 am
Location: Toronto, Canada

Postby kevin » Sun Mar 28, 2004 1:26 pm

Current plan is for the file layout to be like files/<journal_id>/<article_id>/[submission | review | public] where submission, review, and public directories contain the original submission files, review/editing versions, and final published files.

Unless files are to be shuffled around upon publication, we can't really use the volume or issue, as those values are not known until the article is actually assigned to an issue.
kevin
 
Posts: 338
Joined: Tue Oct 14, 2003 8:23 pm


Return to OJS Editorial Support and Discussion

Who is online

Users browsing this forum: No registered users and 2 guests