SAP Learning Solution RKT ERP 2005 LSO 6.00

Size: px

Start display at page:

Download "SAP Learning Solution RKT ERP 2005 LSO 6.00"

Matthew Morton
5 years ago
Views:

1 SAP Learning Solution RKT ERP 2005 LSO 6.00 Authoring Environment SAP AG 2005 SAP AG 1

2 SAP Learning Solution Authoring Environment Metadata management and search Set content to obsolete Repository Explorer functionality Versioning Further functionalities SAP AG 2

3 Metadata Maintenance and Search - Overview In order to leverage the reuse of learning objects, authors may now perform a structured search along metadata to find appropriate learning objects: Consistent metadata maintenance defining in customizing own metadata fields setting metadata fields to mandatory/optional maintain these metadata fields in Authoring Environment supporting existing standards (e.g. LOM, Dublin Core) Powerful metadata search metadata should be indexed and made available for search automatically search using TREX technology Metadata settings take place as customizing in the back end and are taken over to the authoring environment the next time when the repository explorer or the authoring environment is online. The metadata settings will then be used within the authoring environment on learning net or learning object level. The search is started within the authoring environment. SAP AG 3

Metadata Maintenance Authors can use the TREX search engine to find objects stored in the master repository. It is important that a index is generated over the documents.

A mandatory metadata field leads if not maintained to error messages in the authoring environment and content will be prevented from check in.

4 Metadata Maintenance Authors can use the TREX search engine to find objects stored in the master repository. It is important that a index is generated over the documents. In the Back End System the customizing for meta data takes place. The supported metadata receives a metadata ID and can be marked as mandatory or optional. A mandatory metadata field leads if not maintained to error messages in the authoring environment and content will be prevented from check in. XSL (Extensible Stylesheet Language) is a programming language used to convert XML (Extensible Markup Language) documents to any other XML format (XSL transformation). When you import an external course, you can convert external metadata that has an XML format (such as LOM or Dublin Score Schema) using XSL Transformation to the XML format used in the Learning Solution so that the metadata can be transferred to the LSO system. SAP AG 4

Metadata Maintenance Metadata maintenance takes place in the

To maintain metadata a new icon is introduced in the icon bar,

If mandatory fields are not maintained errors appear in the

5 Metadata Maintenance Metadata maintenance takes place in the authoring environment on learning net or learning object level. To maintain metadata a new icon is introduced in the icon bar, which opens a new popup for the required attributes. If mandatory fields are not maintained errors appear in the message area. Clicking on these messages will also open the metadata maintenance popup. SAP AG 5

Metadata Search 2 Define fields 1 Start search dialog The

Learning Objective Search also a fulltext search over the

6 Metadata Search 2 Define fields 1 Start search dialog The search function within the repository explorer has been enhanced. Now the popup offers next to the where-used list and the Learning Objective Search also a fulltext search over the metadata. The metadata search offers a query to select from mandatory and optional fields (the ones that are defined in customizing). SAP AG 6

be filtered by status, object type and languages.

7 Metadata Search 3 Start search 4 Flag objects in Master Repositority and close dialog The search can be filtered by status, object type and languages. The results of the search can be selected and applied. SAP AG 7

8 SAP Learning Solution Authoring Environment Metadata management and search Set content to obsolete Repository Explorer functionality Versioning Further functionalities SAP AG 8

the content is no longer available - when assigning the content to courses, the obsolete courses are no

9 Process for Managing Outdated Content Mark as Obsolete In order to manage outdated content, authors can mark content as obsolete: Existing courses remain untouched - existing bookings are not affected For new courses, the content is no longer available - when assigning the content to courses, the obsolete courses are no longer visible for the course administrator in the publisher s database No physical deletion of content SAP AG 9

Process for Managing Outdated Content Mark as Valid

obsolete content as valid within the standalone

Important: Set the filtered view to All Objects

10 Process for Managing Outdated Content Mark as Valid In order to manage outdated content, authors can mark obsolete content as valid within the standalone Repository Explorer. Important: Set the filtered view to All Objects (Including Dependencies) and the validity to All objects (Including obsolete versions). SAP AG 10

11 SAP Learning Solution Authoring Environment Metadata management and search Set content to obsolete Repository Explorer functionality Versioning Further functionalities SAP AG 11

12 Import Content with Repository Explorer Mark as new version Check in of reusable objects is now possible directly with the Repository Explorer. The process itself stays the same as the importing process over tools menu. If it is a new version of already published content, then there is even the possibility to mark this content as a new version. SAP AG 12

Import & Convert SCORM Courses with Repository Explorer - I If

Repository Explorer is combined with conversion and the check

Following steps have to be proceed: The SCORM course has to be

Import Wizard detects itself that the resource is a SCORM

13 Import & Convert SCORM Courses with Repository Explorer - I If the content is an external learning net then importing via Repository Explorer is combined with conversion and the check in to master repository may follow directly. Following steps have to be proceed: The SCORM course has to be detected on the local server to be imported into the local repository. After the files are verified and the import is prepared, the Import Wizard detects itself that the resource is a SCORM course and the process can be continued. The SCORM anchor file is either detected by the Import Wizard itself or has to be selected. SAP AG 13

Import & Convert SCORM Courses with Repository Explorer - II 4.

the learning net has to be selected or verified. 5.

these files will pop up and can be assigned accordingly. 6.

the conversion and import to the local repository can be finished.

14 Import & Convert SCORM Courses with Repository Explorer - II 4. The conversion process has to be started and the anchor file for the learning net has to be selected or verified. 5. If the imported SCORM course is accompanied by metadata file than these files will pop up and can be assigned accordingly. 6. Finally the SCORM course will receive a name as a learning net and the conversion and import to the local repository can be finished. If desired, the check in to the master repository may follow directly from the same tool. SAP AG 14

Check in to Master Repository To fasten up the procedure tick Release objects after check in and Publish learning nets after

First of all, authors don t have to select the concerned course again and again to proceed in the publishing process, the

Then authors can determine how the check in should proceed, i.e. the author should tick the relevant boxes in the check in

However if there are any mandatory fields not maintained yet, then the check in procedure will stop and require to finish the

15 Check in to Master Repository To fasten up the procedure tick Release objects after check in and Publish learning nets after release Check of mandatory fields Check in to Master Repository can be carried out in a faster way. First of all, authors don t have to select the concerned course again and again to proceed in the publishing process, the next step is always offered at the end of the predecessed process step. Then authors can determine how the check in should proceed, i.e. the author should tick the relevant boxes in the check in dialog, to get as few interruptions as possible by info messages that have to be confirmed. However if there are any mandatory fields not maintained yet, then the check in procedure will stop and require to finish the maintenance before continuing with check in, and still some control stops will take place. If authors want to check in many and/or large contents then the batch check in with the standalone repository explorer should be the choice. SAP AG 15

Batch Jobs in Standalone Repository Explorer I Within the standalone Repository Explorer batch jobs can be used to check in larger content or different courses parallel.

16 Batch Jobs in Standalone Repository Explorer I Within the standalone Repository Explorer batch jobs can be used to check in larger content or different courses parallel. Once a course is in the check in phase the wizard asks either for a step by step (just the next button) approach or for a batch job. When the batch job option is chosen, then this job appears in the Batch Job Manager and waits for further input such as the processing options and consistency checks. SAP AG 16

Batch Jobs in Standalone Repository Explorer II Displayed after finished

if necessary it appears to ask for further information according to the

When the job is finished the Batch Job Manager shows the new status.

17 Batch Jobs in Standalone Repository Explorer II Displayed after finished Processing options From then on the job works in the background and only if necessary it appears to ask for further information according to the processing options chosen. When the job is finished the Batch Job Manager shows the new status. Only jobs that finished without errors are really checked in. Jobs of any status can be removed from the Batch Job Manager. SAP AG 17

18 SAP Learning Solution Authoring Environment Metadata management and search Set content to obsolete Repository Explorer functionality Versioning Further functionalities SAP AG 18

Customizing Versioning and Reactions in Frontend Administrators define in Training Management

method (manually or automatically) Progress handling (keep learning progress or delete learning

should with minor or major content changes or with new legal requirements in regard to content.

19 Customizing Versioning and Reactions in Frontend Administrators define in Training Management change categories for new versions, where they can apply the following attributes: Booking update method (manually or automatically) Progress handling (keep learning progress or delete learning progress) Price policy (free of charge or with fees) These change categories enable to define how should with minor or major content changes or with new legal requirements in regard to content. Authors can assign these change categories when they publish a course to the master repository. SAP AG 19

categories and Authors can assign these change categories when they publish a course.

20 Customizing Versioning and Reactions in Frontend automatic update according to customizing settings that were applied to the content while publishing Training Administrators can define change categories and Authors can assign these change categories when they publish a course. These categories determine how a learner should be informed on major or minor content changes and act on them. SAP AG 20

21 Versioning 3 Examples of Reactions Different change categories lead to different action request in the learning portal. SAP AG 21

22 SAP Learning Solution Authoring Environment Metadata management and search Set content to obsolete Check In functionality Versioning Further functionalities SAP AG 22

23 Further Functionalities Regarding Authoring and Training Management Templates & Publishing Confirmation Template storage in backend Customizing of publishing confirmation in backend Standard templates for instructional elements, learning objects, and learning nets can now be stored globally. If these templates are updated, the corresponding files in the Authoring Environment can be synchronized accordingly. The network or directory address entered in this customizing point is required for this reason. Further it can be customized whether a reason is required when content is published in the Repository Explorer of the Authoring Environment. Blank means that no reason needs to be specified. 1 means that a reason must be specified. 2 means it is required only for the purpose of downward compatibility. SAP AG 23

Further Functionalities Regarding Authoring and Training Management Valid Strategies while Publishing Authors can use the customized learning strategies

24 Further Functionalities Regarding Authoring and Training Management Valid Strategies while Publishing Authors can use the customized learning strategies from the back end to assign the valid ones directly to a course while the course is published. So the learner can only choose from the assigned ones. SAP AG 24

Further Functionalities Regarding Authoring and Training Management Error Messages in Check In Wizard Check-In Wizard will report errors on not

25 Further Functionalities Regarding Authoring and Training Management Error Messages in Check In Wizard Check-In Wizard will report errors on not maintained mandatory metadata fields. These fields can be maintained still in the Check-In Wizard so that the process doesn t have to be interrupted. SAP AG 25

26 Copyright 2006 SAP AG. All Rights Reserved No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iseries, pseries, xseries, zseries, z/os, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mysap, mysap.com, xapps, xapp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence. The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages. SAP AG 26

The test has been performed using a 64 Bit SAP NetWeaver Application Server Java 7.1 Enhancement Package 1 SP4 or greater system.

The test has been performed using a 64 Bit SAP NetWeaver Application Server Java 7.1 Enhancement Package 1 SP4 or greater system. SAP AG hereby confirms that the interface software for the product of the company has been