I trust the PKP team will provide a more thorough point of view on this matter.
From my experience working with PKP, and the evolution proposed for the project, I believe that OJS will continue to be used specifically for journals, although creativity is your limit as to what OxS can do for you. I see a myriad of possibilities, for example, using it to manage projects, but there are always shortcomings due to the need to customize the translation and the process being very specific to blind peer-review.
This being said, since the coming of the PKP Web Application Library, where I trust the idea is to modularize all the functionalities, eventually anyone could develop an application using functionalities from OCS, OJS, OMP, OHS, for example, a custom Timeline for harvesting a collection of documents from similar institutions, creating a mashup and providing a full-text search on the documents, for use by Financial Agencies, for example.
In my opinion, there are a few of issues to discuss here:
- How distant are these "creative" applications from the purpose and objectives of PKP? Hard to tell.
- How much can PKP do without help from the community? Also very difficult to tell. However, we are discussing a stronger development and technology/knowledge transfer policy between PKP and IBICT, to be able to assist PKP in many fronts. Hopefully, more institutions will view this as an option when adopting PKP software.
- How many people would be interested in how many new apps or functionalities? Without specific research on user and community needs, it's hard to decide on what road to take.
- Regarding you specific list of features, these seem to fit more with Open Harvester Systems - OHS, although all of PKP Suite software is basically a repository.