Changeset 38194

Timestamp:

2023-09-24T21:13:41+13:00 (8 months ago)

Author:

anupama

Message:

Adding the javascript wrapper to the perl modmetadataaction cgiactions just committed that introduced the remove-metadata-array methods. All of it is as yet untested. To be tested next.

File:

• main/trunk/greenstone3/web/interfaces/default/js/javascript-global-functions.js (modified) (1 diff)

main/trunk/greenstone3/web/interfaces/default/js/javascript-global-functions.js

@@ -1020 +1020 @@
 }
 
+// metamode (such as accumulate) has no meaning when removingMetadata,
+// so best not make it an option to avoid confusing callers?
+gs.functions.removeMetadataArray = function(collection, site, docArray, /*metamode,*/
+            where, successResponseFunction, forceSync, errorResponseFunction) 
+{  
+    if( typeof errorResponseFunction === 'undefined' ) { errorResponseFunction = null; } // force error callback to be defined: either null or has value
+
+    var payload = gs.functions.getComplexDataForMetadataServer("remove-metadata-array", collection, site, docArray, null/*metamode*/, where);
+    
+    // set operations are generally synchronous, but allow calling function to force ajax call 
+    // to be synchronous or not. Default is synchronous, as it was for GS2
+    if(forceSync == null) {
+    forceSync = true;
+    }
+    
+    //console.log("cgi-bin/metadata-server.pl?"+params);
+    
+    var response = gs.functions._callMetadataServer("Removing metadata from "+where, payload, successResponseFunction, errorResponseFunction, {"forceSync": forceSync, "requestMethod": "POST"});
+    
+    return response;
+}
+
 
 /***********************************************************