![]() |
IMS GLC Public Forums and Resources | ![]() |
| "Where the World's Leaders in Learning Converge"
join :
help :
calendar :
home
|
||
|
Latest News:
|
latest topics : statistics | |


|
Topic Title: Extending Common Cartridge Metadata Topic Summary: Can CC Metadata be extended to meet specific organizational needs? Created On: 11/28/2010 03:30 AM Status: Post and Reply |
Linear : Threading : Single : Branch |
Topic Tools
|
|
|
|
|
Our organization is considering adopting the CC standards in their educational content. After inspecting the basic metadata elements allowed in CC, we have found that many descriptive properties of our content are not supported by the basic metadata.
In the frequently asked questions of CC I see that it is stated clearly that metadata can be extended to fit individual needs. Can anyone tell me how exactly this can be done. Does it require a community-level approval process, or can we accomplish it inside of our organization by extending the schema ourselves, all the while maintaining conformance to CC. Thank you in advance for any responses. |
|
|
|
|
|
|
|
|
looks like they don't really answer questions here. i am myself curious about this
|
|
|
|
|
|
|
|
|
The supported metadata fields in CC are enumerated. By convention, you should follow the intent of each field with regard to its content. Which specific metadata do you want to add that you don't see covered? Depending on the metadata, there may be a suggested best practice.
|
|
|
|
|
|
|
|
|
I am facing the same situation. We want to include additional metadata to items which follow a custom schema. Is it possible to reference such an "extension metadata file"?
|
|
|
|
|
FuseTalk Standard Edition v3.2 - © 1999-2013 FuseTalk Inc. All rights reserved.