Syndicate User loginNavigationWho's new
|
Application Architecture
About the IoCP
Usual static information about the Institute: overview, history, executive, contact us etc
Administration
Drupal Administrator menu plus links to all the external admin functions
Advertising
Management of advertising: contracts, periods, placement
Display of advertising: banners, logos, classifieds, links… Banner module
Special advertising: Google Adsense
Approval
A subset of members (the content committee) can approve content for publication.
Node text for the Document is to be formatted to a standard, and copybook headers and footers applied, some to the doc once, some to every page (e.g. Copyleft, credits…).
They may then just give it an OID and link it up via the taxonomy, or they may need to edit it, or copy it into other content.
There should then be some notification to the original contributor.
Declined content is referred back to the original contributor, or a working group (and project) is formed to develop it to the required state.
CoPr content
Content is stored as nodes in Drupal. There is one node for each guidance or other Document (in the RADIX 0.12 sense of “Document”). Nodes are “indexed’ by Taxonomy, and the navigation between then generated from Taxonomy.
CoreCT information
Training and certification info is stored as Pages.
Scheduled courses are managed in Event.
Credit
Users are registered users of the website, members are paying members of the IoCP.
Users (or only members?) accumulate credit for
Contributions
Mentoring
Committee membership
Attending events
Comments and votes
Database
Database Adminstrator
Download
The node is turned into a file (HTML, rtf, ODT…?) and downloaded to the client
Events
Scheduled events are stored and displayed: conferences, seminars, training…
Financial
Financial data from the merchant gateway is exported as .csv for use by the IoCP Financial System.
Security of the transmission and storage of this data needs careful consideration
Formatting
Standard template(s) for text format, header and footer copybooks (eg Copyleft, credits, about the IoCP etc) are stored and administered.
They are applied as part of the Approval process. Optimally, the templates and copybooks should be just that, and not be stored in every node as embedded text. Use HTML Cascading Style Sheets? PHP snippets?
We thought about applying them only on Download or print and not having them in the node, but there are too many ways to copy and print the text in an uncontrolled manner, so they need to be in there before the text is displayed in any way.
Forums
Uses Forum module.
Forums for the conducting of IoCP business, not social or networking – leave that to the third party operators.
Some are closed forums.
Forums:
Free support: Advice and help with using CoPr
Ideas, feedback, experiences with CoPr
News and activity around CoPr
Discussion of changes and additions to CoPr, submitted or just ideas
IoCP committees (closed)
Front Page
Use the Front_Page module or use custom PHP in a node?
The front page should have
Easy “dummy-level” access to About the IoCP, CoPr content, CoreCT information, and links
Banner advertising and sponsor logos
Instructions on how to navigate the site and what is in there
Menus
Member logon
Gateway
We will use an external commercial payments gateway(s) to provide payment by
Visa, Mastercard
Amex
PayPal
Outsourcing this function removes many security and confidentiality issues
Identity
The identity component provides authorised administration of as many aspects of identity as possible; LDAP, database, Drupal profile…
Legal
T&C at logon
Privacy policy
Disclaimer
Copyright notices on website and on downloads
Links
Registered links to third party providers, for which they will presumably pay a fee.
The links can be referred to in CoPr content and other places about the website, as well as in a Links list
Load
The ability to bulk-load CoPr content and taxonomy, for example if a separate organisation submits an entire new CoPr Group model and content.
An interface format will need to be defined.
Not an early priority in the project.
Mailing
Creation and management of mailing lists
Members
Users are registered users of the website, members are paying members of the IoCP.
Membership application and processing
Mentors
Assessment of mentors (scoring points based on their qualifications, experience, online activity and feedback from other members perhaps?)
Granting of mentor role.
Assigning mentors to users who ask for it.
Partners
Management of associated organisations
Sponsors
Advertisers
Affiliates
Vendors and service providers
Payments
Catalog of fees, products and services
Shopping cart
Link to payments gateway
Print
See Download.
Can we apply the same formatting process to a node then send it to the client’s printer? Or do they need to download then print? And if we can’t print direct, can we prevent printing of the node without the formatting (Copyleft statements etc)?
Projects
Management of Institute projects, especially development and major enhancement of CoPr content, e.g.
Proposals for new Groups
Development of new practice sets
New versions
Establishing new regional chapter
Conference
Training and certificationRecognition
Recording qualifications and credits for members and partners
Professional certification after training
Acknowledging experience and peer references
Content contribution credit
Certification of vendor products and services
Certification of implementation compliance assessment
Registration
Signing up for
Institute events e.g. conferences, seminars
Partner events, e.g. training courses
(as distinct from user registration to the website)
Review
Interactive assessment of proposed CoPr content by users and by committees: comments, voting, polling on key issues
Acts as input to approval process.
Submission
Users (or committees) input proposed amendments or additions to CoPr.
Submissions are linked to the related content node(s) that they replace or extend.
Input is in a standard format, probably HTML. Drupal filters are provided to allow a range of input formats and editors to be converted to HTML. Input is direct on-screen, by cut and paste or typing in. Batch submission is not in general accepted, except for large contributions typically copied from an existing body of work.
Submissions are queued for approval and displayed to the user community for review.
Taxonomy
The capabilities of Drupal taxonomy are not fully understood yet, but initial plans are:
Taxonomy is used to manage the CoPr OID naming taxonomy (1.n.n). Guidance and other documents are nodes related to the taxonomy entry.
Menus and links in the guidance are generated from the taxonomy.
A parallel conceptual taxonomy provides keyword indexing and searching into CoPr.
Unload
Batch unloading of CoPr content and related taxonomy, used
For offsite backup by IoCp
To provide a full set of CoPr to partners (presumably for a fee)
Users
Users are registered users of the website, members are paying members of the IoCP.
Administration of user profiles, granting rights to users, deletion, and user self-administration of profile.
Volunteers
Advertising of "jobs",
Recording who is doing what, links to credit (thanks) and recognition (experience).
|
Known errorsCOPR HAS UNDERGONE A ROUGH UPGRADE: please be patient with us as we restore normal function. Basic stuff will be restored soon but it could be most of 2009 before we are fully rebuilt with a new improved CoPr. Suggestions are welcomed on reshaping CoPr.
To get your own copy of CoPr you use the FastPath menu or "download CoPr" on the Navigate>>Mindmap menu or click here
Who's online
There are currently 0 users and 9 guests online.
|
Click for an example, hover for a definition
Made in New Zealand 
