info:sid/localhost:CollectionWikiData:CustomizationNotes info:sid/localhost:CollectionWikiData CollectionWikiData http://alcme.oclc.org:80/wikid/search/WikiDb.localhost CustomizationNotes display WikiD Documentation Documentation for the OSS WikiD web application userAssigned mailto:jyoung@oclc.org no info:sid/localhost:CollectionSimpleSchemas:wiki info:sid/localhost:CollectionExternalSchemas:xhtml info:sid/localhost:CollectionExternalSchemas:xhtml 1.1 1 y6elg5 300 http://www.oclc.org/schemas/WikiRepository xml http://alcme.oclc.org:80/wikid/docs/WikiRepository info:sid/localhost:CollectionWikiData:CustomizationNotes anonymous CollectionWikiData 2006/01/03/16 inf_3asid_2flocalhost_3aCollectionWikiData_3aCustomizationNotes_5f20060103161707088 text/xml CollectionWikiData:CustomizationNotes 2006-01-03 2006-01-03 1 1.1 repos.hasDate = "hasdate" and oai.identifier exact "info:sid/localhost:CollectionWikiData:CustomizationNotes" cql.any = huh? 1 1 xml default 2006-01-03 http://alcme.oclc.org:80/wikid/docs/WikiRepository/2006/01/03/16/inf_3asid_2flocalhost_3aCollectionWikiData_3aCustomizationNotes_5f20060103161707088 = Customization Notes = As much as possible, WikiD collections can be created and customized directly through the wiki-style user interface. Sometimes, though, custom XSL Stylesheets and Java code are needed to take full advantage of the collection's potential. These levels of customization, however, are inherently risky and thus require the assistance of the WikiD administrator to configure. == Custom Collection Displays == When you configure a collection, you have an option for "XSL Stylesheet". The "System-created" radio button causes WikiD to use a default stylesheet. The "Manually-created" radio button allows the collection administrator to override this default. See CollectionWikiPages:WikiDbXslOverride for details. == Custom Collection "Actions" == You can create custom "action" handlers by extending the ORG.oclc.openurl.app.services.actions.Abstract''''''Action Java class and placing it in the package ORG.oclc.openurl.app.services.actions.Collection''''''Foo.Action_bar, where "Collection''''''Foo" is replaced by the name of the collection and "bar" is replaced by the name of the action you wish to implement. Creating the class in this location is sufficient for WikiD to recognize and use it. == Custom Collection Importing == The default import mechanism works by harvesting records from a specified OAI repository in the collection's native format. If you want to import records into a collection using an alternative mechanism, you can do so by creating an XSL Stylesheet at xsl/mwCollections/Collection''''''Foo/import.xsl (where "Collection''''''Foo" is replace by the real collection name). The import processor should pick it up automatically. == Custom Collection Crosswalks == You can use XSL Stylesheets to crosswalk native records into arbitrary XML Schemas by placing them in the xsl/mwCollections/Collection''''''Foo/crosswalks/bar2baz.xsl directory (where "Collection''''''Foo" is replaced by the real collection name). The name bar2baz.xsl is arbitrary, but it might help to rename bar to match the recordPrefix of you native format and baz to match the recordPrefix of your target format. This crosswalk must be registered in the WikiD.props file. The property should be named: Crosswalk!Collection''''''Foo!xyz (with "Collection''''''Foo" replaced by the real collection name and "xyz" replaced with the desired recordPrefix for the target XML Schema registered in CollectionExternalSchemas) The value for this property should be the URL where the XSL Stylesheet capable of transforming the native record format into "xyz" can be found (see above). Several examples are present in WikiD.props that can be used as a guide. The last step is to select "xyz" as one of the crosswalks in the collection configuration record. == Custom Global Crosswalks == Crosswalks are defined globally much the same as just described for collections. The difference in the global case is that the Crosswalk property in WikiD.props should be changed to use the recordPrefix of the native format in place of the collection name.

Customization Notes

As much as possible, WikiD collections can be created and customized directly through the wiki-style user interface. Sometimes, though, custom XSL Stylesheets and Java code are needed to take full advantage of the collection's potential. These levels of customization, however, are inherently risky and thus require the assistance of the WikiD administrator to configure.

Custom Collection Displays

When you configure a collection, you have an option for "XSL Stylesheet". The "System-created" radio button causes WikiD to use a default stylesheet. The "Manually-created" radio button allows the collection administrator to override this default. See CollectionWikiPages:WikiDbXslOverride for details.

Custom Collection "Actions"

You can create custom "action" handlers by extending the ORG.oclc.openurl.app.services.actions.AbstractAction Java class and placing it in the package ORG.oclc.openurl.app.services.actions.CollectionFoo.Action_bar, where "CollectionFoo" is replaced by the name of the collection and "bar" is replaced by the name of the action you wish to implement. Creating the class in this location is sufficient for WikiD to recognize and use it.

Custom Collection Importing

The default import mechanism works by harvesting records from a specified OAI repository in the collection's native format. If you want to import records into a collection using an alternative mechanism, you can do so by creating an XSL Stylesheet at xsl/mwCollections/CollectionFoo/import.xsl (where "CollectionFoo" is replace by the real collection name). The import processor should pick it up automatically.

Custom Collection Crosswalks

You can use XSL Stylesheets to crosswalk native records into arbitrary XML Schemas by placing them in the xsl/mwCollections/CollectionFoo/crosswalks/bar2baz.xsl directory (where "CollectionFoo" is replaced by the real collection name). The name bar2baz.xsl is arbitrary, but it might help to rename bar to match the recordPrefix of you native format and baz to match the recordPrefix of your target format. This crosswalk must be registered in the WikiD.props file. The property should be named:

Crosswalk!CollectionFoo!xyz (with "CollectionFoo" replaced by the real collection name and "xyz" replaced with the desired recordPrefix for the target XML Schema registered in CollectionExternalSchemas)

The value for this property should be the URL where the XSL Stylesheet capable of transforming the native record format into "xyz" can be found (see above). Several examples are present in WikiD.props that can be used as a guide.

The last step is to select "xyz" as one of the crosswalks in the collection configuration record.

Custom Global Crosswalks

Crosswalks are defined globally much the same as just described for collections. The difference in the global case is that the Crosswalk property in WikiD.props should be changed to use the recordPrefix of the native format in place of the collection name.