In the current Portfolio API implementation (as at time of writing, May 2009), we're missing support for any of the available Portfolio standards. The reason for this is that during the development phase of that project (mid 2008) there wasn't a clear front runner. As I understand it, the IMS Portfolio standard is not mature and very complicated and it would have been far out of the scope of the Portfolio API project to support IMS eP.
Jump to: navigation, search
Rationale![]()
LEAP is a cloud-based legal practice management software solution for law firms. LEAP has a comprehensive list of features including case management, legal time capture, trust accounting, legal billing, document automation/management, a client service portal, office reporting, and more.
However, the landscape has changed somewhat over the last year and LEAP2A has emerged as a very strong candidate. Mahara's upcoming 1.2 release will support importing from LEAP2A, as well as as well as other Portfolio vendors, and therefore it makes sense for Moodle to be able to export LEAP2A in order to be really useful. This doesn't mean that Moodle will never support any other Portfolio standard, it just means that it's a logical first choice.
A note on Moodle's current Portfolio export formats
At the present time, Moodle's Portfolio API exports Moodle content to a HTML respresentation. Files that have been uploaded into Moodle are kept in their native format. This is important as the 'fallback case', because HTML and files (eg PDF, etc) are supported everywhere, however, it is not actually necessarily the most useful end format to import into portfolio systems. For example, a forum post in Moodle will be exported to HTML, and become a HTML 'file' artefact in Mahara, which is essentially a non editable, rastered 'snapshot' of the content. It allows for much richer use, for a forum post in Moodle to (optionally) appear as a blog post artefact in Mahara, for example. In order to achieve this, we must export the forum post to some sort of common standard that Mahara can read. It is then up to Mahara to make decisions about what that content means inside Mahara. This takes away the impetus for Moodle to have to make decisions about what Moodle content becomes when it appears in a Portfolio application, and places it in the realm of the Portfolio application to decide (or ask the user). This is important because the same Moodle content might appear differently in different Portfolio applications.
Background to LEAP2A
LEAP2A is a simple ATOM Based standard that is well positioned as a low-barrier standard to combat some of the heavier standards out there. The basic premis is that every item is an entry, with some additional LEAP specific metadata. Content is not just defined by metadata, but also largely gains meaning based on its relation to other items.
LEAP2A is being championed by JISC in the UK and adopted by a number of Portfolio vendors.
Leap 3 5 2 – Comprehensive File Management Application Pdf
It is relatively simple to add LEAP2A support into Moodle.
What needs to happen in Moodle
What needs to happen in Mahara
Leap 3 5 2 – Comprehensive File Management Application DownloadSee also
Retrieved from 'https://docs.moodle.org/dev/index.php?title=LEAP2A_Portfolio_Implementation&oldid=14237'
Leap 3 5 2 – Comprehensive File Management Application FormNutanix AOS Software Licensing Models
Select a Nutanix AOS license model based on the needs of your organization. You can license by capacity, by appliance, or by specific use cases and workloads. All licensing models include product entitlements for AOS, AHV, and Prism.
Capacity-based licensing
Capacity-based licensing allows you to purchase and apply licenses based on the number of physical CPU cores and total SSD capacity in your cluster. You can purchase software separately from your hardware with a license that is portable across hardware platforms, giving you additional flexibility for budgeting and planning.
Appliance-based licensingLeap 3 5 2 – Comprehensive File Management Application Template
Appliance-based licensing is tied to the underlying hardware and the life of your device and is non-transferable. You can license Nutanix NX appliances or OEM appliances this way and benefit from a packaged single-purchase approach. Term-based licensing is only available for Pro and Ultimate upgrades on NX appliances.
Virtual Desktop Infrastructure Per User
The VDI per user model offers product entitlement for AOS, AHV, and Prism with pricing on a per concurrent user basis. VDI per user is an alternative to capacity-based and appliance licensing options and is designed to provide simple, transparent licensing for all VDI users, regardless of the underlying hardware.
Remote and Branch Office (ROBO) Per Virtual Machine
The ROBO per VM model combines AOS, AHV and Prism together with pricing on a per VM basis. This licensing model is an alternative to capacity-based and appliance licensing and is designed for sites running typically up to 10 VMs.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |