Standardize 'Document page' terminology

True the naming conventions are not very consistent for this content type and the associated view.

The section pages are really just different displays for content, so the 'News' section displays section content in a news-style list. However the fact that section pages are tied to the kinds of content they allow you to create does imply that the naming should be consistent. As we can see from the content type list, the oa_wiki_page is the machine name for the Document Page - so these are the same thing.

So the 'News section' allows you to create 'Document Page's (which has a machine name of oa_wiki_page).

I'm changing this to a feature request to standardize the terminology. I'm not sure that 'Document page' is the clearest name for this content type. I would vote for 'Article' (oa_article) consistently throughout.

I'm pretty sure the "oa_wiki_page" - "Document" difference was due to the changed name of the Content Type in a later stage of development, but if I'm not mistaken the News-section added to it has been on purpose to illustrate Sections can contain different kinds of content. Correct me if I'm wrong.

Thankfully due to the flexibility of Open Atrium (and Drupal of course) it is very easy to create your own Content types and Sections along with it. This makes the naming discussion rather trivial.

Yeah, I think Argus is right about the history of this.

IMO changing the machine name of a content type is probably not going to work. Lots ond lots of modules store content type names in their own variables and tables, and changing it will break all of them which we don't specifically code upgrades for.

I personally like "Document page" as a content type name. But, I agree that having only "News section" as a default is totally confusing. On many of my OA2 sites, I have a "Knowledge section" which is meant to hold "Document pages" with structured content (like the "Notebook" feature in OA1).

We plan to add a "Files Section" in the future that will show Document Pages as a simple file-list listing.

But Argus and David are correct. The Section is named for how the content is displayed. For example, it's called a "Calendar Section" and NOT "Events Section" because it displays events in a Calendar view. So a News Section displays content in a "News-like" view. "Knowledge Section" might be a good better name.

It might be confusing initially, but it's also done on purpose to help teach people the important difference between a Section and a Content Type.

(and yes, Document pages were initially called Wiki which is why the module is oa_wiki. But we got a lot of feedback against calling it Wiki and people liked Document page better. But changing the core module machine name caused too much backwards compatibility issues).

I must agree with the OP that things get confusing, when I create a News Section, the create content button says "Create Document Page"... Huh? I want to create News!

To add to that, I think a "Files Section" isn't going to cut it. Files are images, PDF-documents, Word-documents, Excel-documents etc etc. This kind of section is indeed very much needed, but not as a representative of a standard node within Open Atrium.

Let's chew on this a bit more.

Having a file section as nodes is intentional to associate meta-data with the file. But Drupal has no native way of doing true file revision management. If a node has an attached file and you want to create a revision, then you have to attach the revised file to the new node revision manually.

A more robust option would be to integrate Alfresco but at the moment the CMIS connector lacks single sign-on capability so there's only one Alfresco account hard-wired in. The Canopy initiative has just released a D7 dev version but CMIS hasn't gotten any love in 8 months.

Canopy is a different beast than CMIS however. Alfresco itself is written in Java and requires a Tomcat server.

You could just have a dumb file browser widget - there are a number of modules that provide that functionality like File Depot though I don't think any of them are sophisticated enough to support fine grained access control which is important. I believe File Depot has some rudimentary version control.

Then there's the Git module but I have no experience with that.

The Alfresco solution would be true to OA's "best in class" mantra but it's tricky to set up and has a learning curve of its own. I used a Bitnami Ubuntu/Alfresco image in Virtualbox to make it easier to test the connector.

This subject deserves its own issue thread.

Document Management improvements were added to v2.30.

Actually the OP was about something else: the out of the box experience for novice OA administrators who get confused by the "document - news - wiki" names. But that matter was also answered in the thread.

Just as a small point - probably easy to do somehow.

OK - so the original name was oa_wiki, the content is documents, the Section Type is News. The name 'News' name is confusing for our users.

So, how can I change the section type name from News to Documents? So when the users go to add a new section they can pick to add a 'Documents' section and not a 'News' section?

Thanks.

And as another small point - is it really possible (desirable) to add different things into sections - i.e. add a task into a News section?