Opened 13 years ago

Closed 13 years ago

#830 closed defect (fixed)

MEF Export does not export xlinks

Reported by: jesseeichar Owned by: jesseeichar
Priority: major Milestone: v2.6.5
Component: General Version: v2.6.4
Keywords: Cc:

Description

MEF Export uses its own get metadata method that directly queries the database and as a result it does not do all the same actions as in getMetadata.

Change History (4)

comment:1 by fxp, 13 years ago

I think that should be an option of MEF export as XLinks may be valid/useful across catalogues. Maybe the default should be resolveXlinks = true.

comment:2 by jesseeichar, 13 years ago

Owner: changed from geonetwork-devel@… to jesseeichar
Status: newassigned

There is already a configuration option for exporting xlinks do you think there should be a second parameter for export?

comment:3 by jesseeichar, 13 years ago

I am implementing 2 parameters for service:

resolveXLinks default true removeXlinkAttribute default true

comment:4 by jesseeichar, 13 years ago

Resolution: fixed
Status: assignedclosed

Resolved as of r8874

Note: See TracTickets for help on using tickets.