What is the translation of " SINGLE SCO " in Danish?

• enkelt SCO
• den single SCO

Examples of using Single SCO in English and their translations into Danish

To the Host LMS, this appears to be a single SCO course.
Til værten LMS, dette synes at være en enkelt SCO kursus.

While there are still some single SCO SCORM 2004 courses, the trend has shifted.
Mens der stadig er nogle enkelte SCO SCORM 2004 kurser, tendensen har flyttet.

In SCORM 1.2 we saw 71% of courses uploaded as a single SCO.
I SCORM 1.2 we saw 71% af kurser uploadet som en enkelt SCO.

If the course at hand contains but a single SCO, displaying that structure is a bad idea.
Hvis kurset ved hånden indeholder, men en enkelt SCO, Viser denne struktur er en dårlig idé.

This chart doesn't take into account the fact that 35% of the uploaded SCORM 2004 courses contained only a single SCO.
Dette skema er der ikke taget højde for, at 35% af de uploadede SCORM 2004 kurser, der er indeholdt kun en enkelt SCO.

The example builds upon the Simple Single SCO example by adding descriptive metadata to the manifest file.
Eksemplet bygger på den Simple Single SCO eksempel ved at tilføje deskriptive metadata til manifest-fil.

Which is closely related to, but not exactly the same as the single SCO's runtime data.
Som er nært beslægtet med, men ikke helt det samme som fælles SCO er runtime data.

In this case, there is a single SCO wrapped in a single aggregation every SCORM course always has an aggregation at the top level.
I dette tilfælde, der er en enkelt SCO svøbt i et enkelt sammenlægning hver SCORM naturligvis altid har en aggregering på øverste niveau.

It simply considers all of the files within the course to be part of a single SCO that is listed in the manifest and packaged up.
Det er ganske enkelt finder alle filerne inden kurset at være en del af en enkelt SCO, der er angivet i manifestet og pakket op.

The status you see in Test Track is the completion status of the root aggregation's sequencing data…. which is closely related to, but not exactly the same as the single SCO's runtime data.
Den status, du ser i Test Track er færdiggørelsen status roden sammenlægning er sekventering data…. som er nært beslægtet med, men ikke helt det samme som fælles SCO er runtime data.

This example builds on the Simple Single SCO to demonstrate the proper use of the basic SCORM run-time data model elements.
Dette eksempel bygger på den enkle Single SCO til at demonstrere den korrekte anvendelse af de grundlæggende SCORM run-time data modelelement.

The biggest thing we run into with that is that we get customers who want to do what you would use sequencing to do, but because sequencing is so complex, they want us to incorporate it into a single SCO or somehow do it in on the course-level side.
Den største ting, vi løber ind i med det er, at vi får kunder, der ønsker at gøre, hvad du ville bruge sekventering til at gøre, men fordi sekvensering er så kompleks, de vil have os til at indarbejde det i en enkelt SCO eller anden måde gøre det ind på kursus-niveau side.

That seems to come back to so many people using single SCO content and then essentially they create their own player within that SCO..
Det synes at komme tilbage til så mange mennesker, der bruger enkelt SCO indhold og derefter i det væsentlige de skaber deres egen spiller inden for denne SCO..

It sounds like now, within the standard it's possible to track multiple SCOs, but you want to make four modules multiple SCOs, but you don't because it's easier to throw them all in a single SCO and do your own table of contents internally, and then you lose tracking?
Det lyder som nu, indenfor standarden er det muligt at spore flere SCOs, men du vil være fire moduler flere SCOs, men du behøver ikke, fordi det er nemmere at smide dem alle i et enkelt SCO og lave din egen indholdsfortegnelse internt, og så mister du sporing?

This chart doesn't take into account the fact that 35% of the uploaded SCORM 2004 courses contained only a single SCO. Since single-SCO courses don't need any sequencing rules, we can ascertain that roughly 70% of all multi-SCO courses use some form of deliberate sequencing strategy.
Dette skema er der ikke taget højde for, at 35% af de uploadede SCORM 2004 kurser, der er indeholdt kun en enkelt SCO. Siden enkelt SCO kurserne ikke behøver nogen sekvenseringsregler, Vi kan konstatere, at omkring 70% af alle multi-SCO kurser bruge nogle form for bevidst sekventering strategi.

While there are still some single SCO SCORM 2004 μαθημάτων, the trend has shifted. Το SCORM 1.2 we saw 71% of courses uploaded as a single SCO. Το SCORM 2004, we only see 35%. And who was the guy who uploaded a 5000 SCO course? I really hope he was just trying to crash our server, αν όχι, I really sympathize with his learners!… and I'm happy to report that the package imported successfully!
Mens der stadig er nogle enkelte SCO SCORM 2004 kurser, tendensen har flyttet. I SCORM 1.2 we saw 71% af kurser uploadet som en enkelt SCO. I SCORM 2004, vi kun se 35%. Og hvem var den fyr, der har uploadet en 5000 SCO kursus? Jeg håber virkelig, at han prøvede bare at gå ned vores server, hvis ikke, Jeg sympatiserer med hans elever! …og jeg er glad for, at pakken importeret!

It simply considers all of the files within the course to be part of a single SCO that is listed in the manifest and packaged up. This example is provided for all versions of SCORM.
Det er ganske enkelt finder alle filerne inden kurset at være en del af en enkelt SCO, der er angivet i manifestet og pakket op. Dette eksempel er for alle versioner af SCORM.

The SCORM run-time specification controls how the LMS launches content and how the content then communicates with the LMS. All of this communication happens within the context of a single attempt on a single SCO. The navigation between SCOs is governed by the sequencing specified in the manifest, and explained further here.
Den SCORM run-time specifikationen styrer hvordan LMS lancerer indhold og hvordan indholdet derefter kommunikerer med LMS. All of this communication happens within the context of a single attempt on a single SCO. The navigation mellem SCOs er reguleret ved sekventering er angivet i manifestet, og forklares yderligere her.

Particularly, it would enable content authors to break content down into smaller chunks which theoretically enables more reuse than the traditional SCORM 1.2 model of a single monolithic SCO.
Især, det ville gøre det muligt for indhold, forfattere til at bryde indholdet ned i mindre bidder, som teoretisk set giver mere genbrug end de traditionelle SCORM 1.2 model af en enkelt monolitisk SCO.

Widespread adoption of SCORM 1.2 brought some problems to light. SCORM 1.2 was very good, but it still had some ambiguities that needed to be tightened up. SCORM 1.2 also lacked a sequencing and navigation specification that allowed the content vendor to specify how the learner was allowed to progress between SCOs. The lack of a sequencing specification meant that most SCORM 1.2 content was produced as a single monolithic SCO instead of created with granular, reusable SCOs. SCORM 2004 addressed both of these problems.
Udbredt vedtagelsen af SCORM 1.2 bragte nogle problemer frem i lyset. SCORM 1.2 var meget godt, men det havde stadig nogle uklarheder, der skulle strammes op. SCORM 1.2 også manglede en sekventering og navigation specifikation thaSCORMowed indholdet sælgeren at angive, hvordan den lærende fik lov til at fremskridt mellem SCOs. Manglen på en rækkefølge specifikation betød, at de fleste SCORM 1.2 Indholdet blev fremstillet som en enkelt monolitisk SCO i stedet for oprettet med granuleret, genanvendelige Off. SCORM 2004 henvender sig både af disse problemer.

The lack of a sequencing specification meant that most SCORM 1.2 content was produced as a single monolithic SCO instead of created with granular, reusable SCOs.
Manglen på en rækkefølge specifikation betød, at de fleste SCORM 1.2 Indholdet blev fremstillet som en enkelt monolitisk SCO i stedet for oprettet med granuleret, genanvendelige Off.