\n \n {fieldName.replace(/([A-Z])/g, ' $1').trim()}\n {isRequired && *}\n \n {inputElement}\n {fieldConfig.format && (\n

Format: {fieldConfig.format}

\n )}\n

\n );\n };\n\n return (\n

\n {isImport ? 'Import New Account' : `Edit Account ${account?.UID}`}\n

\n\n

\n {/* UID field for import */}\n {isImport && (\n

Account Identifier

\n \n UID (optional - will be generated if not provided)\n \n \n

\n )}\n\n {/* Profile Fields */}\n {schema?.profileSchema?.fields && (\n

Profile Information

\n {Object.entries(schema.profileSchema.fields).map(([fieldName, fieldConfig]) =>\n renderField(fieldName, fieldConfig, 'profile', account?.profile?.[fieldName])\n )}\n

\n )}\n\n {/* Common Profile Fields (if no schema) */}\n {!schema?.profileSchema?.fields && (\n

Profile Information

\n \n First Name\n \n \n

\n \n Last Name\n \n \n

\n \n Email\n \n \n

\n )}\n\n {/* Data Fields */}\n {schema?.dataSchema?.fields && (\n

Custom Data

\n {Object.entries(schema.dataSchema.fields).map(([fieldName, fieldConfig]) =>\n renderField(fieldName, fieldConfig, 'data', account?.data?.[fieldName])\n )}\n

\n )}\n\n {/* Custom Data Fields (if account has data but no schema) */}\n {!schema?.dataSchema?.fields && account?.data && Object.keys(account.data).length > 0 && (\n

Custom Data

\n {Object.entries(account.data).map(([fieldName, value]) => (\n

\n \n {fieldName}\n \n \n

\n ))}\n

\n )}\n\n {/* Add Custom Data Field */}\n

Add Custom Data Field

\n \n Field Name\n \n \n

\n \n Field Value (JSON format)\n \n \n

\n \n Add Field\n \n

\n\n {/* Form Actions */}\n

\n \n Cancel\n \n \n {isImport ? 'Import Account' : 'Update Account'}\n \n

\n\n {/* JavaScript for dynamic field addition and form submission */}\n \n \n \n \n \n

{children}

\n \n \n );\n}",[],[160,178,215],[160,178],{"_104":225,"_97":226,"_161":227,"_163":162,"_164":146,"_165":228,"_167":118,"_106":229,"_101":230,"_169":231,"_171":232,"_172":22,"_173":-5,"_174":233,"_100":234},"46e252dc-b73f-11f0-a61a-0224a6c84d84","index.tsx","3125b064-4585-11f0-b65c-76b3cceeab13",168,["D",1762014284841],25,"http","/** @jsxImportSource https://esm.sh/hono@4.0.0/jsx */\n\nimport { Hono } from \"https://esm.sh/hono@4.0.0\";\nimport { readFile, serveFile } from \"https://esm.town/v/std/utils@85-main/index.ts\";\nimport { AccountForm } from \"./components/AccountForm.tsx\";\nimport { AccountSearch } from \"./components/AccountSearch.tsx\";\nimport { AccountViewer } from \"./components/AccountViewer.tsx\";\nimport { Layout } from \"./components/Layout.tsx\";\n\nconst app = new Hono();\n\n// Unwrap Hono errors to see original error details\napp.onError((err, c) => {\n throw err;\n});\n\n// Gigya API Configuration\nconst GIGYA_DOMAIN = Deno.env.get(\"GIGYA_DOMAIN\") || \"accounts.eu1.gigya.com\";\nconst GIGYA_API_KEY = Deno.env.get(\"GIGYA_API_KEY\") || \"\";\nconst GIGYA_APP_KEY = Deno.env.get(\"GIGYA_APP_KEY\") || \"\";\nconst GIGYA_APP_SECRET = Deno.env.get(\"GIGYA_APP_SECRET\") || \"\";\n\nif (!GIGYA_API_KEY || !GIGYA_APP_KEY || !GIGYA_APP_SECRET) {\n console.warn(\"Missing Gigya environment variables. Some features may not work.\");\n}\n\n// Direct Gigya API functions\nasync function makeGigyaRequest(endpoint: string, params: Record): Promise {\n const url = `https://${GIGYA_DOMAIN}/${endpoint}?httpStatusCodes=true`;\n\n const body = new URLSearchParams({\n apiKey: GIGYA_API_KEY,\n userKey: GIGYA_APP_KEY,\n secret: GIGYA_APP_SECRET,\n ...params,\n });\n\n const response = await fetch(url, {\n method: \"POST\",\n headers: { \"Content-Type\": \"application/x-www-form-urlencoded\" },\n body,\n });\n\n if (!response.ok) {\n const text = await response.text();\n throw new Error(`HTTP ${response.status}: ${text}`);\n }\n\n const result = await response.json();\n\n if (result.errorCode !== 0) {\n throw new Error(`Gigya API Error ${result.errorCode}: ${result.errorMessage || \"Unknown error\"}`);\n }\n\n return result;\n}\n\nasync function getAccountInfo(uid: string, include?: string) {\n try {\n const response = await makeGigyaRequest(\"accounts.getAccountInfo\", {\n UID: uid,\n include: include\n || \"profile,data,communications,groups,loginIDs,lastLogin,lastLoginLocation,registrationTimestamp,verified,verifiedTimestamp,oldestDataUpdated,oldestDataUpdatedTimestamp\",\n });\n return response;\n } catch (error) {\n console.error(`Error fetching account info for UID ${uid}:`, error);\n return null;\n }\n}\n\nasync function setAccountInfo(uid: string, accountData: {\n profile?: any;\n data?: any;\n communications?: any;\n}) {\n try {\n const params: Record = { UID: uid };\n\n if (accountData.profile) {\n params.profile = JSON.stringify(accountData.profile);\n }\n\n if (accountData.data) {\n params.data = JSON.stringify(accountData.data);\n }\n\n if (accountData.communications) {\n params.communications = JSON.stringify(accountData.communications);\n }\n\n const response = await makeGigyaRequest(\"accounts.setAccountInfo\", params);\n return response;\n } catch (error) {\n console.error(`Error updating account ${uid}:`, error);\n throw error;\n }\n}\n\nasync function importAccount(accountData: {\n profile?: any;\n loginIDs?: any;\n password?: any;\n data?: any;\n UID?: string;\n}) {\n try {\n const params: Record = {};\n\n if (accountData.profile) {\n params.profile = JSON.stringify(accountData.profile);\n }\n\n if (accountData.loginIDs) {\n params.loginIDs = JSON.stringify(accountData.loginIDs);\n }\n\n if (accountData.password) {\n params.password = JSON.stringify(accountData.password);\n }\n\n if (accountData.data) {\n params.data = JSON.stringify(accountData.data);\n }\n\n if (accountData.UID) {\n params.UID = accountData.UID;\n }\n\n const response = await makeGigyaRequest(\"accounts.importFullAccount\", params);\n return response;\n } catch (error) {\n console.error(\"Error importing account:\", error);\n throw error;\n }\n}\n\nasync function getSchema() {\n try {\n const response = await makeGigyaRequest(\"accounts.getSchema\", {});\n return response;\n } catch (error) {\n console.error(\"Error fetching account schema:\", error);\n return null;\n }\n}\n\nasync function setSchema(schemaData: {\n profileSchema?: any;\n dataSchema?: any;\n}) {\n try {\n const params: Record = {};\n\n if (schemaData.profileSchema) {\n params.profileSchema = JSON.stringify(schemaData.profileSchema);\n }\n\n if (schemaData.dataSchema) {\n params.dataSchema = JSON.stringify(schemaData.dataSchema);\n }\n\n await makeGigyaRequest(\"accounts.setSchema\", params);\n } catch (error) {\n console.error(\"Error setting account schema:\", error);\n throw error;\n }\n}\n\n// Serve static files\napp.get(\"/frontend/*\", c => serveFile(c.req.path, import.meta.url));\napp.get(\"/shared/*\", c => serveFile(c.req.path, import.meta.url));\n\n// Main page - Account search and viewer\napp.get(\"/\", async (c) => {\n try {\n const uid = c.req.query(\"uid\");\n const select = c.req.query(\"select\") || \"*\";\n const filter = c.req.query(\"filter\");\n const page = parseInt(c.req.query(\"page\") || \"1\");\n const limit = parseInt(c.req.query(\"limit\") || \"50\");\n\n // Get account schema\n const schema = await getSchema();\n const searchQuery = filter ? `WHERE ${filter}` : \"\";\n const selectQuery = select ? select : \"*\";\n const query = `select ${selectQuery} from accounts ${searchQuery} limit ${Math.min(limit, 100)}`;\n console.log(\n \"Searching with query:\",\n `select ${selectQuery} from accounts ${searchQuery} limit ${Math.min(limit, 100)}`,\n );\n\n const { results: accounts, totalCount } = await makeGigyaRequest(\"accounts.search\", {\n query: query,\n openCursor: true,\n });\n\n return c.html(\n \n

Account Viewer

\n \n Import Account\n \n

\n\n \n\n {/* Search Results */}\n {accounts.length > 0 && (\n

\n Search Results ({totalCount} {totalCount === 1 ? \"account\" : \"accounts\"} found)\n

\n {totalCount > limit && (\n

\n Showing {Math.min(limit, accounts.length)} of {totalCount} results\n

\n )}\n

\n\n {accounts.map((account, index) => (\n \n ))}\n\n {/* Pagination */}\n {totalCount > limit && (\n

\n Page {page} of {Math.ceil(totalCount / limit)}\n

\n {page > 1 && (\n \n Previous\n \n )}\n {page < Math.ceil(totalCount / limit) && (\n \n Next\n \n )}\n

\n )}\n

\n )}\n\n {/* No results message */}\n {(uid || query || filter) && accounts.length === 0 && (\n

\n \n

No accounts found

\n No accounts match your search criteria. Try adjusting your search terms or using different criteria.\n

\n \n Clear Search\n \n

\n )}\n

\n ,\n );\n } catch (error) {\n return c.html(\n \n

\n Error: {error.message}\n

\n ,\n );\n }\n});\n\n// Edit account form\napp.get(\"/edit/:uid\", async (c) => {\n try {\n const uid = c.req.param(\"uid\");\n\n const [schema, account] = await Promise.all([\n getSchema(),\n getAccountInfo(uid),\n ]);\n\n if (!account) {\n return c.html(\n \n

\n Account not found\n

\n ,\n );\n }\n\n return c.html(\n \n

\n ← Back\n

Edit Account

\n \n

\n ,\n );\n } catch (error) {\n return c.html(\n \n

\n Error: {error.message}\n

\n ,\n );\n }\n});\n\n// Import account form\napp.get(\"/import\", async (c) => {\n try {\n const schema = await getSchema();\n\n return c.html(\n \n

\n ← Back\n

Import New Account

\n \n

\n ,\n );\n } catch (error) {\n return c.html(\n \n

\n Error: {error.message}\n

\n ,\n );\n }\n});\n\n// API Routes\n\n// Get account info\napp.get(\"/api/account/:uid\", async (c) => {\n try {\n const uid = c.req.param(\"uid\");\n const account = await getAccountInfo(uid);\n\n if (!account) {\n return c.json({ success: false, error: \"Account not found\" }, 404);\n }\n\n return c.json({ success: true, data: account });\n } catch (error) {\n return c.json({ success: false, error: error.message }, 500);\n }\n});\n\n// Search accounts\napp.get(\"/api/search\", async (c) => {\n try {\n const query = c.req.query(\"q\") || \"\";\n const filter = c.req.query(\"filter\") || \"\";\n const select = c.req.query(\"select\") || \"\";\n const page = parseInt(c.req.query(\"page\") || \"1\");\n const limit = parseInt(c.req.query(\"limit\") || \"50\");\n\n const result = await searchAccountsWithFilter(query, filter, select, page, limit);\n\n return c.json({ success: true, data: result });\n } catch (error) {\n return c.json({ success: false, error: error.message }, 500);\n }\n});\n\n// Update account\napp.put(\"/api/account/:uid\", async (c) => {\n try {\n const uid = c.req.param(\"uid\");\n const body = await c.req.json();\n\n const result = await setAccountInfo(uid, body);\n return c.json({ success: true, data: result });\n } catch (error) {\n return c.json({ success: false, error: error.message }, 500);\n }\n});\n\n// Import account\napp.post(\"/api/account/import\", async (c) => {\n try {\n const body = await c.req.json();\n const result = await importAccount(body);\n return c.json({ success: true, data: result });\n } catch (error) {\n return c.json({ success: false, error: error.message }, 500);\n }\n});\n\n// Get schema\napp.get(\"/api/schema\", async (c) => {\n try {\n const schema = await getSchema();\n return c.json({ success: true, data: schema });\n } catch (error) {\n return c.json({ success: false, error: error.message }, 500);\n }\n});\n\n// Update schema\napp.put(\"/api/schema\", async (c) => {\n try {\n const body = await c.req.json();\n await setSchema(body);\n return c.json({ success: true });\n } catch (error) {\n return c.json({ success: false, error: error.message }, 500);\n }\n});\n\n// Health check\napp.get(\"/api/health\", (c) => {\n return c.json({\n success: true,\n timestamp: new Date().toISOString(),\n service: \"Gigya Account Viewer\",\n });\n});\n\nexport default app.fetch;",[],[160,226],[160],{"_104":237,"_97":238,"_161":239,"_163":-5,"_164":146,"_165":240,"_167":118,"_106":241,"_101":219,"_169":170,"_171":-5,"_172":22,"_173":-5,"_174":242,"_100":293},"528b13ee-457f-11f0-9f14-76b3cceeab13","dsviewer","75b508e6-a450-407f-822f-84516b97fe42",95,["D",1749507359638],[243,285],{"_104":244,"_97":178,"_161":245,"_163":239,"_164":146,"_165":246,"_167":118,"_106":247,"_101":33,"_169":170,"_171":-5,"_172":22,"_173":-5,"_174":248,"_100":284},"b07e1f3e-455f-11f0-9403-76b3cceeab13","a9e5bb92-55e8-4de2-8a96-dc08aa2c1f34",84,["D",1749493773363],[249,258,267,275],{"_104":250,"_97":251,"_161":252,"_163":245,"_164":146,"_165":253,"_167":118,"_106":254,"_101":219,"_169":190,"_171":255,"_172":22,"_173":-5,"_174":256,"_100":257},"bebb335c-4569-11f0-a365-76b3cceeab13","DSViewer.tsx","cd09daf8-455f-11f0-b750-76b3cceeab13",93,["D",1749498092221],"/** @jsxImportSource https://esm.sh/hono@4.0.0/jsx */\n\ninterface DSViewerProps {\n type: string;\n data: any[];\n schema: any;\n totalCount: number;\n currentPage: number;\n limit: number;\n search: string;\n}\n\nfunction formatValue(value: any, maxLength: number = 100): { display: string; full?: string } {\n if (value === null || value === undefined) {\n return { display: \"null\" };\n }\n \n if (typeof value === \"object\") {\n const jsonStr = JSON.stringify(value, null, 2);\n if (jsonStr.length > maxLength) {\n return {\n display: `${jsonStr.substring(0, maxLength)}...`,\n full: jsonStr\n };\n }\n return { display: jsonStr };\n }\n \n const str = String(value);\n if (str.length > maxLength) {\n return {\n display: `${str.substring(0, maxLength)}...`,\n full: str\n };\n }\n \n return { display: str };\n}\n\nfunction getFieldsFromData(data: any[]): string[] {\n const fields = new Set();\n \n // Always include metadata fields\n fields.add(\"oid\");\n fields.add(\"created\");\n fields.add(\"lastUpdated\");\n \n // Extract fields from data objects\n data.forEach(item => {\n if (item.data && typeof item.data === \"object\") {\n Object.keys(item.data).forEach(key => fields.add(`data.${key}`));\n }\n if (item.UID) fields.add(\"UID\");\n });\n \n return Array.from(fields).sort();\n}\n\nfunction getNestedValue(obj: any, path: string): any {\n return path.split('.').reduce((current, key) => {\n return current && current[key] !== undefined ? current[key] : null;\n }, obj);\n}\n\nexport function DSViewer({ type, data, schema, totalCount, currentPage, limit, search }: DSViewerProps) {\n const fields = getFieldsFromData(data);\n const totalPages = Math.ceil(totalCount / limit);\n \n return (\n

{type} Data

\n Showing {data.length} of {totalCount} items\n {search && ` (filtered by \"${search}\")`}\n

\n \n {/* Pagination */}\n {totalPages > 1 && (\n

\n {currentPage > 1 && (\n \n Previous\n \n )}\n \n \n Page {currentPage} of {totalPages}\n \n \n {currentPage < totalPages && (\n \n Next\n \n )}\n

\n )}\n

\n\n {data.length === 0 ? (\n

No data found

\n {search ? `No items match \"${search}\"` : `No items in ${type}`}\n

\n ) : (\n

\n \n \n \n {fields.map(field => (\n \n ))}\n \n \n \n \n {data.map((item, index) => (\n \n {fields.map(field => {\n const value = getNestedValue(item, field);\n const formatted = formatValue(value);\n \n return (\n \n );\n })}\n \n \n ))}\n \n

\n {field}\n	Actions
\n {formatted.full ? (\n \n {formatted.display}\n \n ) : (\n {formatted.display}\n )}\n	\n \n \n Edit\n \n \n Delete\n \n \n

\n )}\n\n {/* Schema Information */}\n {schema && (\n

\n View Schema Information\n

\n {JSON.stringify(schema, null, 2)}\n

\n )}\n

\n );\n}",[],[238,178,251],{"_104":259,"_97":260,"_161":261,"_163":245,"_164":146,"_165":262,"_167":118,"_106":263,"_101":219,"_169":190,"_171":264,"_172":22,"_173":-5,"_174":265,"_100":266},"c96ae220-4569-11f0-9823-76b3cceeab13","DataForm.tsx","e127f394-455f-11f0-bc33-76b3cceeab13",94,["D",1749498110148],"/** @jsxImportSource https://esm.sh/hono@4.0.0/jsx */\n\ninterface DataFormProps {\n type: string;\n schema: any;\n data?: any;\n}\n\nfunction getFieldType(fieldName: string, fieldSchema: any): string {\n if (fieldSchema?.type) {\n switch (fieldSchema.type) {\n case \"integer\":\n case \"long\":\n return \"number\";\n case \"float\":\n return \"number\";\n case \"boolean\":\n return \"checkbox\";\n case \"date\":\n return \"datetime-local\";\n case \"text\":\n case \"string\":\n default:\n return \"text\";\n }\n }\n \n // Infer from field name suffix\n if (fieldName.endsWith(\"_i\") || fieldName.endsWith(\"_l\")) return \"number\";\n if (fieldName.endsWith(\"_f\")) return \"number\";\n if (fieldName.endsWith(\"_b\")) return \"checkbox\";\n if (fieldName.endsWith(\"_d\")) return \"datetime-local\";\n \n return \"text\";\n}\n\nfunction getFieldValue(data: any, fieldPath: string): any {\n if (!data) return \"\";\n \n const parts = fieldPath.split(\".\");\n let value = data;\n \n for (const part of parts) {\n if (value && typeof value === \"object\" && part in value) {\n value = value[part];\n } else {\n return \"\";\n }\n }\n \n return value || \"\";\n}\n\nfunction renderField(fieldName: string, fieldSchema: any, value: any, isEdit: boolean): any {\n const fieldType = getFieldType(fieldName, fieldSchema);\n const isRequired = fieldSchema?.required || false;\n const isReadonly = fieldSchema?.writeAccess === \"serverOnly\";\n \n const commonProps = {\n name: fieldName,\n id: fieldName,\n required: isRequired,\n readonly: isReadonly,\n class: `w-full px-3 py-2 border border-gray-300 rounded-md focus:outline-none focus:ring-2 focus:ring-blue-500 ${\n isReadonly ? \"bg-gray-100\" : \"\"\n }`\n };\n\n if (fieldType === \"checkbox\") {\n return (\n \n );\n }\n\n if (fieldType === \"number\") {\n return (\n \n );\n }\n\n if (fieldType === \"datetime-local\") {\n // Convert various date formats to datetime-local format\n let dateValue = \"\";\n if (value) {\n try {\n const date = new Date(value);\n if (!isNaN(date.getTime())) {\n dateValue = date.toISOString().slice(0, 16);\n }\n } catch (e) {\n // Invalid date, leave empty\n }\n }\n \n return (\n \n );\n }\n\n // For complex objects or long text, use textarea\n if (typeof value === \"object\" || (typeof value === \"string\" && value.length > 100)) {\n const displayValue = typeof value === \"object\" ? JSON.stringify(value, null, 2) : value;\n \n return (\n \n );\n }\n\n return (\n \n );\n}\n\nexport function DataForm({ type, schema, data }: DataFormProps) {\n const isEdit = Boolean(data);\n const fields = schema?.fields || {};\n \n // Get all field names from schema and existing data\n const allFields = new Set();\n \n // Add schema fields\n Object.keys(fields).forEach(field => allFields.add(field));\n \n // Add fields from existing data\n if (data?.data) {\n Object.keys(data.data).forEach(field => allFields.add(`data.${field}`));\n }\n \n const fieldList = Array.from(allFields).sort();\n \n return (\n

\n \n

\n {/* Metadata fields for editing */}\n {isEdit && (\n

Metadata (Read-only)

\n OID: {data.oid}\n

\n Created: {data.createdTime || \"N/A\"}\n

\n Last Updated: {data.lastUpdatedTime || \"N/A\"}\n

\n {data.UID && (\n

\n UID: {data.UID}\n

\n )}\n

\n )}\n\n {/* Data fields */}\n

\n {isEdit ? \"Edit\" : \"Create\"} {type} Data\n

\n \n {fieldList.length === 0 ? (\n

No schema defined for this type

\n You can still create data - fields will be auto-detected\n

\n \n Raw JSON Data\n \n \n

\n ) : (\n

\n {fieldList.map(fieldName => {\n const fieldSchema = fields[fieldName] || {};\n const value = getFieldValue(data, fieldName);\n \n return (\n

\n \n {fieldName}\n {fieldSchema.required && *}\n {fieldSchema.writeAccess === \"serverOnly\" && (\n (read-only)\n )}\n \n {renderField(fieldName, fieldSchema, value, isEdit)}\n {fieldSchema.format && (\n

\n Format: {fieldSchema.format}\n

\n )}\n

\n );\n })}\n

\n )}\n

\n\n {/* Actions */}\n

\n \n Cancel\n \n \n {isEdit ? \"Update\" : \"Create\"}\n \n

\n \n\n {/* Schema Information */}\n {schema && Object.keys(fields).length > 0 && (\n

\n View Schema Details\n

\n {JSON.stringify(schema, null, 2)}\n

\n )}\n

\n );\n}",[],[238,178,260],{"_104":268,"_97":215,"_161":269,"_163":245,"_164":146,"_165":270,"_167":118,"_106":271,"_101":219,"_169":190,"_171":272,"_172":22,"_173":-5,"_174":273,"_100":274},"b3218474-4569-11f0-9d63-76b3cceeab13","b07e0a4e-455f-11f0-9403-76b3cceeab13",91,["D",1749498072755],"/** @jsxImportSource https://esm.sh/hono@4.0.0/jsx */\n\ninterface LayoutProps {\n title: string;\n children: any;\n}\n\nexport function Layout({ title, children }: LayoutProps) {\n return (\n \n \n \n \n {title}\n \n \n \n \n \n \n

\n {children}\n

\n \n \n \n );\n}",[],[238,178,215],{"_104":276,"_97":277,"_161":278,"_163":245,"_164":146,"_165":279,"_167":118,"_106":280,"_101":219,"_169":190,"_171":281,"_172":22,"_173":-5,"_174":282,"_100":283},"b952b034-4569-11f0-a824-76b3cceeab13","TypeSelector.tsx","bc1fc52c-455f-11f0-a4ca-76b3cceeab13",92,["D",1749498083144],"/** @jsxImportSource https://esm.sh/hono@4.0.0/jsx */\n\ninterface TypeSelectorProps {\n types: string[];\n selectedType?: string;\n search?: string;\n}\n\nexport function TypeSelector({ types, selectedType, search }: TypeSelectorProps) {\n return (\n

Select Data Type

\n \n

\n {types.map((type) => (\n \n

{type}

\n Click to view data\n

\n \n ))}\n

\n\n {types.length === 0 && (\n

No data types found

\n Make sure your Gigya DS credentials are configured correctly.\n

\n )}\n\n {selectedType && (\n

\n )}\n

\n );\n}",[],[238,178,277],[238,178],{"_104":286,"_97":226,"_161":116,"_163":239,"_164":146,"_165":287,"_167":118,"_106":288,"_101":289,"_169":231,"_171":290,"_172":22,"_173":-5,"_174":291,"_100":292},"5561921e-b73f-11f0-ba01-0224a6c84d84",169,["D",1762014309157],8,"/** @jsxImportSource https://esm.sh/hono@4.0.0/jsx */\n\nimport { Hono } from \"https://esm.sh/hono@4.0.0\";\nimport { readFile, serveFile } from \"https://esm.town/v/std/utils@85-main/index.ts\";\nimport { DSManager } from \"../shared/ds-manager.ts\";\nimport { DataForm } from \"./components/DataForm.tsx\";\nimport { DSViewer } from \"./components/DSViewer.tsx\";\nimport { Layout } from \"./components/Layout.tsx\";\nimport { TypeSelector } from \"./components/TypeSelector.tsx\";\n\nconst app = new Hono();\n\n// Unwrap Hono errors to see original error details\napp.onError((err, c) => {\n throw err;\n});\n\n// Initialize DS Manager\nconst dsManager = new DSManager();\n\n// Serve static files\napp.get(\"/frontend/*\", c => serveFile(c.req.path, import.meta.url));\napp.get(\"/shared/*\", c => serveFile(c.req.path, import.meta.url));\n\n// Main page - Type selector and data viewer\napp.get(\"/\", async (c) => {\n try {\n const selectedType = c.req.query(\"type\");\n const page = parseInt(c.req.query(\"page\") || \"1\");\n const limit = parseInt(c.req.query(\"limit\") || \"50\");\n const search = c.req.query(\"search\") || \"\";\n\n // Get all available types\n const types = await dsManager.getTypes();\n\n let data = null;\n let schema = null;\n let totalCount = 0;\n\n if (selectedType) {\n // Get schema for the selected type\n schema = await dsManager.getSchema(selectedType);\n\n // Get data for the selected type\n const result = await dsManager.searchData(selectedType, search, page, limit);\n data = result.data;\n totalCount = result.totalCount;\n }\n\n return c.html(\n \n

DS Store Viewer

\n {selectedType && (\n \n Create New {selectedType}\n \n )}\n

\n\n \n\n {selectedType && data && (\n \n )}\n

\n ,\n );\n } catch (error) {\n return c.html(\n \n

\n Error: {error.message}\n

\n ,\n );\n }\n});\n\n// Create data form\napp.get(\"/create\", async (c) => {\n try {\n const type = c.req.query(\"type\");\n if (!type) {\n return c.redirect(\"/\");\n }\n\n const schema = await dsManager.getSchema(type);\n\n return c.html(\n \n

\n ← Back\n

Create New {type}

\n \n

\n ,\n );\n } catch (error) {\n return c.html(\n \n

\n Error: {error.message}\n

\n ,\n );\n }\n});\n\n// Edit data form\napp.get(\"/edit/:type/:id\", async (c) => {\n try {\n const type = c.req.param(\"type\");\n const id = c.req.param(\"id\");\n\n const [schema, item] = await Promise.all([\n dsManager.getSchema(type),\n dsManager.getItem(type, id),\n ]);\n\n if (!item) {\n return c.html(\n \n

\n Item not found\n

\n ,\n );\n }\n\n return c.html(\n \n

\n ← Back\n

Edit {type}

\n \n

\n ,\n );\n } catch (error) {\n return c.html(\n \n

\n Error: {error.message}\n

\n ,\n );\n }\n});\n\n// API Routes\n\n// Get all types\napp.get(\"/api/types\", async (c) => {\n try {\n const types = await dsManager.getTypes();\n return c.json({ success: true, data: types });\n } catch (error) {\n return c.json({ success: false, error: error.message }, 500);\n }\n});\n\n// Get schema for a type\napp.get(\"/api/schema/:type\", async (c) => {\n try {\n const type = c.req.param(\"type\");\n const schema = await dsManager.getSchema(type);\n return c.json({ success: true, data: schema });\n } catch (error) {\n return c.json({ success: false, error: error.message }, 500);\n }\n});\n\n// Search data\napp.get(\"/api/data/:type\", async (c) => {\n try {\n const type = c.req.param(\"type\");\n const search = c.req.query(\"search\") || \"\";\n const page = parseInt(c.req.query(\"page\") || \"1\");\n const limit = parseInt(c.req.query(\"limit\") || \"50\");\n\n const result = await dsManager.searchData(type, search, page, limit);\n return c.json({ success: true, data: result });\n } catch (error) {\n return c.json({ success: false, error: error.message }, 500);\n }\n});\n\n// Get single item\napp.get(\"/api/data/:type/:id\", async (c) => {\n try {\n const type = c.req.param(\"type\");\n const id = c.req.param(\"id\");\n const item = await dsManager.getItem(type, id);\n\n if (!item) {\n return c.json({ success: false, error: \"Item not found\" }, 404);\n }\n\n return c.json({ success: true, data: item });\n } catch (error) {\n return c.json({ success: false, error: error.message }, 500);\n }\n});\n\n// Create item\napp.post(\"/api/data/:type\", async (c) => {\n try {\n const type = c.req.param(\"type\");\n const body = await c.req.json();\n const item = await dsManager.createItem(type, body);\n return c.json({ success: true, data: item });\n } catch (error) {\n return c.json({ success: false, error: error.message }, 500);\n }\n});\n\n// Update item\napp.put(\"/api/data/:type/:id\", async (c) => {\n try {\n const type = c.req.param(\"type\");\n const id = c.req.param(\"id\");\n const body = await c.req.json();\n const item = await dsManager.updateItem(type, id, body);\n return c.json({ success: true, data: item });\n } catch (error) {\n return c.json({ success: false, error: error.message }, 500);\n }\n});\n\n// Delete item\napp.delete(\"/api/data/:type/:id\", async (c) => {\n try {\n const type = c.req.param(\"type\");\n const id = c.req.param(\"id\");\n await dsManager.deleteItem(type, id);\n return c.json({ success: true });\n } catch (error) {\n return c.json({ success: false, error: error.message }, 500);\n }\n});\n\n// Execute custom query\napp.post(\"/api/query\", async (c) => {\n try {\n const { query } = await c.req.json();\n const result = await dsManager.executeQuery(query);\n return c.json({ success: true, data: result });\n } catch (error) {\n return c.json({ success: false, error: error.message }, 500);\n }\n});\n\n// Health check\napp.get(\"/api/health\", (c) => {\n return c.json({\n success: true,\n timestamp: new Date().toISOString(),\n service: \"Generic DS Store Viewer\",\n });\n});\n\nexport default app.fetch;",[],[238,226],[238],{"_104":295,"_97":296,"_161":297,"_163":-5,"_164":146,"_165":298,"_167":118,"_106":299,"_101":33,"_169":170,"_171":-5,"_172":22,"_173":-5,"_174":300,"_100":309},"a21d2cfa-455f-11f0-abcd-76b3cceeab13","shared","08305951-52e8-4c5a-8990-e907da039bbf",83,["D",1749493749218],[301],{"_104":302,"_97":303,"_161":304,"_163":297,"_164":146,"_165":298,"_167":118,"_106":305,"_101":33,"_169":190,"_171":306,"_172":22,"_173":-5,"_174":307,"_100":308},"a21d1116-455f-11f0-abcd-76b3cceeab13","ds-manager.ts","a21d11d4-455f-11f0-abcd-76b3cceeab13",["D",1749493749218],"// Generic Gigya DS Manager\n// Handles all interactions with Gigya Data Store APIs\n\nexport interface GigyaResponse {\n errorCode: number;\n errorMessage?: string;\n callId?: string;\n time?: string;\n statusCode?: number;\n statusReason?: string;\n}\n\nexport interface DSSearchResponse extends GigyaResponse {\n results?: Array<{\n oid: string;\n data: any;\n lastUpdated?: number;\n lastUpdatedTime?: string;\n created?: number;\n createdTime?: string;\n UID?: string;\n }>;\n objectsCount?: number;\n totalCount?: number;\n nextCursorId?: string;\n}\n\nexport interface DSGetResponse extends GigyaResponse {\n data?: any;\n oid?: string;\n UID?: string;\n lastUpdated?: number;\n lastUpdatedTime?: string;\n created?: number;\n createdTime?: string;\n}\n\nexport interface DSStoreResponse extends GigyaResponse {\n oid?: string;\n}\n\nexport interface DSSchemaResponse extends GigyaResponse {\n schema?: {\n fields?: Record;\n dynamicSchema?: boolean;\n };\n}\n\nexport interface DSTypesResponse extends GigyaResponse {\n types?: string[];\n}\n\nexport class DSManager {\n private domain: string;\n private apiKey: string;\n private appKey: string;\n private appSecret: string;\n\n constructor() {\n // Get credentials from environment variables\n this.domain = Deno.env.get(\"GIGYA_DOMAIN\") || \"accounts.eu1.gigya.com\";\n this.apiKey = Deno.env.get(\"GIGYA_API_KEY\") || \"\";\n this.appKey = Deno.env.get(\"GIGYA_APP_KEY\") || \"\";\n this.appSecret = Deno.env.get(\"GIGYA_APP_SECRET\") || \"\";\n\n if (!this.apiKey || !this.appKey || !this.appSecret) {\n console.warn(\"Missing Gigya environment variables. Some features may not work.\");\n }\n }\n\n private async makeRequest(endpoint: string, params: Record): Promise {\n const url = `https://${this.domain}/${endpoint}?httpStatusCodes=true`;\n\n const body = new URLSearchParams({\n apiKey: this.apiKey,\n userKey: this.appKey,\n secret: this.appSecret,\n ...params,\n });\n\n const response = await fetch(url, {\n method: \"POST\",\n headers: { \"Content-Type\": \"application/x-www-form-urlencoded\" },\n body,\n });\n\n if (!response.ok) {\n const text = await response.text();\n throw new Error(`HTTP ${response.status}: ${text}`);\n }\n\n const result = await response.json();\n \n if (result.errorCode !== 0) {\n throw new Error(`Gigya API Error ${result.errorCode}: ${result.errorMessage || 'Unknown error'}`);\n }\n\n return result;\n }\n\n // Get all available data types\n async getTypes(): Promise {\n try {\n const response: DSTypesResponse = await this.makeRequest(\"ds.getTypes\", {});\n return response.types || [];\n } catch (error) {\n console.error(\"Error fetching types:\", error);\n return [];\n }\n }\n\n // Get schema for a specific type\n async getSchema(type: string): Promise {\n try {\n const response: DSSchemaResponse = await this.makeRequest(\"ds.getSchema\", {\n type,\n filter: \"full\"\n });\n return response.schema || null;\n } catch (error) {\n console.error(`Error fetching schema for type ${type}:`, error);\n return null;\n }\n }\n\n // Search data with pagination and filtering\n async searchData(\n type: string, \n searchTerm: string = \"\", \n page: number = 1, \n limit: number = 50\n ): Promise<{ data: any[], totalCount: number, objectsCount: number }> {\n try {\n let query = `SELECT * FROM ${type}`;\n \n // Add search conditions if provided\n if (searchTerm.trim()) {\n // Try to search in common text fields\n const searchConditions = [\n `data CONTAINS \"${searchTerm}\"`,\n `oid CONTAINS \"${searchTerm}\"`\n ];\n query += ` WHERE (${searchConditions.join(\" OR \")})`;\n }\n \n // Add pagination\n const start = (page - 1) * limit;\n query += ` LIMIT ${limit}`;\n if (start > 0) {\n query += ` START ${start}`;\n }\n\n const response: DSSearchResponse = await this.makeRequest(\"ds.search\", {\n query\n });\n\n return {\n data: response.results || [],\n totalCount: response.totalCount || 0,\n objectsCount: response.objectsCount || 0\n };\n } catch (error) {\n console.error(`Error searching data for type ${type}:`, error);\n return { data: [], totalCount: 0, objectsCount: 0 };\n }\n }\n\n // Get a single item by type and ID\n async getItem(type: string, oid: string): Promise {\n try {\n const response: DSGetResponse = await this.makeRequest(\"ds.get\", {\n type,\n oid,\n fields: \"*\"\n });\n\n if (response.data) {\n return {\n oid: response.oid,\n data: response.data,\n lastUpdated: response.lastUpdated,\n lastUpdatedTime: response.lastUpdatedTime,\n created: response.created,\n createdTime: response.createdTime,\n UID: response.UID\n };\n }\n \n return null;\n } catch (error) {\n console.error(`Error fetching item ${oid} of type ${type}:`, error);\n return null;\n }\n }\n\n // Create a new item\n async createItem(type: string, data: any): Promise {\n try {\n const response: DSStoreResponse = await this.makeRequest(\"ds.store\", {\n type,\n data: JSON.stringify(data),\n oid: \"auto\"\n });\n\n return {\n oid: response.oid,\n data\n };\n } catch (error) {\n console.error(`Error creating item of type ${type}:`, error);\n throw error;\n }\n }\n\n // Update an existing item\n async updateItem(type: string, oid: string, data: any): Promise {\n try {\n const response: DSStoreResponse = await this.makeRequest(\"ds.store\", {\n type,\n oid,\n data: JSON.stringify(data),\n updateBehavior: \"replace\"\n });\n\n return {\n oid,\n data\n };\n } catch (error) {\n console.error(`Error updating item ${oid} of type ${type}:`, error);\n throw error;\n }\n }\n\n // Delete an item\n async deleteItem(type: string, oid: string): Promise {\n try {\n await this.makeRequest(\"ds.delete\", {\n type,\n oid,\n fields: \"*\"\n });\n } catch (error) {\n console.error(`Error deleting item ${oid} of type ${type}:`, error);\n throw error;\n }\n }\n\n // Execute a custom query\n async executeQuery(query: string): Promise {\n try {\n const response: DSSearchResponse = await this.makeRequest(\"ds.search\", {\n query\n });\n\n return {\n results: response.results || [],\n totalCount: response.totalCount || 0,\n objectsCount: response.objectsCount || 0\n };\n } catch (error) {\n console.error(\"Error executing custom query:\", error);\n throw error;\n }\n }\n\n // Set schema for a type\n async setSchema(type: string, schema: any): Promise {\n try {\n await this.makeRequest(\"ds.setSchema\", {\n type,\n dataSchema: JSON.stringify(schema)\n });\n } catch (error) {\n console.error(`Error setting schema for type ${type}:`, error);\n throw error;\n }\n }\n\n // Delete schema fields\n async deleteSchemaFields(type: string, fields: string[]): Promise {\n try {\n await this.makeRequest(\"ds.deleteSchemaFields\", {\n type,\n dataSchema: JSON.stringify(fields)\n });\n } catch (error) {\n console.error(`Error deleting schema fields for type ${type}:`, error);\n throw error;\n }\n }\n}",[],[296,303],[296],{"_104":311,"_97":312,"_161":313,"_163":-5,"_164":146,"_165":314,"_167":118,"_106":315,"_101":33,"_169":316,"_171":317,"_172":22,"_173":-5,"_174":318,"_100":319},"2086ef42-42de-11f0-8fb7-76b3cceeab13","README-author-update.md","2086f014-42de-11f0-8fb7-76b3cceeab13",63,["D",1749218224426],"file","# Project Author Update Scripts\n\nThis directory contains scripts to update existing projects in Gigya DS with proper author names where they are missing or set to \"Unknown\".\n\n## Scripts\n\n### 1. `update-project-authors.ts` (Basic Version)\nA straightforward script that updates projects with missing or \"Unknown\" authors.\n\n**Features:**\n- Fetches all projects from Gigya DS\n- Identifies projects needing author updates\n- Updates them with author data from `data.json`\n- Provides summary statistics\n\n### 2. `update-authors-advanced.ts` (Advanced Version)\nA comprehensive script with additional features and configuration options.\n\n**Features:**\n- Dry run mode to preview changes\n- Batch processing with rate limiting\n- Detailed analysis and reporting\n- Configurable update criteria\n- Better error handling and logging\n- Author name cleanup and formatting\n\n## Prerequisites\n\n1. **Environment Variables:**\n ```bash\n export GIGYA_API_KEY=\"your_api_key\"\n export GIGYA_APP_KEY=\"your_app_key\"\n export GIGYA_APP_SECRET=\"your_app_secret\"\n export GIGYA_DOMAIN=\"accounts.eu1.gigya.com\" # Optional, defaults to EU1\n ```\n\n2. **Data Source:**\n - Ensure `data.json` exists in the same directory\n - The file should contain project data with author information\n\n## Usage\n\n### Basic Script\n```bash\n# Run the basic update script\nnpx tsx update-project-authors.ts\n```\n\n### Advanced Script\n\n#### Preview Changes (Dry Run)\n```bash\n# Preview what would be updated without making changes\nDRY_RUN=true npx tsx update-authors-advanced.ts\n```\n\n#### Update All Missing Authors\n```bash\n# Update both missing and \"Unknown\" authors\nnpx tsx update-authors-advanced.ts\n```\n\n#### Update Only \"Unknown\" Authors\n```bash\n# Only update projects where author is specifically \"Unknown\"\nUPDATE_UNKNOWN_ONLY=true npx tsx update-authors-advanced.ts\n```\n\n## Configuration Options (Advanced Script)\n\n| Environment Variable | Default | Description |\n|---------------------|---------|-------------|\n| `DRY_RUN` | `false` | Preview changes without applying them |\n| `UPDATE_UNKNOWN_ONLY` | `false` | Only update \"Unknown\" authors, not missing ones |\n| `GIGYA_DOMAIN` | `accounts.eu1.gigya.com` | Gigya domain to use |\n\n## What Gets Updated\n\nThe scripts will update projects where the author field is:\n- `undefined` or `null`\n- Empty string (`\"\"`)\n- Set to `\"Unknown\"`\n- Set to `\"undefined\"` or `\"null\"` (string values)\n\n**Note:** If `UPDATE_UNKNOWN_ONLY=true`, only projects with author exactly equal to `\"Unknown\"` will be updated.\n\n## Author Name Processing\n\nThe advanced script includes author name cleanup:\n- User IDs like `I123456` become `User I123456`\n- Bot names like `osvote[bot]` become `osvote (Bot)`\n- Other names are used as-is\n\n## Output\n\nBoth scripts provide detailed logging including:\n- Projects being processed\n- Update success/failure status\n- Summary statistics\n- Verification of changes\n\n### Example Output\n```\n🔍 Starting author update process...\n📥 Found 25 existing projects\n📝 Created lookup for 20 projects with author data\n\n🔄 Updating \"bolt.diy\" with author: \"I347305\"\n✅ Successfully updated \"bolt.diy\"\n\n📊 Update Summary:\n✅ Successfully updated: 15 projects\n⏭️ Skipped: 8 projects\n❌ Errors: 0 projects\n📁 Total processed: 23 projects\n```\n\n## Error Handling\n\n- Network errors are caught and reported\n- Individual project failures don't stop the entire process\n- Rate limiting prevents API overload\n- Detailed error messages help with troubleshooting\n\n## Safety Features\n\n- **Dry run mode** allows previewing changes\n- **Batch processing** with delays prevents rate limiting\n- **Verification step** confirms updates were applied\n- **Backup consideration**: The scripts update existing records, so consider backing up your data first\n\n## Troubleshooting\n\n1. **Missing Environment Variables:**\n - Ensure all required Gigya credentials are set\n - Check that the domain is correct for your region\n\n2. **No Projects Updated:**\n - Verify `data.json` contains author information\n - Check that project titles match between DS and data.json\n - Use dry run mode to see what would be updated\n\n3. **API Errors:**\n - Check your Gigya credentials and permissions\n - Verify the DS schema exists and is accessible\n - Ensure rate limits aren't being exceeded\n\n4. **Author Data Not Found:**\n - Verify the project exists in `data.json`\n - Check that the title normalization (cabbabCase) matches\n - Some projects may not have author data in the source\n\n## Next Steps\n\nAfter running the update scripts:\n\n1. **Verify Results:** Check the application to ensure author names display correctly\n2. **Manual Review:** Review any projects that still need author assignment\n3. **Data Quality:** Consider implementing validation to prevent future author data issues\n4. **Monitoring:** Set up processes to ensure new projects include proper author information",[],[312],{"_104":321,"_97":322,"_161":323,"_163":-5,"_164":146,"_165":324,"_167":118,"_106":325,"_101":33,"_169":316,"_171":326,"_172":22,"_173":-5,"_174":327,"_100":328},"cbbc1bc4-42e5-11f0-ba72-76b3cceeab13","README-delete-test-projects.md","cbbc1c8c-42e5-11f0-ba72-76b3cceeab13",67,["D",1749221518146],"# Test Project Deletion Scripts\n\nThis directory contains scripts to safely delete projects with titles that are \"test\" or start with \"test\" from Gigya DS.\n\n## Scripts\n\n### 1. `delete-test-projects.ts` (Basic Version)\nA straightforward script that deletes test projects with minimal configuration.\n\n**Features:**\n- Identifies projects with titles matching \"test\" patterns\n- Soft deletes projects (marks as deleted rather than permanent removal)\n- Provides summary statistics and verification\n\n### 2. `delete-test-projects-advanced.ts` (Advanced Version)\nA comprehensive script with extensive safety features and configuration options.\n\n**Features:**\n- **Dry run mode** to preview deletions\n- **Confirmation prompts** for safety\n- **Flexible matching patterns** (exact match, starts with, custom patterns)\n- **Case sensitivity options**\n- **Batch processing** with rate limiting\n- **Detailed analysis and reporting**\n- **Comprehensive verification**\n\n## ⚠️ Safety Notice\n\n**IMPORTANT:** These scripts perform **soft deletes** by marking projects as `deleted: true` rather than permanently removing them from the database. This allows for potential recovery if needed.\n\n## Prerequisites\n\n1. **Environment Variables:**\n ```bash\n export GIGYA_API_KEY=\"your_api_key\"\n export GIGYA_APP_KEY=\"your_app_key\"\n export GIGYA_APP_SECRET=\"your_app_secret\"\n export GIGYA_DOMAIN=\"accounts.eu1.gigya.com\" # Optional, defaults to EU1\n ```\n\n2. **Permissions:**\n - Ensure your Gigya credentials have write access to the `oss_projects` data store\n\n## Usage\n\n### Basic Script\n```bash\n# Delete all test projects (basic version)\nnpx tsx delete-test-projects.ts\n```\n\n### Advanced Script\n\n#### Preview Deletions (Recommended First Step)\n```bash\n# Preview what would be deleted without making changes\nDRY_RUN=true npx tsx delete-test-projects-advanced.ts\n```\n\n#### Delete with Confirmation\n```bash\n# Delete test projects with confirmation prompt\nCONFIRM_DELETE=DELETE npx tsx delete-test-projects-advanced.ts\n```\n\n#### Delete Without Confirmation\n```bash\n# Delete test projects without confirmation (use with caution!)\nREQUIRE_CONFIRMATION=false npx tsx delete-test-projects-advanced.ts\n```\n\n#### Case Sensitive Matching\n```bash\n# Only match \"Test\" with exact case\nCASE_SENSITIVE=true npx tsx delete-test-projects-advanced.ts\n```\n\n#### Exact Match Only\n```bash\n# Only delete projects with title exactly \"test\"\nEXACT_MATCH_ONLY=true npx tsx delete-test-projects-advanced.ts\n```\n\n#### Custom Patterns\n```bash\n# Delete projects matching custom patterns\nCUSTOM_PATTERNS=\"demo,sample,temp\" npx tsx delete-test-projects-advanced.ts\n```\n\n## Configuration Options (Advanced Script)\n\n| Environment Variable | Default | Description |\n|---------------------|---------|-------------|\n| `DRY_RUN` | `false` | Preview deletions without executing them |\n| `REQUIRE_CONFIRMATION` | `true` | Require manual confirmation before deletion |\n| `CASE_SENSITIVE` | `false` | Use case-sensitive title matching |\n| `EXACT_MATCH_ONLY` | `false` | Only delete exact \"test\" matches, not \"test*\" |\n| `CUSTOM_PATTERNS` | `\"\"` | Comma-separated additional patterns to match |\n| `CONFIRM_DELETE` | `\"\"` | Set to \"DELETE\" to confirm deletion |\n\n## Matching Patterns\n\n### Default Behavior (Case Insensitive)\nThe scripts will delete projects with titles that:\n- Are exactly \"test\" (case insensitive)\n- Start with \"test\" (case insensitive)\n\n**Examples of matched titles:**\n- `test`\n- `Test`\n- `TEST`\n- `test project`\n- `Test Application`\n- `testing something`\n\n### Exact Match Only\nWith `EXACT_MATCH_ONLY=true`, only projects with title exactly \"test\" will be deleted.\n\n### Custom Patterns\nYou can specify additional patterns to match:\n```bash\nCUSTOM_PATTERNS=\"demo,sample,temp,prototype\"\n```\n\nThis will also delete projects containing these words in their titles.\n\n## Output Examples\n\n### Analysis Phase\n```\n🔍 Analyzing projects for test patterns...\n\n📊 Project Analysis:\n 📁 Total active projects: 25\n 🧪 Test projects found: 3\n 🎯 Exact 'test' matches: 1\n 🔤 Starts with 'test': 2\n 🔧 Custom pattern matches: 0\n\n📋 Projects that will be deleted:\n 1. \"test\" - Exact match: 'test'\n 👤 Author: User I123456\n 📅 Created: 12/3/2024\n 2. \"test project\" - Starts with 'test'\n 👤 Author: Developer\n 📅 Created: 12/2/2024\n```\n\n### Deletion Phase\n```\n🗑️ Starting test project deletion...\n\n📦 Processing batch 1/1\n\n🔄 Deleting \"test\"\n 📝 Reason: Exact match: 'test'\n ✅ Successfully deleted\n\n📊 Final Deletion Report:\n✅ Successfully deleted: 3 projects\n❌ Errors: 0 projects\n📈 Success rate: 100.0%\n```\n\n## Safety Features\n\n### 1. Dry Run Mode\n- Preview all changes before execution\n- See exactly which projects would be deleted\n- No actual modifications made\n\n### 2. Confirmation Prompts\n- Manual confirmation required by default\n- Must type \"DELETE\" exactly to proceed\n- Can be disabled for automation\n\n### 3. Soft Deletion\n- Projects marked as `deleted: true`\n- Original data preserved\n- Can potentially be recovered\n\n### 4. Batch Processing\n- Processes projects in small batches\n- Rate limiting to prevent API overload\n- Graceful error handling\n\n### 5. Comprehensive Verification\n- Confirms deletions were successful\n- Reports any remaining test projects\n- Shows before/after statistics\n\n## Recovery\n\nIf you need to recover deleted projects:\n\n```bash\n# Find deleted test projects\n# You would need to create a recovery script that:\n# 1. Searches for projects with deleted=true\n# 2. Filters for test projects\n# 3. Sets deleted=false to restore them\n```\n\n## Troubleshooting\n\n### 1. No Projects Found\n```\n✅ No test projects found to delete.\n```\n- Verify projects exist with test-like titles\n- Check case sensitivity settings\n- Ensure projects aren't already deleted\n\n### 2. Permission Errors\n```\n❌ Failed to delete: Access denied\n```\n- Verify Gigya credentials have write permissions\n- Check API key, app key, and secret are correct\n- Ensure you have access to the oss_projects data store\n\n### 3. Confirmation Issues\n```\n❌ Deletion not confirmed. Exiting.\n```\n- Set `CONFIRM_DELETE=DELETE` environment variable\n- Or use `REQUIRE_CONFIRMATION=false` to skip confirmation\n\n### 4. Rate Limiting\n```\n❌ Error: Too many requests\n```\n- The script includes built-in rate limiting\n- If issues persist, increase delay between requests\n- Process smaller batches\n\n## Best Practices\n\n1. **Always start with dry run:**\n ```bash\n DRY_RUN=true npx tsx delete-test-projects-advanced.ts\n ```\n\n2. **Review the analysis carefully:**\n - Check the list of projects to be deleted\n - Verify no legitimate projects are included\n - Pay attention to author and creation date\n\n3. **Use confirmation for safety:**\n - Keep `REQUIRE_CONFIRMATION=true` for manual operations\n - Only disable for trusted automated processes\n\n4. **Test with exact match first:**\n ```bash\n EXACT_MATCH_ONLY=true DRY_RUN=true npx tsx delete-test-projects-advanced.ts\n ```\n\n5. **Backup considerations:**\n - Consider exporting project data before deletion\n - Soft deletes allow recovery, but backup is safer\n\n## Integration with Other Scripts\n\nThese deletion scripts work well with other project management scripts:\n\n1. **After data imports:** Clean up test projects created during development\n2. **Before production:** Remove test data before going live\n3. **Regular maintenance:** Periodic cleanup of test projects\n\n## Example Workflows\n\n### Development Cleanup\n```bash\n# 1. Preview what would be deleted\nDRY_RUN=true npx tsx delete-test-projects-advanced.ts\n\n# 2. Delete exact \"test\" matches only\nEXACT_MATCH_ONLY=true CONFIRM_DELETE=DELETE npx tsx delete-test-projects-advanced.ts\n\n# 3. Delete all test projects\nCONFIRM_DELETE=DELETE npx tsx delete-test-projects-advanced.ts\n```\n\n### Automated Cleanup\n```bash\n# For CI/CD or automated environments\nREQUIRE_CONFIRMATION=false CUSTOM_PATTERNS=\"temp,demo\" npx tsx delete-test-projects-advanced.ts\n```\n\n### Conservative Cleanup\n```bash\n# Very careful deletion - exact matches only, case sensitive\nEXACT_MATCH_ONLY=true CASE_SENSITIVE=true CONFIRM_DELETE=DELETE npx tsx delete-test-projects-advanced.ts\n```",[],[322],{"_104":330,"_97":331,"_161":332,"_163":-5,"_164":146,"_165":333,"_167":118,"_106":334,"_101":335,"_169":190,"_171":336,"_172":22,"_173":-5,"_174":337,"_100":338},"d4a99f32-4253-11f0-a423-76b3cceeab13","accounts-schema.ts","7efb4cca-4253-11f0-ad15-76b3cceeab13",50,["D",1749158826598],7,"// Script to update Gigya Accounts schema for the OSS Contribution project\n\nconst GIGYA_DOMAIN = process.env.GIGYA_DOMAIN || \"accounts.eu1.gigya.com\";\nconst GIGYA_API_KEY = process.env.GIGYA_API_KEY;\nconst GIGYA_APP_KEY = process.env.GIGYA_APP_KEY;\nconst GIGYA_APP_SECRET = process.env.GIGYA_APP_SECRET;\n\nif (!GIGYA_API_KEY || !GIGYA_APP_KEY || !GIGYA_APP_SECRET) {\n console.error(\"Missing Gigya environment variables!\");\n console.log(\"Required variables: GIGYA_API_KEY, GIGYA_APP_KEY, GIGYA_APP_SECRET\");\n process.exit(1);\n}\n\nasync function makeGigyaRequest(endpoint, params) {\n const url = `https://${GIGYA_DOMAIN}/${endpoint}?httpStatusCodes=true`;\n\n const body = new URLSearchParams({\n apiKey: GIGYA_API_KEY,\n userKey: GIGYA_APP_KEY,\n secret: GIGYA_APP_SECRET,\n ...params,\n });\n\n const response = await fetch(url, {\n method: \"POST\",\n headers: { \"Content-Type\": \"application/x-www-form-urlencoded\" },\n body,\n });\n\n if (!response.ok) {\n const text = await response.text();\n throw new Error(`${response.statusText}: ${text}`);\n }\n\n const text = await response.text();\n return JSON.parse(text);\n}\n\nasync function updateAccountsSchema() {\n console.log(\"Updating Gigya Accounts schema for OSS Contribution project...\");\n\n // Define the data schema fields to add/update\n const dataSchema = {\n dynamicSchema: true,\n fields: {\n \"vote\": {\n type: \"basic-string\",\n writeAccess: \"clientModify\",\n },\n \"assign\": {\n type: \"basic-string\",\n writeAccess: \"serverOnly\",\n },\n },\n };\n\n try {\n // Get current schema first\n console.log(\"Getting current accounts schema...\");\n const currentSchemaResponse = await makeGigyaRequest(\"accounts.getSchema\", {});\n\n if (currentSchemaResponse.errorCode !== 0) {\n console.error(\"❌ Failed to get current schema:\", currentSchemaResponse.errorMessage);\n return false;\n }\n\n console.log(\"✅ Current schema retrieved successfully\");\n\n // Update the schema with new fields\n console.log(\"Updating accounts schema with vote field...\");\n\n const response = await makeGigyaRequest(\"accounts.setSchema\", {\n dataSchema: JSON.stringify(dataSchema),\n });\n\n if (response.errorCode === 0) {\n console.log(\"✅ Accounts schema updated successfully\");\n } else {\n console.error(\"❌ Failed to update accounts schema:\", response.errorMessage);\n return false;\n }\n\n // Verify the schema was updated\n console.log(\"Verifying updated schema...\");\n const verifyResponse = await makeGigyaRequest(\"accounts.getSchema\", {});\n\n if (verifyResponse.errorCode === 0) {\n console.log(\"✅ Schema verification successful\");\n\n // Check if our new field is present\n if (verifyResponse.dataSchema && verifyResponse.dataSchema.vote) {\n const voteField = verifyResponse.dataSchema.vote;\n console.log(\n `✅ Vote field added: type=${voteField.type}, writeAccess=${voteField.writeAccess || \"serverOnly\"}`,\n );\n } else {\n console.log(\"⚠️ Vote field not found in schema response\");\n }\n\n // Show all data schema fields\n if (verifyResponse.dataSchema) {\n const fields = Object.keys(verifyResponse.dataSchema);\n console.log(\"Data schema fields:\", fields.join(\", \"));\n }\n } else {\n console.error(\"❌ Schema verification failed:\", verifyResponse.errorMessage);\n }\n\n return true;\n } catch (error) {\n console.error(\"❌ Error updating accounts schema:\", error.message);\n return false;\n }\n}\n\n// Run the script\nupdateAccountsSchema()\n .then((success) => {\n if (success) {\n console.log(\"\\n🎉 Accounts schema update completed successfully!\");\n console.log(\"\\nNext steps:\");\n console.log(\"1. Test voting functionality with the new schema\");\n console.log(\"2. Verify client-side vote updates work correctly\");\n } else {\n console.log(\"\\n❌ Accounts schema update failed!\");\n process.exit(1);\n }\n })\n .catch((error) => {\n console.error(\"❌ Script execution failed:\", error);\n process.exit(1);\n });",[],[331],{"_104":340,"_97":341,"_161":342,"_163":-5,"_164":146,"_165":343,"_167":118,"_106":344,"_101":345,"_169":316,"_171":346,"_172":22,"_173":-5,"_174":347,"_100":348},"3a4f9680-4596-11f0-9a93-76b3cceeab13","accounts.yaml","751a558c-457f-11f0-88a2-76b3cceeab13",129,["D",1749517197409],9,"openapi: 3.0.3\ninfo:\n title: SAP Customer Data Cloud - Account API\n version: 1.0.0\n description: OpenAPI spec for Account Info, Account Update, Account Import, Schema\n configuration, and Account Search\nservers:\n- url: https://cdcs-api.example.com\npaths:\n /accounts.getAccountInfo:\n get:\n summary: Get Account Info\n parameters:\n - in: query\n name: UID\n schema:\n type: string\n required: true\n description: Unique user ID\n responses:\n '200':\n description: Account object\n content:\n application/json:\n schema:\n $ref: '#/components/schemas/Account'\n /accounts.setAccountInfo:\n post:\n summary: Update Account Info\n requestBody:\n required: true\n content:\n application/x-www-form-urlencoded:\n schema:\n type: object\n properties:\n profile:\n type: string\n communications:\n type: string\n data:\n type: string\n example:\n profile: '{\"firstName\":\"John\",\"lastName\":\"Doe\"}'\n communications: '{\"Marketing_Email\":{\"status\":\"optIn\"}}'\n data: '{\"customField\":\"value\"}'\n responses:\n '200':\n description: Update successful\n '400':\n description: Invalid input\n /accounts.importFullAccount:\n post:\n summary: Import a user account\n description: Imports a new user account with provided profile, login IDs, and\n password hash\n requestBody:\n required: true\n content:\n application/x-www-form-urlencoded:\n schema:\n type: object\n properties:\n profile:\n type: string\n loginIDs:\n type: string\n password:\n type: string\n UID:\n type: string\n example:\n profile: '{\"firstName\":\"Alice\",\"lastName\":\"Smith\"}'\n loginIDs: '{\"email\":\"alice@example.com\"}'\n password: '{\"hash\":\"abc123\",\"hashSettings\":{\"algorithm\":\"sha256\"}}'\n UID: user-001\n responses:\n '200':\n description: Account imported successfully\n '400':\n description: Invalid input\n /accounts.getSchema:\n get:\n summary: Retrieve schema configuration\n responses:\n '200':\n description: Schema definition\n content:\n application/json:\n schema:\n $ref: '#/components/schemas/Schema'\n /accounts.setSchema:\n post:\n summary: Update schema definition\n requestBody:\n required: true\n content:\n application/x-www-form-urlencoded:\n schema:\n type: object\n properties:\n schema:\n type: string\n example:\n schema: '{\"fields\":{\"firstName\":{\"type\":\"string\",\"required\":true}}}'\n responses:\n '200':\n description: Schema updated\n /accounts.search:\n get:\n summary: Search Accounts\n description: Search for accounts using parameters such as email or UID.\n parameters:\n - in: query\n name: email\n schema:\n type: string\n format: email\n required: false\n description: Email address to search for\n - in: query\n name: UID\n schema:\n type: string\n required: false\n description: Specific UID to search\n - in: query\n name: query\n schema:\n type: string\n required: false\n description: Free-form query string\n responses:\n '200':\n description: List of matching accounts\n content:\n application/json:\n schema:\n type: array\n items:\n $ref: '#/components/schemas/Account'\n '400':\n description: Invalid query parameters\ncomponents:\n schemas:\n Account:\n type: object\n properties:\n UID:\n type: string\n isActive:\n type: boolean\n profile:\n $ref: '#/components/schemas/Profile'\n communications:\n $ref: '#/components/schemas/Communications'\n groups:\n type: array\n items:\n type: object\n properties:\n orgId:\n type: string\n roles:\n type: array\n items:\n type: string\n status:\n type: string\n Profile:\n type: object\n properties:\n firstName:\n type: string\n lastName:\n type: string\n email:\n type: string\n format: email\n Communications:\n type: object\n additionalProperties:\n type: object\n properties:\n status:\n type: string\n optIn:\n type: object\n additionalProperties:\n type: string\n Schema:\n type: object\n properties:\n fields:\n type: object\n additionalProperties:\n type: object\n properties:\n type:\n type: string\n required:\n type: boolean\n writeAccess:\n type: string\n allowNull:\n type: boolean\n format:\n type: string\n encrypt:\n type: string",[],[341],{"_104":350,"_97":351,"_161":352,"_163":-5,"_164":146,"_165":353,"_167":118,"_106":354,"_101":355,"_169":190,"_171":356,"_172":22,"_173":-5,"_174":357,"_100":358},"b74e1a96-426f-11f0-89c8-76b3cceeab13","cleanup.tsx","0a13e63e-4225-11f0-9f81-76b3cceeab13",55,["D",1749170803254],6,"// Script to cleanup and reset Gigya DS data (use with caution!)\n\nconst GIGYA_DOMAIN = process.env.GIGYA_DOMAIN || \"accounts.eu1.gigya.com\";\nconst GIGYA_API_KEY = process.env.GIGYA_API_KEY;\nconst GIGYA_APP_KEY = process.env.GIGYA_APP_KEY;\nconst GIGYA_APP_SECRET = process.env.GIGYA_APP_SECRET;\n\nif (!GIGYA_API_KEY || !GIGYA_APP_KEY || !GIGYA_APP_SECRET) {\n console.error(\"Missing Gigya environment variables!\");\n console.log(\"Required variables: GIGYA_API_KEY, GIGYA_APP_KEY, GIGYA_APP_SECRET\");\n process.exit(1);\n}\n\nasync function makeGigyaRequest(endpoint, params) {\n const url = `https://${GIGYA_DOMAIN}/${endpoint}?httpStatusCodes=true`;\n\n const body = new URLSearchParams({\n apiKey: GIGYA_API_KEY,\n userKey: GIGYA_APP_KEY,\n secret: GIGYA_APP_SECRET,\n ...params,\n });\n\n const response = await fetch(url, {\n method: \"POST\",\n headers: { \"Content-Type\": \"application/x-www-form-urlencoded\" },\n body,\n });\n\n if (!response.ok) {\n const text = await response.text();\n throw new Error(`${response.statusText}: ${text}`);\n }\n\n const text = await response.text();\n return JSON.parse(text);\n}\nasync function confirmCleanup() {\n console.log(\"⚠️ WARNING: This script will delete ALL data from Gigya DS!\");\n console.log(\"This action cannot be undone.\");\n console.log(\"\\nTo proceed, you must set the environment variable CONFIRM_CLEANUP=true\");\n\n if (process.env.CONFIRM_CLEANUP !== \"true\") {\n console.log(\"❌ Cleanup not confirmed. Exiting for safety.\");\n process.exit(0);\n }\n\n console.log(\"✅ Cleanup confirmed. Proceeding...\");\n return true;\n}\n\nasync function cleanupDSData() {\n await confirmCleanup();\n\n console.log(\"🧹 Starting Gigya DS data cleanup...\\n\");\n\n try {\n // 1. Get all projects\n console.log(\"1. Fetching all projects...\");\n const searchResponse = await makeGigyaRequest(\"ds.search\", {\n query: \"SELECT * FROM oss_projects\",\n });\n\n if (searchResponse.errorCode !== 0) {\n console.log(\"❌ Failed to fetch projects:\", searchResponse.errorMessage);\n return false;\n }\n\n const projects = searchResponse.results || [];\n console.log(`Found ${projects.length} projects to cleanup`);\n\n if (projects.length === 0) {\n console.log(\"✅ No projects found. Nothing to cleanup.\");\n return true;\n }\n\n // 2. Mark all projects as deleted\n console.log(\"\\n2. Marking projects as deleted...\");\n let deletedCount = 0;\n let errorCount = 0;\n\n for (const project of projects) {\n try {\n const deleteResponse = await makeGigyaRequest(\"ds.delete\", {\n type: \"oss_projects\",\n oid: project.oid,\n });\n\n if (deleteResponse.errorCode === 0) {\n console.log(`✅ Deleted: ${project.data.title}`);\n deletedCount++;\n } else {\n console.log(`❌ Failed to delete ${project.data.title}:`, deleteResponse.errorMessage);\n errorCount++;\n }\n\n // Add delay to avoid rate limiting\n await new Promise((resolve) => setTimeout(resolve, 100));\n } catch (error) {\n console.error(`❌ Error deleting project ${project.data.title}:`, error.message);\n errorCount++;\n }\n }\n\n console.log(`\\n📊 Cleanup Summary:`);\n console.log(`✅ Successfully deleted: ${deletedCount} projects`);\n console.log(`❌ Errors: ${errorCount} projects`);\n\n // 3. Verify cleanup\n console.log(\"\\n3. Verifying cleanup...\");\n const verifyResponse = await makeGigyaRequest(\"ds.search\", {\n query: \"SELECT COUNT(*) FROM oss_projects WHERE deleted != true\",\n });\n\n if (verifyResponse.errorCode === 0) {\n const remainingCount = verifyResponse.totalCount || 0;\n if (remainingCount === 0) {\n console.log(\"✅ Cleanup verification successful: No active projects remaining\");\n } else {\n console.log(`⚠️ Warning: ${remainingCount} active projects still found`);\n }\n }\n\n return true;\n } catch (error) {\n console.error(\"❌ Error during cleanup:\", error.message);\n return false;\n }\n}\n\n// Run the cleanup\ncleanupDSData()\n .then((success) => {\n if (success) {\n console.log(\"\\n🎉 DS data cleanup completed!\");\n console.log(\"\\nNext steps:\");\n console.log(\"1. Run load-projects-to-ds.js to reload fresh data\");\n console.log(\"2. Verify the application works correctly\");\n } else {\n console.log(\"\\n❌ Cleanup failed!\");\n process.exit(1);\n }\n })\n .catch((error) => {\n console.error(\"❌ Cleanup script failed:\", error);\n process.exit(1);\n });",[],[351],{"_104":360,"_97":361,"_161":362,"_163":-5,"_164":146,"_165":363,"_167":118,"_106":364,"_101":365,"_169":190,"_171":366,"_172":22,"_173":-5,"_174":367,"_100":368},"b22b53bc-42dd-11f0-bea7-76b3cceeab13","copy-projects-tods.ts","59080d84-4215-11f0-931e-76b3cceeab13",60,["D",1749218039278],17,"// Script to load projects from data.json into Gigya DS\n\nconst GIGYA_DOMAIN = process.env.GIGYA_DOMAIN || \"accounts.eu1.gigya.com\";\nconst GIGYA_API_KEY = process.env.GIGYA_API_KEY;\nconst GIGYA_APP_KEY = process.env.GIGYA_APP_KEY;\nconst GIGYA_APP_SECRET = process.env.GIGYA_APP_SECRET;\n\nif (!GIGYA_API_KEY || !GIGYA_APP_KEY || !GIGYA_APP_SECRET) {\n console.error(\"Missing Gigya environment variables!\");\n console.log(\"Required variables: GIGYA_API_KEY, GIGYA_APP_KEY, GIGYA_APP_SECRET\");\n process.exit(1);\n}\n\nasync function makeGigyaRequest(endpoint, params) {\n const url = `https://${GIGYA_DOMAIN}/${endpoint}?httpStatusCodes=true`;\n\n const body = new URLSearchParams({\n apiKey: GIGYA_API_KEY,\n userKey: GIGYA_APP_KEY,\n secret: GIGYA_APP_SECRET,\n ...params,\n });\n\n const response = await fetch(url, {\n method: \"POST\",\n headers: { \"Content-Type\": \"application/x-www-form-urlencoded\" },\n body,\n });\n\n if (!response.ok) {\n const text = await response.text();\n throw new Error(`${response.statusText}: ${text}`);\n }\n\n const text = await response.text();\n return JSON.parse(text);\n}\n\n// Helper function to safely ensure a value is an array\nfunction ensureArray(value) {\n if (Array.isArray(value)) {\n return value;\n }\n if (value === null || value === undefined) {\n return [];\n }\n if (typeof value === \"string\") {\n try {\n const parsed = JSON.parse(value);\n return Array.isArray(parsed) ? parsed : [];\n } catch {\n return value\n .split(\",\")\n .map((item) => item.trim())\n .filter(Boolean);\n }\n }\n return [value].filter(Boolean);\n}\n\n// Helper function to normalize project data\nfunction normalizeProjectData(rawProject) {\n if (!rawProject || typeof rawProject !== \"object\") {\n return null;\n }\n\n try {\n const normalized = {\n title: String(rawProject.title || rawProject.projectName || \"Untitled Project\"),\n description: String(rawProject.description || \"No description available\"),\n repositoryUrl: String(rawProject.repositoryUrl || \"#\"),\n votes: Number(rawProject.reactions?.[\"+1\"] || 0) + Number(rawProject.reactions?.[\"heart\"] || 0),\n comments: Number(rawProject.comments) || 0,\n cmmitment: rawProject.timeCommitment && String(rawProject.timeCommitment),\n skills: rawProject.skills && ensureArray(rawProject.skills),\n contribution: rawProject.contribution && String(rawProject.contribution),\n author: rawProject.author?.name ?? String(rawProject.author?.name),\n enabled: Boolean(true),\n createdAt: rawProject.createdAt,\n updatedAt: rawProject.updatedAt,\n };\n\n return normalized;\n } catch (error) {\n console.error(\"Error normalizing project data:\", error);\n return null;\n }\n}\nimport data from \"./data.json\" with { \"type\": \"json\" };\nconsole.log(data);\n\nfunction cabbabCase(str: string): string {\n return str.replaceAll(/[\\W_]+/g, \"-\").toLowerCase();\n}\nconst { projects } = data;\nasync function loadProjectsToDS() {\n console.log(\"Loading projects from data.json to Gigya DS...\");\n\n try {\n // Read the data.json file\n\n if (!projects || !Array.isArray(projects)) {\n throw new Error(\"Invalid data.json format - projects array not found\");\n }\n\n console.log(`Found ${projects.length} projects in data.json`);\n\n let successCount = 0;\n let skipCount = 0;\n let errorCount = 0;\n\n for (const rawProject of projects) {\n try {\n // Skip archived projects\n if (rawProject.labels?.includes(\"os:archive\")) {\n console.log(`⏭️ Skipping archived project: ${rawProject.title}`);\n skipCount++;\n continue;\n }\n\n // Normalize the project data\n const projectData = normalizeProjectData(rawProject);\n\n if (!projectData) {\n console.error(`❌ Failed to normalize project: ${rawProject.title || rawProject.id}`);\n errorCount++;\n continue;\n }\n\n // Check if project already exists\n const oid = cabbabCase(projectData.title);\n\n try {\n const existingResponse = await makeGigyaRequest(\"ds.get\", {\n type: \"oss_projects\",\n oid: oid,\n });\n\n if (\n existingResponse.errorCode === 0\n && existingResponse.object?.data\n && !existingResponse.object.data.deleted\n ) {\n console.log(`⏭️ Project already exists: ${projectData.title}`);\n skipCount++;\n continue;\n }\n } catch (error) {\n // Project doesn't exist, continue with creation\n }\n\n // Store the project in Gigya DS\n const storeResponse = await makeGigyaRequest(\"ds.store\", {\n type: \"oss_projects\",\n data: JSON.stringify(projectData),\n oid: oid,\n });\n\n if (storeResponse.errorCode === 0) {\n console.log(`✅ Successfully loaded: ${projectData.title}`);\n successCount++;\n } else {\n console.error(`❌ Failed to store project ${projectData.title}:`, storeResponse.errorMessage);\n errorCount++;\n }\n\n // Add a small delay to avoid rate limiting\n await new Promise((resolve) => setTimeout(resolve, 100));\n } catch (error) {\n console.error(`❌ Error processing project ${rawProject.title || rawProject.id}:`, error.message);\n errorCount++;\n }\n }\n\n console.log(\"\\n📊 Loading Summary:\");\n console.log(`✅ Successfully loaded: ${successCount} projects`);\n console.log(`⏭️ Skipped: ${skipCount} projects`);\n console.log(`❌ Errors: ${errorCount} projects`);\n console.log(`📁 Total processed: ${successCount + skipCount + errorCount} projects`);\n\n return { successCount, skipCount, errorCount };\n } catch (error) {\n console.error(\"❌ Error loading projects to DS:\", error.message);\n throw error;\n }\n}\n\nasync function verifyLoadedData() {\n console.log(\"\\n🔍 Verifying loaded data...\");\n\n try {\n const response = await makeGigyaRequest(\"ds.search\", {\n query: \"SELECT * FROM oss_projects WHERE deleted != true\",\n });\n\n if (response.errorCode === 0) {\n const count = response.results?.length || 0;\n console.log(`✅ Verification successful: Found ${count} projects in DS`);\n\n if (response.results && response.results.length > 0) {\n console.log(\"\\n📋 Sample projects:\");\n response.results.slice(0, 3).forEach((result, index) => {\n const project = result.data;\n console.log(`${index + 1}. ${project.title} (ID: ${project.id})`);\n });\n }\n } else {\n console.error(\"❌ Verification failed:\", response.errorMessage);\n }\n } catch (error) {\n console.error(\"❌ Error during verification:\", error.message);\n }\n}\n\n// Run the script\nloadProjectsToDS()\n .then(async (result) => {\n if (result.successCount > 0) {\n await verifyLoadedData();\n console.log(\"\\n🎉 Project loading completed successfully!\");\n console.log(\"\\nNext steps:\");\n console.log(\"1. Test the application to ensure projects are loading correctly\");\n console.log(\"2. Verify user voting and assignment functionality\");\n } else {\n console.log(\"\\n⚠️ No projects were loaded successfully!\");\n }\n })\n .catch((error) => {\n console.error(\"❌ Script execution failed:\", error);\n process.exit(1);\n });",[],[361],{"_104":370,"_97":371,"_161":372,"_163":-5,"_164":146,"_165":373,"_167":118,"_106":374,"_101":289,"_169":316,"_171":375,"_172":22,"_173":-5,"_174":376,"_100":377},"8834f28a-425f-11f0-b846-76b3cceeab13","data.json","92f50704-4215-11f0-b622-76b3cceeab13",51,["D",1749163852288],"{\n\n \n \"projects\": [\n {\n \"raw\": \"# bolt.diy\\r\\n\\r\\n### Repository URL\\r\\n\\r\\nhttps://github.com/stackblitz-labs/bolt.diy\\r\\n\\r\\n### Project Description\\r\\n\\r\\nbolt.diy is an open-source platform that enables users to prompt, run, edit, and deploy full-stack web applications directly in the browser using various Large Language Models (LLMs). It supports integration with multiple LLM providers, including OpenAI, Anthropic, HuggingFace, and more. The platform offers features like an integrated terminal, code versioning, and the ability to attach images to prompts, facilitating a seamless AI-powered development experience. \\r\\n\\r\\n\\r\\n### Potential Contribution Areas\\r\\n\\r\\nAgent Collaboration: Enhance bolt.diy to support MCP tool access and A2A-based agent collaboration, fostering better interoperability between SAP agents and bolt.diy projects.\\r\\nSAP Integration: Develop adapters or plugins to integrate bolt.diy with SAP's App Router or Cloud Foundry, enabling seamless deployment of applications within the SAP ecosystem.\\r\\n\\r\\n### Estimated Time Commitment\\r\\n\\r\\nMedium (4-8 hours/week)\\r\\n\\r\\n### Required Skills\\r\\n\\r\\nTypeScript\\r\\n\\r\\n### License\\r\\n\\r\\nMIT\\r\\n\\r\\n### Additional Information\\r\\n\\r\\n_No response_\",\n \"id\": 22,\n \"title\": \"bolt.diy\",\n \"reactions\": {\n \"url\": \"https://github.tools.sap/api/v3/repos/AI-GUILD-IL/os-contribution/issues/22/reactions\",\n \"total_count\": 1,\n \"+1\": 0,\n \"-1\": 0,\n \"laugh\": 0,\n \"hooray\": 0,\n \"confused\": 0,\n \"heart\": 1,\n \"rocket\": 0,\n \"eyes\": 0\n },\n \"labels\": [\n \"os:suggestion\",\n \"os:app-builder\"\n ],\n \"votes\": 1,\n \"comments\": 0,\n \"prerequisites\": {\n \"notDuplicate\": false,\n \"hasLicense\": false,\n \"isActive\": false\n },\n \"author\": {\n \"name\": \"I347305\",\n \"avatar\": \"https://avatars.github.tools.sap/u/39522?\"\n },\n \"createdAt\": \"2025-06-03T12:14:23Z\",\n \"updatedAt\": \"2025-06-03T13:06:02Z\",\n \"languages\": [],\n \"projectName\": \"\",\n \"repositoryUrl\": \"https://github.com/stackblitz-labs/bolt.diy\",\n \"description\": \"bolt.diy is an open-source platform that enables users to prompt, run, edit, and deploy full-stack web applications directly in the browser using various Large Language Models (LLMs). It supports integration with multiple LLM providers, including OpenAI, Anthropic, HuggingFace, and more. The platform offers features like an integrated terminal, code versioning, and the ability to attach images to prompts, facilitating a seamless AI-powered development experience.\",\n \"contribution\": \"Agent Collaboration: Enhance bolt.diy to support MCP tool access and A2A-based agent collaboration, fostering better interoperability between SAP agents and bolt.diy projects.\\r\\nSAP Integration: Develop adapters or plugins to integrate bolt.diy with SAP's App Router or Cloud Foundry, enabling seamless deployment of applications within the SAP ecosystem.\",\n \"timeCommitment\": \"Medium (4-8 hours/week)\",\n \"skills\": [\n \"TypeScript\"\n ],\n \"license\": \"MIT\",\n \"additionalInfo\": \"_No response_\",\n \"highlights\": \"\"\n },\n {\n \"raw\": \"### Project Name\\n\\nDevstral_FT\\n\\n### Repository URL\\n\\nhttps://github.TBD/org-name/sap-tuned-devstral\\n\\n### Project Description\\n\\nProblem Statement/Motivation: 🎯\\r\\nCurrently, leveraging Large Language Models (LLMs) for code assistance, generation, and understanding often involves sending proprietary code to third-party services. This presents potential privacy and security concerns. Additionally, reliance on external services can introduce latency and lacks offline capabilities.\\r\\n\\r\\nOur services extensive codebase, contained within our Git repositories, represents a valuable dataset. Fine-tuning a capable open-source model like Devstral specifically on our code could provide a highly contextualized, fast, and private LLM assistant. This would empower developers with tailored code suggestions, explanations, and generation capabilities directly within their local development environment.\\r\\n\\r\\nGoals/Acceptance Criteria: ✅\\r\\n\\r\\nSuccessfully fine-tune a version of the Devstral model on a selected subset of our team's Git repositories.\\r\\nThe fine-tuned model can be run locally using Ollama on a typical developer machine with acceptable performance (e.g., response time for suggestions < 1-2 seconds).\\r\\nDevelopers can query the local model from VS Code (e.g., via a compatible extension like Continue or a similar tool) for:\\r\\nCode completion/suggestion relevant to our codebase.\\r\\nExplaining snippets of our proprietary code.\\r\\nGenerating boilerplate or utility functions based on our coding patterns.\\r\\nThe entire process maintains data privacy by keeping our codebase and the fine-tuned model strictly within our local/private infrastructure.\\r\\nDocumentation is created for setting up and using the local LLM.\\r\\n\\r\\n\\r\\nHigh-Level Tasks: 🛠️\\r\\n\\r\\n[ ] Research & Planning:\\r\\n[ ] Identify suitable Git repositories and branches for the training dataset.\\r\\n[ ] Research best practices for preparing code data for fine-tuning (e.g., filtering, formatting, anonymization if needed).\\r\\n[ ] Evaluate hardware requirements for fine-tuning and local inference.\\r\\n[ ] Investigate and select the most appropriate VS Code plugin(s) for Ollama integration.\\r\\n\\r\\n[ ] Data Preparation:\\r\\n[ ] Clone selected repositories.\\r\\n[ ] Implement scripts to clean, preprocess, and format the code data.\\r\\n\\r\\n[ ] Model Fine-Tuning:\\r\\n[ ] Set up the fine-tuning environment for Devstral.\\r\\n[ ] Perform initial fine-tuning runs and iterate on parameters.\\r\\n[ ] Evaluate the performance and quality of the fine-tuned model.\\r\\n\\r\\n[ ] Deployment & Integration:\\r\\n[ ] Package the fine-tuned model for Ollama.\\r\\n[ ] Develop instructions for team members to install Ollama and the custom model.\\r\\n[ ] Configure VS Code plugin(s) to connect to the local Ollama instance.\\r\\n\\r\\n[ ] Testing & Feedback:\\r\\n[ ] Conduct internal testing with the development team.\\r\\n[ ] Gather feedback and iterate on the model/setup.\\r\\n\\r\\n[ ] Documentation:\\r\\n[ ] Create user guides for setup and usage.\\r\\n[ ] Document the fine-tuning process for future reference.\\r\\n\\r\\n\\r\\nConsiderations/Potential Challenges: 🤔\\r\\nData Volume & Quality: Ensuring enough high-quality, representative code is used for effective fine-tuning.\\r\\nComputational Resources: Fine-tuning can be resource-intensive. We need to assess if local machines are sufficient or if a dedicated training server is needed.\\r\\nModel Performance: Achieving a good balance between model size, inference speed, and the quality of assistance.\\r\\nMaintenance: The model may need to be periodically retrained as the codebase evolves.\\n\\n### Potential Contribution Areas\\n\\n_No response_\\n\\n### Estimated Time Commitment\\n\\nMedium (4-8 hours/week)\\n\\n### Required Skills\\n\\n_No response_\\n\\n### License\\n\\n_No response_\\n\\n### Additional Information\\n\\n_No response_\",\n \"id\": 27,\n \"title\": \"🚀 Project: Fine-tune Devstral for Local, Private Code Assistance via Ollama & VS Code\",\n \"reactions\": {\n \"url\": \"https://github.tools.sap/api/v3/repos/AI-GUILD-IL/os-contribution/issues/27/reactions\",\n \"total_count\": 0,\n \"+1\": 0,\n \"-1\": 0,\n \"laugh\": 0,\n \"hooray\": 0,\n \"confused\": 0,\n \"heart\": 0,\n \"rocket\": 0,\n \"eyes\": 0\n },\n \"labels\": [\n \"os:suggestion\"\n ],\n \"votes\": 0,\n \"comments\": 0,\n \"prerequisites\": {\n \"notDuplicate\": false,\n \"hasLicense\": false,\n \"isActive\": false\n },\n \"author\": {\n \"name\": \"I500695\",\n \"avatar\": \"https://avatars.github.tools.sap/u/19453?\"\n },\n \"createdAt\": \"2025-06-03T15:03:49Z\",\n \"updatedAt\": \"2025-06-03T15:03:49Z\",\n \"languages\": [],\n \"projectName\": \"Devstral_FT\",\n \"repositoryUrl\": \"https://github.TBD/org-name/sap-tuned-devstral\",\n \"description\": \"Problem Statement/Motivation: 🎯\\r\\nCurrently, leveraging Large Language Models (LLMs) for code assistance, generation, and understanding often involves sending proprietary code to third-party services. This presents potential privacy and security concerns. Additionally, reliance on external services can introduce latency and lacks offline capabilities.\\r\\n\\r\\nOur services extensive codebase, contained within our Git repositories, represents a valuable dataset. Fine-tuning a capable open-source model like Devstral specifically on our code could provide a highly contextualized, fast, and private LLM assistant. This would empower developers with tailored code suggestions, explanations, and generation capabilities directly within their local development environment.\\r\\n\\r\\nGoals/Acceptance Criteria: ✅\\r\\n\\r\\nSuccessfully fine-tune a version of the Devstral model on a selected subset of our team's Git repositories.\\r\\nThe fine-tuned model can be run locally using Ollama on a typical developer machine with acceptable performance (e.g., response time for suggestions < 1-2 seconds).\\r\\nDevelopers can query the local model from VS Code (e.g., via a compatible extension like Continue or a similar tool) for:\\r\\nCode completion/suggestion relevant to our codebase.\\r\\nExplaining snippets of our proprietary code.\\r\\nGenerating boilerplate or utility functions based on our coding patterns.\\r\\nThe entire process maintains data privacy by keeping our codebase and the fine-tuned model strictly within our local/private infrastructure.\\r\\nDocumentation is created for setting up and using the local LLM.\\r\\n\\r\\n\\r\\nHigh-Level Tasks: 🛠️\\r\\n\\r\\n[ ] Research & Planning:\\r\\n[ ] Identify suitable Git repositories and branches for the training dataset.\\r\\n[ ] Research best practices for preparing code data for fine-tuning (e.g., filtering, formatting, anonymization if needed).\\r\\n[ ] Evaluate hardware requirements for fine-tuning and local inference.\\r\\n[ ] Investigate and select the most appropriate VS Code plugin(s) for Ollama integration.\\r\\n\\r\\n[ ] Data Preparation:\\r\\n[ ] Clone selected repositories.\\r\\n[ ] Implement scripts to clean, preprocess, and format the code data.\\r\\n\\r\\n[ ] Model Fine-Tuning:\\r\\n[ ] Set up the fine-tuning environment for Devstral.\\r\\n[ ] Perform initial fine-tuning runs and iterate on parameters.\\r\\n[ ] Evaluate the performance and quality of the fine-tuned model.\\r\\n\\r\\n[ ] Deployment & Integration:\\r\\n[ ] Package the fine-tuned model for Ollama.\\r\\n[ ] Develop instructions for team members to install Ollama and the custom model.\\r\\n[ ] Configure VS Code plugin(s) to connect to the local Ollama instance.\\r\\n\\r\\n[ ] Testing & Feedback:\\r\\n[ ] Conduct internal testing with the development team.\\r\\n[ ] Gather feedback and iterate on the model/setup.\\r\\n\\r\\n[ ] Documentation:\\r\\n[ ] Create user guides for setup and usage.\\r\\n[ ] Document the fine-tuning process for future reference.\\r\\n\\r\\n\\r\\nConsiderations/Potential Challenges: 🤔\\r\\nData Volume & Quality: Ensuring enough high-quality, representative code is used for effective fine-tuning.\\r\\nComputational Resources: Fine-tuning can be resource-intensive. We need to assess if local machines are sufficient or if a dedicated training server is needed.\\r\\nModel Performance: Achieving a good balance between model size, inference speed, and the quality of assistance.\\r\\nMaintenance: The model may need to be periodically retrained as the codebase evolves.\",\n \"contribution\": \"_No response_\",\n \"timeCommitment\": \"Medium (4-8 hours/week)\",\n \"skills\": [],\n \"license\": \"_No response_\",\n \"additionalInfo\": \"_No response_\",\n \"highlights\": \"\"\n },\n {\n \"raw\": \"### Project Name\\n\\nCVE Mitigator\\n\\n### Repository URL\\n\\nhttps://github.com/sap-samples/cve-mitigator\\n\\n### Project Description\\n\\nCVE Mitigator is a developer-focused tool designed to automate the mitigation workflow for Common Vulnerabilities and Exposures (CVEs) detected in SAP development environments. It connects to SAP’s security scanning tools (e.g. Whitesource), fetches detected vulnerabilities, and intelligently maps them to affected source code in Git-based repositories. Leveraging AI-assisted suggestions, the tool proposes relevant code changes, library upgrades, or configuration fixes. This dramatically reduces mean-time-to-remediate (MTTR) and enhances security response efficiency across SAP projects. The tool can be used as a CLI utility, GitHub bot, or CI pipeline integration.\\n\\n### Potential Contribution Areas\\n\\n_No response_\\n\\n### Estimated Time Commitment\\n\\nMedium (4-8 hours/week)\\n\\n### Required Skills\\n\\n_No response_\\n\\n### License\\n\\n_No response_\\n\\n### Additional Information\\n\\n_No response_\",\n \"id\": 26,\n \"title\": \"CVE Mitigator\",\n \"reactions\": {\n \"url\": \"https://github.tools.sap/api/v3/repos/AI-GUILD-IL/os-contribution/issues/26/reactions\",\n \"total_count\": 0,\n \"+1\": 0,\n \"-1\": 0,\n \"laugh\": 0,\n \"hooray\": 0,\n \"confused\": 0,\n \"heart\": 0,\n \"rocket\": 0,\n \"eyes\": 0\n },\n \"labels\": [\n \"os:suggestion\"\n ],\n \"votes\": 0,\n \"comments\": 0,\n \"prerequisites\": {\n \"notDuplicate\": false,\n \"hasLicense\": false,\n \"isActive\": false\n },\n \"author\": {\n \"name\": \"I074921\",\n \"avatar\": \"https://avatars.github.tools.sap/u/6395?\"\n },\n \"createdAt\": \"2025-06-03T14:40:59Z\",\n \"updatedAt\": \"2025-06-03T14:41:00Z\",\n \"languages\": [],\n \"projectName\": \"CVE Mitigator\",\n \"repositoryUrl\": \"https://github.com/sap-samples/cve-mitigator\",\n \"description\": \"CVE Mitigator is a developer-focused tool designed to automate the mitigation workflow for Common Vulnerabilities and Exposures (CVEs) detected in SAP development environments. It connects to SAP’s security scanning tools (e.g. Whitesource), fetches detected vulnerabilities, and intelligently maps them to affected source code in Git-based repositories. Leveraging AI-assisted suggestions, the tool proposes relevant code changes, library upgrades, or configuration fixes. This dramatically reduces mean-time-to-remediate (MTTR) and enhances security response efficiency across SAP projects. The tool can be used as a CLI utility, GitHub bot, or CI pipeline integration.\",\n \"contribution\": \"_No response_\",\n \"timeCommitment\": \"Medium (4-8 hours/week)\",\n \"skills\": [],\n \"license\": \"_No response_\",\n \"additionalInfo\": \"_No response_\",\n \"highlights\": \"\"\n },\n {\n \"raw\": \"### Project Name\\n\\nJira Support Agent\\n\\n### Repository URL\\n\\nhttps://github.TBD/org-name/support-agent-jira\\n\\n### Project Description\\n\\nThe Support Agent (Jira) is an AI-powered automation tool that enhances support ticket triaging and stakeholder communication within Jira. It intelligently analyzes incoming tickets to assign them to the correct teams, apply relevant tags and labels, and post contextual comments when information is missing. The agent is designed to improve operational efficiency, reduce human error, and ensure faster turnaround times by streamlining the first-touch resolution process in enterprise support workflows.\\n\\n### Potential Contribution Areas\\n\\n- NLP Integration: Improve natural language understanding to better classify and route tickets based on intent and content.\\r\\n- Custom Workflows: Develop rule-based or LLM-based flows for specific Jira projects or support queues.\\r\\n- Stakeholder Interaction: Enhance the agent’s comment generation to ask for missing information in a context-aware, human-like manner.\\r\\n- Jira API Enhancements: Extend the agent’s capabilities to support bulk operations, custom fields, and integration with other Atlassian tools (e.g., Confluence, Opsgenie).\\n\\n### Estimated Time Commitment\\n\\nLow (1-3 hours/week)\\n\\n### Required Skills\\n\\n_No response_\\n\\n### License\\n\\n_No response_\\n\\n### Additional Information\\n\\n_No response_\",\n \"id\": 25,\n \"title\": \"Jira Support Agent\",\n \"reactions\": {\n \"url\": \"https://github.tools.sap/api/v3/repos/AI-GUILD-IL/os-contribution/issues/25/reactions\",\n \"total_count\": 0,\n \"+1\": 0,\n \"-1\": 0,\n \"laugh\": 0,\n \"hooray\": 0,\n \"confused\": 0,\n \"heart\": 0,\n \"rocket\": 0,\n \"eyes\": 0\n },\n \"labels\": [\n \"os:suggestion\"\n ],\n \"votes\": 0,\n \"comments\": 0,\n \"prerequisites\": {\n \"notDuplicate\": false,\n \"hasLicense\": false,\n \"isActive\": false\n },\n \"author\": {\n \"name\": \"I355895\",\n \"avatar\": \"https://avatars.github.tools.sap/u/8901?\"\n },\n \"createdAt\": \"2025-06-03T14:28:06Z\",\n \"updatedAt\": \"2025-06-03T14:28:06Z\",\n \"languages\": [],\n \"projectName\": \"Jira Support Agent\",\n \"repositoryUrl\": \"https://github.TBD/org-name/support-agent-jira\",\n \"description\": \"The Support Agent (Jira) is an AI-powered automation tool that enhances support ticket triaging and stakeholder communication within Jira. It intelligently analyzes incoming tickets to assign them to the correct teams, apply relevant tags and labels, and post contextual comments when information is missing. The agent is designed to improve operational efficiency, reduce human error, and ensure faster turnaround times by streamlining the first-touch resolution process in enterprise support workflows.\",\n \"contribution\": \"- NLP Integration: Improve natural language understanding to better classify and route tickets based on intent and content.\\r\\n- Custom Workflows: Develop rule-based or LLM-based flows for specific Jira projects or support queues.\\r\\n- Stakeholder Interaction: Enhance the agent’s comment generation to ask for missing information in a context-aware, human-like manner.\\r\\n- Jira API Enhancements: Extend the agent’s capabilities to support bulk operations, custom fields, and integration with other Atlassian tools (e.g., Confluence, Opsgenie).\",\n \"timeCommitment\": \"Low (1-3 hours/week)\",\n \"skills\": [],\n \"license\": \"_No response_\",\n \"additionalInfo\": \"_No response_\",\n \"highlights\": \"\"\n },\n {\n \"raw\": \"### Project Name\\n\\nSoftware Dependency Upgrade Agent\\n\\n### Repository URL\\n\\nhttps://githubTBD/org-name/dependency-upgrade-agent\\n\\n### Project Description\\n\\nThe Software Dependency Upgrade Agent is an intelligent automation tool designed to monitor and upgrade outdated dependencies in internal codebases. It works across various project types (Node.js, Python, Java, etc.), detecting outdated libraries, proposing or applying version upgrades, validating compatibility, and optionally opening merge requests. Integrated with Git and CI pipelines, the agent reduces tech debt and security risks while saving developer time. Its pluggable design allows easy adaptation to organizational policies and internal registries.\\n\\n### Potential Contribution Areas\\n\\n- Language Support: Extend support for additional languages and package managers (e.g., Maven, pip, Cargo).\\r\\n- Smart Upgrade Logic: Implement AI-based changelog analysis to flag breaking changes or suggest semantic versioning strategies.\\r\\n- CI/CD Integration: Build adapters for CI tools like GitHub Actions, GitLab CI, or SAP CI/CD service to run upgrades and tests automatically.\\r\\n- Custom Policies: Enable configuration of internal upgrade policies (e.g., allow minor upgrades only, require code owners' review).\\n\\n### Estimated Time Commitment\\n\\nLow (1-3 hours/week)\\n\\n### Required Skills\\n\\n_No response_\\n\\n### License\\n\\n_No response_\\n\\n### Additional Information\\n\\n_No response_\",\n \"id\": 24,\n \"title\": \"Software Dependency Upgrade Agent\",\n \"reactions\": {\n \"url\": \"https://github.tools.sap/api/v3/repos/AI-GUILD-IL/os-contribution/issues/24/reactions\",\n \"total_count\": 0,\n \"+1\": 0,\n \"-1\": 0,\n \"laugh\": 0,\n \"hooray\": 0,\n \"confused\": 0,\n \"heart\": 0,\n \"rocket\": 0,\n \"eyes\": 0\n },\n \"labels\": [\n \"os:suggestion\"\n ],\n \"votes\": 0,\n \"comments\": 0,\n \"prerequisites\": {\n \"notDuplicate\": false,\n \"hasLicense\": false,\n \"isActive\": false\n },\n \"author\": {\n \"name\": \"I355895\",\n \"avatar\": \"https://avatars.github.tools.sap/u/8901?\"\n },\n \"createdAt\": \"2025-06-03T14:26:31Z\",\n \"updatedAt\": \"2025-06-03T14:26:31Z\",\n \"languages\": [],\n \"projectName\": \"Software Dependency Upgrade Agent\",\n \"repositoryUrl\": \"https://githubTBD/org-name/dependency-upgrade-agent\",\n \"description\": \"The Software Dependency Upgrade Agent is an intelligent automation tool designed to monitor and upgrade outdated dependencies in internal codebases. It works across various project types (Node.js, Python, Java, etc.), detecting outdated libraries, proposing or applying version upgrades, validating compatibility, and optionally opening merge requests. Integrated with Git and CI pipelines, the agent reduces tech debt and security risks while saving developer time. Its pluggable design allows easy adaptation to organizational policies and internal registries.\",\n \"contribution\": \"- Language Support: Extend support for additional languages and package managers (e.g., Maven, pip, Cargo).\\r\\n- Smart Upgrade Logic: Implement AI-based changelog analysis to flag breaking changes or suggest semantic versioning strategies.\\r\\n- CI/CD Integration: Build adapters for CI tools like GitHub Actions, GitLab CI, or SAP CI/CD service to run upgrades and tests automatically.\\r\\n- Custom Policies: Enable configuration of internal upgrade policies (e.g., allow minor upgrades only, require code owners' review).\",\n \"timeCommitment\": \"Low (1-3 hours/week)\",\n \"skills\": [],\n \"license\": \"_No response_\",\n \"additionalInfo\": \"_No response_\",\n \"highlights\": \"\"\n },\n {\n \"raw\": \"### Project Name\\n\\nLLM Proxy Server for SAP AI Core\\n\\n### Repository URL\\n\\nhttps://github.com/sap-samples/llm-proxy-sap-ai-core\\n\\n### Project Description\\n\\nThe LLM Proxy Server for SAP AI Core is an open-source project designed to serve as a lightweight, performant, and extensible intermediary between SAP AI Core and a variety of large language model (LLM) backends. Inspired by solutions like LightLLM, this proxy server standardizes interactions with different model providers (OpenAI, Anthropic, HuggingFace, etc.), handles rate limiting and caching, and simplifies integration for enterprise use cases. Its purpose is to provide a scalable, multi-tenant LLM gateway that plugs seamlessly into the SAP AI Core inference pipeline.\\n\\n### Potential Contribution Areas\\n\\n- Model Adapter Layer: Implement new adapters to support additional LLM providers or fine-tuned models hosted on SAP AI Core.\\r\\n- Request Routing & Optimization: Improve routing logic, caching strategies, and load balancing between LLM providers.\\r\\n- Security & Multi-Tenancy: Enhance authentication, logging, and quota management to support secure, tenant-aware deployments.\\r\\n- SAP Integration: Develop SDK components or API contracts to enable easy consumption of the proxy within SAP BTP-based applications.\\n\\n### Estimated Time Commitment\\n\\nMedium (4-8 hours/week)\\n\\n### Required Skills\\n\\n_No response_\\n\\n### License\\n\\n_No response_\\n\\n### Additional Information\\n\\n_No response_\",\n \"id\": 23,\n \"title\": \"LLM Proxy Server for SAP AI Core\",\n \"reactions\": {\n \"url\": \"https://github.tools.sap/api/v3/repos/AI-GUILD-IL/os-contribution/issues/23/reactions\",\n \"total_count\": 1,\n \"+1\": 1,\n \"-1\": 0,\n \"laugh\": 0,\n \"hooray\": 0,\n \"confused\": 0,\n \"heart\": 0,\n \"rocket\": 0,\n \"eyes\": 0\n },\n \"labels\": [\n \"os:suggestion\"\n ],\n \"votes\": 1,\n \"comments\": 0,\n \"prerequisites\": {\n \"notDuplicate\": false,\n \"hasLicense\": false,\n \"isActive\": false\n },\n \"author\": {\n \"name\": \"I355895\",\n \"avatar\": \"https://avatars.github.tools.sap/u/8901?\"\n },\n \"createdAt\": \"2025-06-03T14:25:01Z\",\n \"updatedAt\": \"2025-06-03T14:25:01Z\",\n \"languages\": [],\n \"projectName\": \"LLM Proxy Server for SAP AI Core\",\n \"repositoryUrl\": \"https://github.com/sap-samples/llm-proxy-sap-ai-core\",\n \"description\": \"The LLM Proxy Server for SAP AI Core is an open-source project designed to serve as a lightweight, performant, and extensible intermediary between SAP AI Core and a variety of large language model (LLM) backends. Inspired by solutions like LightLLM, this proxy server standardizes interactions with different model providers (OpenAI, Anthropic, HuggingFace, etc.), handles rate limiting and caching, and simplifies integration for enterprise use cases. Its purpose is to provide a scalable, multi-tenant LLM gateway that plugs seamlessly into the SAP AI Core inference pipeline.\",\n \"contribution\": \"- Model Adapter Layer: Implement new adapters to support additional LLM providers or fine-tuned models hosted on SAP AI Core.\\r\\n- Request Routing & Optimization: Improve routing logic, caching strategies, and load balancing between LLM providers.\\r\\n- Security & Multi-Tenancy: Enhance authentication, logging, and quota management to support secure, tenant-aware deployments.\\r\\n- SAP Integration: Develop SDK components or API contracts to enable easy consumption of the proxy within SAP BTP-based applications.\",\n \"timeCommitment\": \"Medium (4-8 hours/week)\",\n \"skills\": [],\n \"license\": \"_No response_\",\n \"additionalInfo\": \"_No response_\",\n \"highlights\": \"\"\n },\n {\n \"raw\": \"### Project Name\\n\\n_No response_\\n\\n### Repository URL\\n\\nhttps://github.com/BerriAI/litellm\\n\\n### Project Description\\n\\nknown proxy for several tools (used by high volume projects such as aidr/claude code/cline/etc)\\n\\n### Potential Contribution Areas\\n\\nsupport sap core ai in lite llm which can be generic solution for all the tools that we want to support core ai\\r\\n\\r\\nnote: someone from sap already started to work on it: https://github.com/mbrner/litellm/tree/main/litellm/llms/sap/chat\\n\\n### Estimated Time Commitment\\n\\nMedium (4-8 hours/week)\\n\\n### Required Skills\\n\\nPython, Prompt Engineering\\n\\n### License\\n\\n_No response_\\n\\n### Additional Information\\n\\n_No response_\",\n \"id\": 21,\n \"title\": \"litellm\",\n \"reactions\": {\n \"url\": \"https://github.tools.sap/api/v3/repos/AI-GUILD-IL/os-contribution/issues/21/reactions\",\n \"total_count\": 1,\n \"+1\": 1,\n \"-1\": 0,\n \"laugh\": 0,\n \"hooray\": 0,\n \"confused\": 0,\n \"heart\": 0,\n \"rocket\": 0,\n \"eyes\": 0\n },\n \"labels\": [\n \"os:suggestion\"\n ],\n \"votes\": 1,\n \"comments\": 1,\n \"prerequisites\": {\n \"notDuplicate\": false,\n \"hasLicense\": false,\n \"isActive\": false\n },\n \"author\": {\n \"name\": \"I538157\",\n \"avatar\": \"https://avatars.github.tools.sap/u/22102?\"\n },\n \"createdAt\": \"2025-05-26T15:41:06Z\",\n \"updatedAt\": \"2025-05-26T15:41:16Z\",\n \"languages\": [],\n \"projectName\": \"_No response_\",\n \"repositoryUrl\": \"https://github.com/BerriAI/litellm\",\n \"description\": \"known proxy for several tools (used by high volume projects such as aidr/claude code/cline/etc)\",\n \"contribution\": \"support sap core ai in lite llm which can be generic solution for all the tools that we want to support core ai\\r\\n\\r\\nnote: someone from sap already started to work on it: https://github.com/mbrner/litellm/tree/main/litellm/llms/sap/chat\",\n \"timeCommitment\": \"Medium (4-8 hours/week)\",\n \"skills\": [\n \"Python\",\n \"Prompt Engineering\"\n ],\n \"license\": \"_No response_\",\n \"additionalInfo\": \"_No response_\",\n \"highlights\": \"\"\n },\n {\n \"raw\": \"# 📌 OpenDevin\\r\\n \\r\\n ## 🔗 Repository URL \\r\\n https://github.com/OpenDevin/OpenDevin\\r\\n \\r\\n ## 🧠 Project Description \\r\\n Open-source autonomous software engineer focused on building full dev environments and tasks.\\r\\n \\r\\n ## 🧩 Interoperability: Agent & Tool Protocol Fit \\r\\n Ideal candidate for MCP to unify tooling access (e.g. terminals, file systems) and A2A to interoperate with external agents (e.g. testers, reviewers).\\r\\n \\r\\n ## 🛠️ How AI Guild Can Contribute \\r\\n - Modularize tasks using A2A to break software dev flow into subprocesses\\r\\n - Create devops MCP tool for CF deployment automation\\r\\n - Align agents with SAP’s internal CLI tools (btp CLI)\\r\\n \\r\\n ## 🕒 Estimated Time Commitment \\r\\n Medium (4-8 hours/week)\\r\\n \\r\\n ## 🧪 Required Skills \\r\\n Python, TypeScript, DevOps Automation, LLMs\\r\\n\\r\\n ## 🔑 SAP Relevance \\r\\n - Modularize tasks using A2A to break software dev flow into subprocesses\\r\\n- Create devops MCP tool for CF deployment automation\\r\\n- Align agents with SAP’s internal CLI tools (btp CLI)\\r\\n \\r\\n ## ⚖️ License \\r\\n \\r\\n \\r\\n ---\\r\\n \\r\\n ## 💬 Additional Information \\r\\n \\r\\n \\r\\n 📎 Linked source: `OpenDevin.json`\\r\\n \",\n \"id\": 20,\n \"title\": \"OpenDevin\",\n \"reactions\": {\n \"url\": \"https://github.tools.sap/api/v3/repos/AI-GUILD-IL/os-contribution/issues/20/reactions\",\n \"total_count\": 0,\n \"+1\": 0,\n \"-1\": 0,\n \"laugh\": 0,\n \"hooray\": 0,\n \"confused\": 0,\n \"heart\": 0,\n \"rocket\": 0,\n \"eyes\": 0\n },\n \"labels\": [\n \"os:suggestion\"\n ],\n \"votes\": 0,\n \"comments\": 0,\n \"prerequisites\": {\n \"notDuplicate\": false,\n \"hasLicense\": false,\n \"isActive\": false\n },\n \"author\": {\n \"name\": \"osvote[bot]\",\n \"avatar\": \"https://avatars.github.tools.sap/u/39522?\"\n },\n \"createdAt\": \"2025-05-15T20:10:06Z\",\n \"updatedAt\": \"2025-05-26T16:15:59Z\",\n \"languages\": [],\n \"projectName\": \"\",\n \"repositoryUrl\": \"\",\n \"description\": \"\",\n \"contribution\": \"\",\n \"timeCommitment\": \"\",\n \"skills\": [],\n \"license\": \"\",\n \"additionalInfo\": \"\",\n \"highlights\": \"\"\n },\n {\n \"raw\": \"# Continue\\r\\n \\r\\n ## 🔗 Repository URL \\r\\n https://github.com/continuedev/continue\\r\\n \\r\\n ## 🧠 Project Description \\r\\n Open-source VS Code/JetBrains extension for AI pair programming and agentic editing.\\r\\n \\r\\n ## 🧩 Interoperability: Agent & Tool Protocol Fit \\r\\n Could benefit from A2A to collaborate with remote agents (e.g. testers, doc agents) and MCP to fetch standardized tool or context data (e.g. bug reports, CI results).\\r\\n \\r\\n ## 🛠️ How AI Guild Can Contribute \\r\\n - Add SAP authorization to Continue editor agent\\r\\n - Write MCP plugin to fetch dev logs or issues from SAP ecosystem\\r\\n - Integrate with SAP application studio\\r\\n - Add diffrent SAP context providers\\r\\n - Build AI reviewer that uses A2A to consult SAP coding guidelines\\r\\n\\r\\n ## 🕒 Estimated Time Commitment \\r\\n Medium (4-8 hours/week)\\r\\n\\r\\n \\r\\n ## 🧪 Required Skills \\r\\n TypeScript, VS Code Extensions, Python, LLM Integration\\r\\n\\r\\n \\r\\n ## ⚖️ License \\r\\n \\r\\n \\r\\n ---\\r\\n \\r\\n ## 💬 Additional Information \\r\\n \\r\\n \\r\\n 📎 Linked source: `Continue.json`\\r\\n \",\n \"id\": 19,\n \"title\": \"Continue\",\n \"description\": \"Continue is an IDE Assistant designed to enhance the coding experience by providing support and suggestions directly within the integrated development environment. It aims to streamline the coding process, making it easier for developers to write, debug, and optimize their code without switching contexts. This tool is open source, allowing for community contributions and improvements, and it is not a no-code solution, indicating that it is intended for users who are comfortable with coding.\",\n \"reactions\": {\n \"url\": \"https://github.tools.sap/api/v3/repos/AI-GUILD-IL/os-contribution/issues/19/reactions\",\n \"total_count\": 1,\n \"+1\": 1,\n \"-1\": 0,\n \"laugh\": 0,\n \"hooray\": 0,\n \"confused\": 0,\n \"heart\": 0,\n \"rocket\": 0,\n \"eyes\": 0\n },\n \"labels\": [\n \"os:suggestion\",\n \"os:smart-ide\"\n ],\n \"votes\": 1,\n \"comments\": 0,\n \"prerequisites\": {\n \"notDuplicate\": false,\n \"hasLicense\": false,\n \"isActive\": false\n },\n \"author\": {\n \"name\": \"osvote[bot]\",\n \"avatar\": \"https://avatars.github.tools.sap/u/39522?\"\n },\n \"createdAt\": \"2025-05-15T20:10:05Z\",\n \"updatedAt\": \"2025-06-03T13:10:38Z\",\n \"languages\": [],\n \"projectName\": \"\",\n \"repositoryUrl\": \"\",\n \"description\": \"\",\n \"contribution\": \"\",\n \"timeCommitment\": \"\",\n \"skills\": [],\n \"license\": \"\",\n \"additionalInfo\": \"\",\n \"highlights\": \"\"\n },\n {\n \"raw\": \"# code-sandbox-mcp\\r\\n \\r\\n ## 🔗 Repository URL \\r\\n https://github.com/Automata-Labs-team/code-sandbox-mcp\\r\\n \\r\\n ## 🧠 Project Description \\r\\n Code sandbox tool server implementing MCP, built for AI agents to execute code in a safe environment.\\r\\n \\r\\n ## 🧩 Interoperability: Agent & Tool Protocol Fit \\r\\n Implements MCP directly; useful as a tool server for any agent using MCP. Could benefit from hardening, tests, extensions.\\r\\n \\r\\n ## 🛠️ How AI Guild Can Contribute \\r\\n - Integrate with CloudFundry/ Kyma runtime\\r\\n - Secure sandbox with SA identity in multi-agent flows\\r\\n\\r\\n ## 🕒 Estimated Time Commitment \\r\\n Medium (4-8 hours/week)\\r\\n\\r\\n \\r\\n ## 🧪 Required Skills \\r\\n Python, Docker, MCP, Security\\r\\n\\r\\n ## 🔑 SAP Relevance \\r\\n \\r\\n ## ⚖️ License \\r\\n \\r\\n \\r\\n ---\\r\\n \\r\\n ## 💬 Additional Information \\r\\n \\r\\n \\r\\n 📎 Linked source: `code-sandbox-mcp.json`\\r\\n \",\n \"id\": 18,\n \"title\": \"code-sandbox-mcp\",\n \"reactions\": {\n \"url\": \"https://github.tools.sap/api/v3/repos/AI-GUILD-IL/os-contribution/issues/18/reactions\",\n \"total_count\": 0,\n \"+1\": 0,\n \"-1\": 0,\n \"laugh\": 0,\n \"hooray\": 0,\n \"confused\": 0,\n \"heart\": 0,\n \"rocket\": 0,\n \"eyes\": 0\n },\n \"labels\": [\n \"os:suggestion\"\n ],\n \"votes\": 0,\n \"comments\": 0,\n \"prerequisites\": {\n \"notDuplicate\": false,\n \"hasLicense\": false,\n \"isActive\": false\n },\n \"author\": {\n \"name\": \"osvote[bot]\",\n \"avatar\": \"https://avatars.github.tools.sap/u/39522?\"\n },\n \"createdAt\": \"2025-05-15T20:10:05Z\",\n \"updatedAt\": \"2025-05-26T16:19:31Z\",\n \"languages\": [],\n \"projectName\": \"\",\n \"repositoryUrl\": \"\",\n \"description\": \"\",\n \"contribution\": \"\",\n \"timeCommitment\": \"\",\n \"skills\": [],\n \"license\": \"\",\n \"additionalInfo\": \"\",\n \"highlights\": \"\"\n },\n {\n \"raw\": \" **Semantic Kernel**\\r\\n \\r\\n ## 🔗 Repository URL \\r\\n https://github.com/microsoft/semantic-kernel\\r\\n \\r\\n ## 🧠 Project Description \\r\\n Lightweight orchestration SDK to build agents combining LLMs with tools, memory, and plans.\\r\\n \\r\\n ## 🧩 Interoperability: Agent & Tool Protocol Fit \\r\\n Supports MCP concepts via tool plugins; could benefit from A2A for cross-agent coordination.\\r\\n \\r\\n ## 🛠️ How AI Guild Can Contribute \\r\\n - Plug kernel plugins into A2A so that orchestration spans agents\\r\\n - Use SAP Gateway (OData) as agentized tool set via MCP\\r\\n \\r\\n ## 🕒 Estimated Time Commitment \\r\\n Medium (4-8 hours/week)\\r\\n\\r\\n \\r\\n ## 🧪 Required Skills \\r\\n C#, Python, AI Orchestration, LLM Integration\\r\\n \\r\\n ## ⚖️ License \\r\\n \\r\\n \\r\\n ---\\r\\n \\r\\n ## 💬 Additional Information \\r\\n \\r\\n \\r\\n 📎 Linked source: `Semantic Kernel.json`\\r\\n \",\n \"id\": 16,\n \"title\": \"Semantic Kernel\",\n \"reactions\": {\n \"url\": \"https://github.tools.sap/api/v3/repos/AI-GUILD-IL/os-contribution/issues/16/reactions\",\n \"total_count\": 0,\n \"+1\": 0,\n \"-1\": 0,\n \"laugh\": 0,\n \"hooray\": 0,\n \"confused\": 0,\n \"heart\": 0,\n \"rocket\": 0,\n \"eyes\": 0\n },\n \"labels\": [\n \"os:suggestion\",\n \"microsoft\",\n \"os:agent-builder\"\n ],\n \"votes\": 0,\n \"comments\": 0,\n \"prerequisites\": {\n \"notDuplicate\": false,\n \"hasLicense\": false,\n \"isActive\": false\n },\n \"author\": {\n \"name\": \"osvote[bot]\",\n \"avatar\": \"https://avatars.github.tools.sap/u/39522?\"\n },\n \"createdAt\": \"2025-05-15T20:10:04Z\",\n \"updatedAt\": \"2025-06-03T13:08:50Z\",\n \"languages\": [],\n \"projectName\": \"\",\n \"repositoryUrl\": \"\",\n \"description\": \"\",\n \"contribution\": \"\",\n \"timeCommitment\": \"\",\n \"skills\": [],\n \"license\": \"\",\n \"additionalInfo\": \"\",\n \"highlights\": \"\"\n },\n {\n \"raw\": \"# OpenGPTs \\r\\n \\r\\n ---\\r\\n \\r\\n ## 🔗 Repository URL \\r\\n https://github.com/langchain-ai/opengpts\\r\\n \\r\\n ## 🧠 Project Description \\r\\n Multi-agent interface with LangChain to create and interact with autonomous GPTs via UI.\\r\\n \\r\\n ## 🧩 Interoperability: Agent & Tool Protocol Fit \\r\\n Could expose agents as A2A endpoints and add MCP-based tools into LangChain tools list.\\r\\n \\r\\n ## 🛠️ How AI Guild Can Contribute \\r\\n - Add UI for registering tools into SAP Launchpad via MCP schema\\r\\n - Wire agent config into SAP IAS and provisioning interface\\r\\n \\r\\n ## 🕒 Estimated Time Commitment \\r\\n Medium (4-8 hours/week)\\r\\n\\r\\n \\r\\n ## 🧪 Required Skills \\r\\n Python, LangChain, TypeScript, LLM Agents\\r\\n\\r\\n \\r\\n ## ⚖️ License \\r\\n \\r\\n \\r\\n ---\\r\\n \\r\\n ## 💬 Additional Information \\r\\n \\r\\n \\r\\n 📎 Linked source: `OpenGPTs.json`\\r\\n \",\n \"id\": 15,\n \"title\": \"OpenGPTs\",\n \"reactions\": {\n \"url\": \"https://github.tools.sap/api/v3/repos/AI-GUILD-IL/os-contribution/issues/15/reactions\",\n \"total_count\": 0,\n \"+1\": 0,\n \"-1\": 0,\n \"laugh\": 0,\n \"hooray\": 0,\n \"confused\": 0,\n \"heart\": 0,\n \"rocket\": 0,\n \"eyes\": 0\n },\n \"labels\": [\n \"os:archive\"\n ],\n \"votes\": 0,\n \"comments\": 0,\n \"prerequisites\": {\n \"notDuplicate\": false,\n \"hasLicense\": false,\n \"isActive\": false\n },\n \"author\": {\n \"name\": \"osvote[bot]\",\n \"avatar\": \"https://avatars.github.tools.sap/u/39522?\"\n },\n \"createdAt\": \"2025-05-15T20:10:03Z\",\n \"updatedAt\": \"2025-06-03T13:02:25Z\",\n \"languages\": [],\n \"projectName\": \"\",\n \"repositoryUrl\": \"\",\n \"description\": \"\",\n \"contribution\": \"\",\n \"timeCommitment\": \"\",\n \"skills\": [],\n \"license\": \"\",\n \"additionalInfo\": \"\",\n \"highlights\": \"\"\n },\n {\n \"raw\": \"# smol-developer\\r\\n ---\\r\\n \\r\\n ## 🔗 Repository URL \\r\\n https://github.com/smol-ai/developer\\r\\n \\r\\n ## 🧠 Project Description \\r\\n Smol AI’s autonomous developer – plans and executes entire software tasks with LLMs.\\r\\n \\r\\n ## 🧩 Interoperability: Agent & Tool Protocol Fit \\r\\n Could be modularized with A2A for coordination and enhanced via MCP tool integrations (debuggers, browsers, docs).\\r\\n \\r\\n ## 🛠️ How AI Guild Can Contribute \\r\\n - Provide SAP GitOps overlay on agent-generated names\\r\\n - Auto-gen build + deploy workflows for BTP or CAP from A2A agent intents\\r\\n \\r\\n ## 🕒 Estimated Time Commitment \\r\\n Medium (4-8 hours/week)\\r\\n\\r\\n \\r\\n ## 🧪 Required Skills \\r\\n Python, Autonomous Agents, Software Engineering, LLMs\\r\\n\\r\\n \\r\\n ## ⚖️ License \\r\\n \\r\\n \\r\\n ---\\r\\n \\r\\n ## 💬 Additional Information \\r\\n \\r\\n \\r\\n 📎 Linked source: `smol-developer.json`\\r\\n \",\n \"id\": 14,\n \"title\": \"smol-developer\",\n \"reactions\": {\n \"url\": \"https://github.tools.sap/api/v3/repos/AI-GUILD-IL/os-contribution/issues/14/reactions\",\n \"total_count\": 1,\n \"+1\": 0,\n \"-1\": 0,\n \"laugh\": 0,\n \"hooray\": 0,\n \"confused\": 0,\n \"heart\": 1,\n \"rocket\": 0,\n \"eyes\": 0\n },\n \"labels\": [\n \"os:suggestion\"\n ],\n \"votes\": 1,\n \"comments\": 1,\n \"prerequisites\": {\n \"notDuplicate\": false,\n \"hasLicense\": false,\n \"isActive\": false\n },\n \"author\": {\n \"name\": \"osvote[bot]\",\n \"avatar\": \"https://avatars.github.tools.sap/u/39522?\"\n },\n \"createdAt\": \"2025-05-15T20:10:03Z\",\n \"updatedAt\": \"2025-05-26T16:28:11Z\",\n \"languages\": [],\n \"projectName\": \"\",\n \"repositoryUrl\": \"\",\n \"description\": \"\",\n \"contribution\": \"\",\n \"timeCommitment\": \"\",\n \"skills\": [],\n \"license\": \"\",\n \"additionalInfo\": \"\",\n \"highlights\": \"\"\n },\n {\n \"raw\": \"# Aider \\r\\n ---\\r\\n ## 🔗 Repository URL \\r\\n https://github.com/Aider-AI/aider\\r\\n \\r\\n ## 🧠 Project Description \\r\\n CLI tool for AI pair programming with Git integration.\\r\\n \\r\\n ## 🧩 Interoperability: Agent & Tool Protocol Fit \\r\\n No current MCP/A2A use; could benefit from MCP tool access and A2A-based agent collaboration.\\r\\n \\r\\n ## 🕒 Estimated Time Commitment \\r\\n Medium (4-8 hours/week)\\r\\n\\r\\n \\r\\n ## 🧪 Required Skills \\r\\n Python, Git, LLMs, CLI Tools\\r\\n\\r\\n \\r\\n ## ⚖️ License \\r\\n \\r\\n \\r\\n ---\\r\\n \\r\\n ## 💬 Additional Information \\r\\n \\r\\n \\r\\n 📎 Linked source: `Aider.json`\\r\\n \",\n \"id\": 13,\n \"title\": \"Aider\",\n \"reactions\": {\n \"url\": \"https://github.tools.sap/api/v3/repos/AI-GUILD-IL/os-contribution/issues/13/reactions\",\n \"total_count\": 0,\n \"+1\": 0,\n \"-1\": 0,\n \"laugh\": 0,\n \"hooray\": 0,\n \"confused\": 0,\n \"heart\": 0,\n \"rocket\": 0,\n \"eyes\": 0\n },\n \"labels\": [\n \"os:suggestion\"\n ],\n \"votes\": 0,\n \"comments\": 1,\n \"prerequisites\": {\n \"notDuplicate\": false,\n \"hasLicense\": false,\n \"isActive\": false\n },\n \"author\": {\n \"name\": \"osvote[bot]\",\n \"avatar\": \"https://avatars.github.tools.sap/u/39522?\"\n },\n \"createdAt\": \"2025-05-15T20:10:02Z\",\n \"updatedAt\": \"2025-05-26T16:29:39Z\",\n \"languages\": [],\n \"projectName\": \"\",\n \"repositoryUrl\": \"\",\n \"description\": \"\",\n \"contribution\": \"\",\n \"timeCommitment\": \"\",\n \"skills\": [],\n \"license\": \"\",\n \"additionalInfo\": \"\",\n \"highlights\": \"\"\n },\n {\n \"raw\": \"# Helicone \\r\\n ---\\r\\n \\r\\n ## 🔗 Repository URL \\r\\n https://github.com/Helicone/helicone\\r\\n \\r\\n ## 🧠 Project Description \\r\\n Observability and analytics layer for LLM usage, focused on prompt tracing and cost tracking.\\r\\n \\r\\n ## 🧩 Interoperability: Agent & Tool Protocol Fit \\r\\n Could benefit from A2A for distributed agent monitoring and from MCP to standardize tool usage across tracked models.\\r\\n \\r\\n ## 🛠️ How AI Guild Can Contribute \\r\\n - Add A2A hooks for remote tool feedback to prompt monitors\\r\\n - Expose telemetry as MCP service for dynamic model adjustments\\r\\n \\r\\n ## 🕒 Estimated Time Commitment \\r\\n Medium (4-8 hours/week)\\r\\n\\r\\n \\r\\n ## 🧪 Required Skills \\r\\n TypeScript, Go, Python, LLM Observability\\r\\n\\r\\n \\r\\n ## ⚖️ License \\r\\n \\r\\n \\r\\n ---\\r\\n \\r\\n ## 💬 Additional Information \\r\\n \\r\\n \\r\\n 📎 Linked source: `Helicone.json`\\r\\n \",\n \"id\": 12,\n \"title\": \"Helicone\",\n \"reactions\": {\n \"url\": \"https://github.tools.sap/api/v3/repos/AI-GUILD-IL/os-contribution/issues/12/reactions\",\n \"total_count\": 1,\n \"+1\": 0,\n \"-1\": 0,\n \"laugh\": 0,\n \"hooray\": 0,\n \"confused\": 0,\n \"heart\": 1,\n \"rocket\": 0,\n \"eyes\": 0\n },\n \"labels\": [\n \"os:suggestion\"\n ],\n \"votes\": 1,\n \"comments\": 0,\n \"prerequisites\": {\n \"notDuplicate\": false,\n \"hasLicense\": false,\n \"isActive\": false\n },\n \"author\": {\n \"name\": \"osvote[bot]\",\n \"avatar\": \"https://avatars.github.tools.sap/u/39522?\"\n },\n \"createdAt\": \"2025-05-15T20:10:01Z\",\n \"updatedAt\": \"2025-05-26T16:30:57Z\",\n \"languages\": [],\n \"projectName\": \"\",\n \"repositoryUrl\": \"\",\n \"description\": \"\",\n \"contribution\": \"\",\n \"timeCommitment\": \"\",\n \"skills\": [],\n \"license\": \"\",\n \"additionalInfo\": \"\",\n \"highlights\": \"\"\n },\n {\n \"raw\": \" ## 🔗 Repository URL \\r\\n https://github.com/lastmile-ai/mcp-agent\\r\\n \\r\\n ## 🧠 Project Description \\r\\n Framework for building agents using the Model Context Protocol.\\r\\n \\r\\n ## 🧩 Interoperability: Agent & Tool Protocol Fit \\r\\n Built on MCP; could be extended with A2A support for inter-agent communication.\\r\\n \\r\\n ## 🛠️ How AI Guild Can Contribute \\r\\n - Build SAP-specific tool servers (e.g., SAP Help Search, DB Query)\\r\\n - Add A2A protocol endpoints for inter-agent federation on BTP (?)\\r\\n\\r\\n ## 🕒 Estimated Time Commitment \\r\\n Medium (4-8 hours/week)\\r\\n \\r\\n ## 🧪 Required Skills \\r\\n Python, Model Context Protocol (MCP), Agent Orchestration\\r\\n\\r\\n \\r\\n ## ⚖️ License \\r\\n \\r\\n \\r\\n ---\\r\\n \\r\\n ## 💬 Additional Information \\r\\n \\r\\n \\r\\n 📎 Linked source: `MCP Agent.json`\\r\\n \",\n \"id\": 11,\n \"title\": \"MCP Agent\",\n \"reactions\": {\n \"url\": \"https://github.tools.sap/api/v3/repos/AI-GUILD-IL/os-contribution/issues/11/reactions\",\n \"total_count\": 0,\n \"+1\": 0,\n \"-1\": 0,\n \"laugh\": 0,\n \"hooray\": 0,\n \"confused\": 0,\n \"heart\": 0,\n \"rocket\": 0,\n \"eyes\": 0\n },\n \"labels\": [\n \"os:suggestion\",\n \"os:agent-builder\"\n ],\n \"votes\": 0,\n \"comments\": 0,\n \"prerequisites\": {\n \"notDuplicate\": false,\n \"hasLicense\": false,\n \"isActive\": false\n },\n \"author\": {\n \"name\": \"osvote[bot]\",\n \"avatar\": \"https://avatars.github.tools.sap/u/39522?\"\n },\n \"createdAt\": \"2025-05-15T20:10:01Z\",\n \"updatedAt\": \"2025-06-03T13:10:06Z\",\n \"languages\": [],\n \"projectName\": \"\",\n \"repositoryUrl\": \"\",\n \"description\": \"\",\n \"contribution\": \"\",\n \"timeCommitment\": \"\",\n \"skills\": [],\n \"license\": \"\",\n \"additionalInfo\": \"\",\n \"highlights\": \"\"\n },\n {\n \"raw\": \"# MCP Inspector \\r\\n ---\\r\\n \\r\\n ## 🔗 Repository URL \\r\\n https://github.com/modelcontextprotocol/inspector\\r\\n \\r\\n ## 🧠 Project Description \\r\\n Inspector tool for MCP messages—monitors and visualizes requests/responses between clients and servers.\\r\\n \\r\\n ## 🧩 Interoperability: Agent & Tool Protocol Fit \\r\\n Built to debug MCP; could be enhanced with better visualizations or support for A2A traffic in future extensions.\\r\\n \\r\\n ## 🛠️ How AI Guild Can Contribute \\r\\n - Extend to support multi servers \\r\\n \\r\\n ## 🕒 Estimated Time Commitment \\r\\n Small (1-3 hours/week)\\r\\n \\r\\n ## 🧪 Required Skills \\r\\n TypeScript, React, MCP, Debugging Tools\\r\\n\\r\\n \\r\\n ## ⚖️ License \\r\\n \\r\\n \\r\\n ---\\r\\n \\r\\n ## 💬 Additional Information \\r\\n \\r\\n \\r\\n 📎 Linked source: `inspector.json`\\r\\n \",\n \"id\": 10,\n \"title\": \"MCP Inspector\",\n \"reactions\": {\n \"url\": \"https://github.tools.sap/api/v3/repos/AI-GUILD-IL/os-contribution/issues/10/reactions\",\n \"total_count\": 0,\n \"+1\": 0,\n \"-1\": 0,\n \"laugh\": 0,\n \"hooray\": 0,\n \"confused\": 0,\n \"heart\": 0,\n \"rocket\": 0,\n \"eyes\": 0\n },\n \"labels\": [\n \"os:suggestion\"\n ],\n \"votes\": 0,\n \"comments\": 0,\n \"prerequisites\": {\n \"notDuplicate\": false,\n \"hasLicense\": false,\n \"isActive\": false\n },\n \"author\": {\n \"name\": \"osvote[bot]\",\n \"avatar\": \"https://avatars.github.tools.sap/u/39522?\"\n },\n \"createdAt\": \"2025-05-15T20:10:00Z\",\n \"updatedAt\": \"2025-06-03T13:04:40Z\",\n \"languages\": [],\n \"projectName\": \"\",\n \"repositoryUrl\": \"\",\n \"description\": \"\",\n \"contribution\": \"\",\n \"timeCommitment\": \"\",\n \"skills\": [],\n \"license\": \"\",\n \"additionalInfo\": \"\",\n \"highlights\": \"\"\n },\n {\n \"raw\": \"# Open WebUI \\r\\n ---\\r\\n \\r\\n ## 🔗 Repository URL \\r\\n https://github.com/open-webui/open-webui\\r\\n \\r\\n ## 🧠 Project Description \\r\\n Local web UI for interacting with LLMs like OpenAI, Ollama, LM Studio, and others.\\r\\n \\r\\n ## 🧩 Interoperability: Agent & Tool Protocol Fit \\r\\n Could integrate MCP to allow access to external tool APIs and A2A for backend AI agent interaction.\\r\\n \\r\\n ## 🛠️ How AI Guild Can Contribute \\r\\n - Add SAP API Hub wrapper as MCP server\\r\\n - Build agent-to-agent pipeline that connects support tooling to dev tools\\r\\n \\r\\n ## 🕒 Estimated Time Commitment \\r\\n Medium (4-8 hours/week)\\r\\n\\r\\n \\r\\n ## 🧪 Required Skills \\r\\n TypeScript, Python, LLM APIs, Web UI Development\\r\\n \\r\\n ## ⚖️ License \\r\\n \\r\\n \\r\\n ---\\r\\n \\r\\n ## 💬 Additional Information \\r\\n \\r\\n \\r\\n 📎 Linked source: `Open WebUI.json`\\r\\n \",\n \"id\": 9,\n \"title\": \"Open WebUI\",\n \"reactions\": {\n \"url\": \"https://github.tools.sap/api/v3/repos/AI-GUILD-IL/os-contribution/issues/9/reactions\",\n \"total_count\": 2,\n \"+1\": 2,\n \"-1\": 0,\n \"laugh\": 0,\n \"hooray\": 0,\n \"confused\": 0,\n \"heart\": 0,\n \"rocket\": 0,\n \"eyes\": 0\n },\n \"labels\": [\n \"os:suggestion\",\n \"os:chat-app\"\n ],\n \"votes\": 2,\n \"comments\": 0,\n \"prerequisites\": {\n \"notDuplicate\": false,\n \"hasLicense\": false,\n \"isActive\": false\n },\n \"author\": {\n \"name\": \"osvote[bot]\",\n \"avatar\": \"https://avatars.github.tools.sap/u/39522?\"\n },\n \"createdAt\": \"2025-05-15T20:09:59Z\",\n \"updatedAt\": \"2025-06-03T13:09:13Z\",\n \"languages\": [],\n \"projectName\": \"\",\n \"repositoryUrl\": \"\",\n \"description\": \"\",\n \"contribution\": \"\",\n \"timeCommitment\": \"\",\n \"skills\": [],\n \"license\": \"\",\n \"additionalInfo\": \"\",\n \"highlights\": \"\"\n },\n {\n \"raw\": \"# GPT Pilot\\r\\nAI software engineer that generates full-stack apps from specifications and user feedback.\\r\\n\\r\\n ---\\r\\n\\r\\n ## 🔗 Repository URL \\r\\n https://github.com/Pythagora-io/gpt-pilot\\r\\n \\r\\n ## 🧠 Project Description \\r\\nGPT Pilot demonstrates high autonomy by employing a multi-agent system (Product Owner Agent, Software Architect Agent, DevOps Agent) to handle requirement analysis, technical planning, environment setup, and TDD-based code generation\\r\\n \\r\\n ## 🧩 Interoperability: Agent & Tool Protocol Fit \\r\\n Could be modularized with A2A for task delegation to specialized agents (e.g. UX, backend, infra) and integrate MCP for tool access during code generation.\\r\\n \\r\\n ## 🛠️ How AI Guild Can Contribute \\r\\n - Extend the pilot capabilities with SAP diffrent applications (CDS, App Router, Worzone, Identity, AMS etc) \\r\\n - Implement design-to-code toolchain with SAP Fiori assets as MCP service\\r\\n \\r\\n ## 🕒 Estimated Time Commitment \\r\\n Medium (4-8 hours/week)\\r\\n\\r\\n \\r\\n ## 🧪 Required Skills \\r\\n TypeScript, Python, Full-Stack Development, LLMs\\r\\n\\r\\n \\r\\n ## ⚖️ License \\r\\n \\r\\n \\r\\n ---\\r\\n \\r\\n ## 💬 Additional Information \\r\\n \\r\\n \\r\\n 📎 Linked source: `GPT Pilot.json`\\r\\n \",\n \"id\": 8,\n \"title\": \"GPT Pilot\",\n \"description\": \"GPT Pilot is an AI-driven assistant for building full-fledged applications autonomously from natural language prompts. GPT Pilot demonstrates high autonomy by employing a multi-agent system (Product Owner Agent, Software Architect Agent, DevOps Agent) to handle requirement analysis, technical planning, environment setup, and TDD-based code generation.\",\n\n \"reactions\": {\n \"url\": \"https://github.tools.sap/api/v3/repos/AI-GUILD-IL/os-contribution/issues/8/reactions\",\n \"total_count\": 1,\n \"+1\": 1,\n \"-1\": 0,\n \"laugh\": 0,\n \"hooray\": 0,\n \"confused\": 0,\n \"heart\": 0,\n \"rocket\": 0,\n \"eyes\": 0\n },\n \"labels\": [\n \"os:suggestion\",\n \"os:app-builder\"\n ],\n \"votes\": 1,\n \"comments\": 0,\n \"prerequisites\": {\n \"notDuplicate\": false,\n \"hasLicense\": false,\n \"isActive\": false\n },\n \"author\": {\n \"name\": \"osvote[bot]\",\n \"avatar\": \"https://avatars.github.tools.sap/u/39522?\"\n },\n \"createdAt\": \"2025-05-15T20:09:59Z\",\n \"updatedAt\": \"2025-06-03T13:09:04Z\",\n \"languages\": [],\n \"projectName\": \"\",\n \"repositoryUrl\": \"\",\n \"description\": \"\",\n \"contribution\": \"\",\n \"timeCommitment\": \"\",\n \"skills\": [],\n \"license\": \"\",\n \"additionalInfo\": \"\",\n \"highlights\": \"\"\n },\n {\n \"raw\": \"\\r\\n ## 🔗 Repository URL \\r\\n https://github.com/plastic-labs/tutor-gpt\\r\\n \\r\\n ## 🧠 Project Description \\r\\n Personalized AI tutor with theory-of-mind capabilities.\\r\\n \\r\\n ## 🧩 Interoperability: Agent & Tool Protocol Fit \\r\\n Not currently using MCP/A2A; potential for multi-agent tutoring with A2A and dynamic tool access via MCP.\\r\\n \\r\\n ## 🛠️ How AI Guild Can Contribute \\r\\n - Create multi-agent tutoring model with A2A (lesson agent, quiz agent)\\r\\n - Add MCP integration for retrieving learning content from SAP Learning Hub\\r\\n - Develop context manager that tailors response via SAP profile extensions\\r\\n \\r\\n ## 🕒 Estimated Time Commitment \\r\\n Medium (4-8 hours/week)\\r\\n\\r\\n \\r\\n ## 🧪 Required Skills \\r\\n TypeScript, Next.js, Python, LLMs\\r\\n\\r\\n \\r\\n ## ⚖️ License \\r\\n \\r\\n \\r\\n ---\\r\\n \\r\\n ## 💬 Additional Information \\r\\n \\r\\n \\r\\n 📎 Linked source: `Tutor-GPT.json`\\r\\n \",\n \"id\": 7,\n \"title\": \"Tutor-GPT\",\n \"reactions\": {\n \"url\": \"https://github.tools.sap/api/v3/repos/AI-GUILD-IL/os-contribution/issues/7/reactions\",\n \"total_count\": 1,\n \"+1\": 0,\n \"-1\": 0,\n \"laugh\": 0,\n \"hooray\": 0,\n \"confused\": 0,\n \"heart\": 1,\n \"rocket\": 0,\n \"eyes\": 0\n },\n \"labels\": [\n \"os:archive\"\n ],\n \"votes\": 1,\n \"comments\": 0,\n \"prerequisites\": {\n \"notDuplicate\": false,\n \"hasLicense\": false,\n \"isActive\": false\n },\n \"author\": {\n \"name\": \"osvote[bot]\",\n \"avatar\": \"https://avatars.github.tools.sap/u/39522?\"\n },\n \"createdAt\": \"2025-05-15T20:09:58Z\",\n \"updatedAt\": \"2025-06-03T13:03:30Z\",\n \"languages\": [],\n \"projectName\": \"\",\n \"repositoryUrl\": \"\",\n \"description\": \"\",\n \"contribution\": \"\",\n \"timeCommitment\": \"\",\n \"skills\": [],\n \"license\": \"\",\n \"additionalInfo\": \"\",\n \"highlights\": \"\"\n },\n {\n \"raw\": \"# 📌 Big-AGI\\r\\n---\\r\\n \\r\\n ## 🔗 Repository URL \\r\\n https://github.com/enricoros/big-AGI\\r\\n \\r\\n ## 🧠 Project Description \\r\\n Open AGI interface and agentic framework with extensible toolset and local-first model options.\\r\\n \\r\\n ## 🧩 Interoperability: Agent & Tool Protocol Fit \\r\\n Framework is ready for MCP/A2A plugins—excellent candidate to embed protocol support for agent interoperability and external tool usage.\\r\\n \\r\\n ## 🛠️ How AI Guild Can Contribute \\r\\n - Enable App Router extensions for multi-agent interface\\r\\n - Use MCP to pull service info from SAP HANA Cloud metadata layer\\r\\n \\r\\n ## 🕒 Estimated Time Commitment \\r\\n Medium (4-8 hours/week)\\r\\n\\r\\n \\r\\n ## 🧪 Required Skills \\r\\n TypeScript, Python, AI Orchestration, Tools Integration\\r\\n\\r\\n \\r\\n ## ⚖️ License \\r\\n \\r\\n \\r\\n ---\\r\\n \\r\\n ## 💬 Additional Information \\r\\n \\r\\n \\r\\n 📎 Linked source: `big-AGI.json`\\r\\n \",\n \"id\": 6,\n \"title\": \"big-AGI\",\n \"reactions\": {\n \"url\": \"https://github.tools.sap/api/v3/repos/AI-GUILD-IL/os-contribution/issues/6/reactions\",\n \"total_count\": 0,\n \"+1\": 0,\n \"-1\": 0,\n \"laugh\": 0,\n \"hooray\": 0,\n \"confused\": 0,\n \"heart\": 0,\n \"rocket\": 0,\n \"eyes\": 0\n },\n \"labels\": [\n \"os:suggestion\"\n ],\n \"votes\": 0,\n \"comments\": 0,\n \"prerequisites\": {\n \"notDuplicate\": false,\n \"hasLicense\": false,\n \"isActive\": false\n },\n \"author\": {\n \"name\": \"osvote[bot]\",\n \"avatar\": \"https://avatars.github.tools.sap/u/39522?\"\n },\n \"createdAt\": \"2025-05-15T20:09:58Z\",\n \"updatedAt\": \"2025-05-26T16:45:59Z\",\n \"languages\": [],\n \"projectName\": \"\",\n \"repositoryUrl\": \"\",\n \"description\": \"\",\n \"contribution\": \"\",\n \"timeCommitment\": \"\",\n \"skills\": [],\n \"license\": \"\",\n \"additionalInfo\": \"\",\n \"highlights\": \"\"\n },\n {\n \"raw\": \"# Zed\\r\\n \\r\\n--- \\r\\n \\r\\n ## 🔗 Repository URL \\r\\n https://github.com/zed-industries/zed\\r\\n \\r\\n ## 🧠 Project Description \\r\\n High-performance code editor built in Rust with collaborative features.\\r\\n \\r\\n ## 🧩 Interoperability: Agent & Tool Protocol Fit \\r\\n Though primarily Rust, could be extended with A2A for agent co-editing, or embed MCP clients for tooling support in AI-assisted workflows.\\r\\n \\r\\n ## 🛠️ How AI Guild Can Contribute \\r\\n - \\r\\n \\r\\n ## 🕒 Estimated Time Commitment \\r\\n Medium (4-8 hours/week)\\r\\n\\r\\n \\r\\n ## 🧪 Required Skills \\r\\n Rust, TypeScript, Real-time Collaboration, Editor Development\\r\\n\\r\\n \\r\\n ## ⚖️ License \\r\\n \\r\\n \\r\\n ---\\r\\n \\r\\n ## 💬 Additional Information \\r\\n \\r\\n \\r\\n 📎 Linked source: `Zed.json`\\r\\n \",\n \"id\": 5,\n \"title\": \"Zed\",\n \"reactions\": {\n \"url\": \"https://github.tools.sap/api/v3/repos/AI-GUILD-IL/os-contribution/issues/5/reactions\",\n \"total_count\": 0,\n \"+1\": 0,\n \"-1\": 0,\n \"laugh\": 0,\n \"hooray\": 0,\n \"confused\": 0,\n \"heart\": 0,\n \"rocket\": 0,\n \"eyes\": 0\n },\n \"labels\": [\n \"os:suggestion\",\n \"os:smart-ide\"\n ],\n \"votes\": 0,\n \"comments\": 0,\n \"prerequisites\": {\n \"notDuplicate\": false,\n \"hasLicense\": false,\n \"isActive\": false\n },\n \"author\": {\n \"name\": \"osvote[bot]\",\n \"avatar\": \"https://avatars.github.tools.sap/u/39522?\"\n },\n \"createdAt\": \"2025-05-15T20:09:57Z\",\n \"updatedAt\": \"2025-06-03T13:09:26Z\",\n \"languages\": [],\n \"projectName\": \"\",\n \"repositoryUrl\": \"\",\n \"description\": \"\",\n \"contribution\": \"\",\n \"timeCommitment\": \"\",\n \"skills\": [],\n \"license\": \"\",\n \"additionalInfo\": \"\",\n \"highlights\": \"\"\n },\n {\n \"raw\": \"# 📌 XState Agent\\r\\n---\\r\\n \\r\\n ## 🔗 Repository URL \\r\\n https://github.com/statelyai/agent\\r\\n \\r\\n ## 🧠 Project Description \\r\\n Agent framework built on top of XState to manage reasoning and actions via finite state machines.\\r\\n \\r\\n ## 🧩 Interoperability: Agent & Tool Protocol Fit \\r\\n A strong fit for both protocols — could expose agents as A2A services and leverage MCP to connect tools declaratively inside the state machine logic.\\r\\n \\r\\n ## 🛠️ How AI Guild Can Contribute \\r\\n - Integrate Agent tools with MCP servers\\r\\n - Integration with SAP agent builder\\r\\n - Add agent visualization\\r\\n \\r\\n ## 🕒 Estimated Time Commitment \\r\\n Medium (4-8 hours/week)\\r\\n\\r\\n \\r\\n ## 🧪 Required Skills \\r\\n TypeScript, XState, State Machines, LLM Integration\\r\\n\\r\\n \\r\\n ## ⚖️ License \\r\\n \\r\\n \\r\\n ---\\r\\n \\r\\n ## 💬 Additional Information \\r\\n \\r\\n \\r\\n 📎 Linked source: `XState Agent.json`\\r\\n \",\n \"id\": 4,\n \"title\": \"XState Agent\",\n \"reactions\": {\n \"url\": \"https://github.tools.sap/api/v3/repos/AI-GUILD-IL/os-contribution/issues/4/reactions\",\n \"total_count\": 0,\n \"+1\": 0,\n \"-1\": 0,\n \"laugh\": 0,\n \"hooray\": 0,\n \"confused\": 0,\n \"heart\": 0,\n \"rocket\": 0,\n \"eyes\": 0\n },\n \"labels\": [\n \"os:suggestion\",\n \"os:smart-ide\"\n ],\n \"votes\": 0,\n \"comments\": 0,\n \"prerequisites\": {\n \"notDuplicate\": false,\n \"hasLicense\": false,\n \"isActive\": false\n },\n \"author\": {\n \"name\": \"osvote[bot]\",\n \"avatar\": \"https://avatars.github.tools.sap/u/39522?\"\n },\n \"createdAt\": \"2025-05-15T20:09:57Z\",\n \"updatedAt\": \"2025-06-03T13:09:42Z\",\n \"languages\": [],\n \"projectName\": \"\",\n \"repositoryUrl\": \"\",\n \"description\": \"\",\n \"contribution\": \"\",\n \"timeCommitment\": \"\",\n \"skills\": [],\n \"license\": \"\",\n \"additionalInfo\": \"\",\n \"highlights\": \"\"\n },\n {\n \"raw\": \"# AutoGen Studio\\r\\n---\\r\\n \\r\\n## 🔗 Repository URL \\r\\nhttps://github.com/microsoft/autogen\\r\\n\\r\\n## 🧠 Project Description \\r\\nVisual drag-and-drop interface for building multi-agent workflows using AutoGen.\\r\\n\\r\\n## 🧩 Interoperability: Agent & Tool Protocol Fit \\r\\nAlthough initiated by Microsoft, many forks/extensions are open. Guild could fork and add MCP/A2A compatibility to let agents talk across frameworks or use MCP-based tools.\\r\\n\\r\\n ## 🛠️ How AI Guild Can Contribute \\r\\n - Fork and integrate MCP into agent graph visualizer\\r\\n- Embed SAP BTP tool server templates for LLM workflows\\r\\n- Allow App Router to proxy agent tool execution\\r\\n \\r\\n## 🕒 Estimated Time Commitment \\r\\nMedium (4-8 hours/week)\\r\\n\\r\\n\\r\\n## 🧪 Required Skills \\r\\nPython, TypeScript, Multi-Agent Systems, Low-Code Tools\\r\\n\\r\\n \\r\\n ## ⚖️ License \\r\\n Creative Commons Attribution 4.0 International\\r\\n \\r\\n ---\\r\\n \\r\\n ## 💬 Additional Information \\r\\n \\r\\n \\r\\n 📎 Linked source: `AutoGen Studio.json`\\r\\n \",\n \"id\": 3,\n \"title\": \"AutoGen Studio\",\n \"reactions\": {\n \"url\": \"https://github.tools.sap/api/v3/repos/AI-GUILD-IL/os-contribution/issues/3/reactions\",\n \"total_count\": 0,\n \"+1\": 0,\n \"-1\": 0,\n \"laugh\": 0,\n \"hooray\": 0,\n \"confused\": 0,\n \"heart\": 0,\n \"rocket\": 0,\n \"eyes\": 0\n },\n \"labels\": [\n \"os:suggestion\"\n ],\n \"votes\": 0,\n \"comments\": 0,\n \"prerequisites\": {\n \"notDuplicate\": false,\n \"hasLicense\": false,\n \"isActive\": false\n },\n \"author\": {\n \"name\": \"osvote[bot]\",\n \"avatar\": \"https://avatars.github.tools.sap/u/39522?\"\n },\n \"createdAt\": \"2025-05-15T20:09:56Z\",\n \"updatedAt\": \"2025-06-03T13:06:39Z\",\n \"languages\": [],\n \"projectName\": \"\",\n \"repositoryUrl\": \"\",\n \"description\": \"\",\n \"contribution\": \"\",\n \"timeCommitment\": \"\",\n \"skills\": [],\n \"license\": \"\",\n \"additionalInfo\": \"\",\n \"highlights\": \"\"\n },\n {\n \"raw\": \"# LlamaIndex \\r\\n ---\\r\\n \\r\\n \\r\\n ## 🔗 Repository URL \\r\\n https://github.com/jerryjliu/llama_index\\r\\n \\r\\n ## 🧠 Project Description \\r\\n Framework for connecting LLMs to external data using custom indexes, tools, and retrieval.\\r\\n \\r\\n ## 🧩 Interoperability: Agent & Tool Protocol Fit \\r\\n Ideal fit for MCP to standardize tool access and for A2A to interact as a specialized knowledge agent.\\r\\n \\r\\n \\r\\n ## 🕒 Estimated Time Commitment \\r\\n Medium (4-8 hours/week)\\r\\n\\r\\n \\r\\n ## 🧪 Required Skills \\r\\n Python, Data Indexing, Knowledge Retrieval, LLMs\\r\\n\\r\\n \\r\\n ## ⚖️ License \\r\\n \\r\\n \\r\\n ---\\r\\n \\r\\n ## 💬 Additional Information \\r\\n \\r\\n \\r\\n 📎 Linked source: `LlamaIndex.json`\\r\\n \",\n \"id\": 2,\n \"title\": \"LlamaIndex\",\n \"reactions\": {\n \"url\": \"https://github.tools.sap/api/v3/repos/AI-GUILD-IL/os-contribution/issues/2/reactions\",\n \"total_count\": 0,\n \"+1\": 0,\n \"-1\": 0,\n \"laugh\": 0,\n \"hooray\": 0,\n \"confused\": 0,\n \"heart\": 0,\n \"rocket\": 0,\n \"eyes\": 0\n },\n \"labels\": [\n \"os:archive\"\n ],\n \"votes\": 0,\n \"comments\": 0,\n \"prerequisites\": {\n \"notDuplicate\": false,\n \"hasLicense\": false,\n \"isActive\": false\n },\n \"author\": {\n \"name\": \"osvote[bot]\",\n \"avatar\": \"https://avatars.github.tools.sap/u/39522?\"\n },\n \"createdAt\": \"2025-05-15T20:09:55Z\",\n \"updatedAt\": \"2025-06-03T13:01:04Z\",\n \"languages\": [],\n \"projectName\": \"\",\n \"repositoryUrl\": \"\",\n \"description\": \"\",\n \"contribution\": \"\",\n \"timeCommitment\": \"\",\n \"skills\": [],\n \"license\": \"\",\n \"additionalInfo\": \"\",\n \"highlights\": \"\"\n },\n {\n \"raw\": \"# 📜 DocETL: Powering Complex Document Processing Pipelines\\r\\n \\r\\n---\\r\\n ## 🔗 Repository URL \\r\\n https://github.com/ucbepic/docetl\\r\\n \\r\\n ## 🧠 Project Description \\r\\n LLM-powered document-centric data pipeline builder.\\r\\n \\r\\n ## 🧩 Interoperability: Agent & Tool Protocol Fit \\r\\n Does not use MCP/A2A; could benefit by using A2A to delegate tasks and MCP for standardized tool access.\\r\\n \\r\\n ## 🕒 Estimated Time Commitment \\r\\n Medium (4-8 hours/week)\\r\\n\\r\\n \\r\\n ## 🧪 Required Skills \\r\\n Python, Data Pipelines, Document AI, LLM Integration\\r\\n\\r\\n \\r\\n ## ⚖️ License \\r\\n \\r\\n \\r\\n ---\\r\\n \\r\\n ## 💬 Additional Information \\r\\n \\r\\n \\r\\n 📎 Linked source: `DocETL.json`\\r\\n \",\n \"id\": 1,\n \"title\": \"DocETL\",\n \"reactions\": {\n \"url\": \"https://github.tools.sap/api/v3/repos/AI-GUILD-IL/os-contribution/issues/1/reactions\",\n \"total_count\": 0,\n \"+1\": 0,\n \"-1\": 0,\n \"laugh\": 0,\n \"hooray\": 0,\n \"confused\": 0,\n \"heart\": 0,\n \"rocket\": 0,\n \"eyes\": 0\n },\n \"labels\": [\n \"os:archive\"\n ],\n \"votes\": 0,\n \"comments\": 0,\n \"prerequisites\": {\n \"notDuplicate\": false,\n \"hasLicense\": false,\n \"isActive\": false\n },\n \"author\": {\n \"name\": \"osvote[bot]\",\n \"avatar\": \"https://avatars.github.tools.sap/u/39522?\"\n },\n \"createdAt\": \"2025-05-15T20:09:55Z\",\n \"updatedAt\": \"2025-06-03T13:03:06Z\",\n \"languages\": [],\n \"projectName\": \"\",\n \"repositoryUrl\": \"\",\n \"description\": \"\",\n \"contribution\": \"\",\n \"timeCommitment\": \"\",\n \"skills\": [],\n \"license\": \"\",\n \"additionalInfo\": \"\",\n \"highlights\": \"\"\n }\n ]\n}",[],[371],{"_104":379,"_97":380,"_161":381,"_163":-5,"_164":146,"_165":382,"_167":118,"_106":383,"_101":355,"_169":190,"_171":384,"_172":22,"_173":-5,"_174":385,"_100":386},"227a0cee-42e8-11f0-b273-76b3cceeab13","delete-test-projects-advanced.ts","b31e31b0-42e5-11f0-a397-76b3cceeab13",73,["D",1749222522666],"// Advanced script to delete projects with titles that are \"test\" or start with \"test\"\n// Includes safety features, dry run mode, and comprehensive reporting\n\nconst GIGYA_DOMAIN = process.env.GIGYA_DOMAIN || \"accounts.eu1.gigya.com\";\nconst GIGYA_API_KEY = process.env.GIGYA_API_KEY;\nconst GIGYA_APP_KEY = process.env.GIGYA_APP_KEY;\nconst GIGYA_APP_SECRET = process.env.GIGYA_APP_SECRET;\n\n// Configuration options\nconst CONFIG = {\n dryRun: false, // process.env.DRY_RUN === \"true\", // Set to true to preview deletions without executing them\n requireConfirmation: false, // process.env.REQUIRE_CONFIRMATION !== \"false\", // Require manual confirmation\n batchSize: 5, // Number of projects to delete in each batch\n delayBetweenRequests: 200, // Milliseconds to wait between API calls\n caseSensitive: process.env.CASE_SENSITIVE === \"true\", // Case sensitive matching\n exactMatchOnly: process.env.EXACT_MATCH_ONLY === \"true\", // Only delete exact \"test\" matches\n customPatterns: process.env.CUSTOM_PATTERNS?.split(\",\") || [], // Additional patterns to match\n};\n\nif (!GIGYA_API_KEY || !GIGYA_APP_KEY || !GIGYA_APP_SECRET) {\n console.error(\"Missing Gigya environment variables!\");\n console.log(\"Required variables: GIGYA_API_KEY, GIGYA_APP_KEY, GIGYA_APP_SECRET\");\n console.log(\"\\nOptional environment variables:\");\n console.log(\"- DRY_RUN=true (preview deletions without executing)\");\n console.log(\"- REQUIRE_CONFIRMATION=false (skip confirmation prompt)\");\n console.log(\"- CASE_SENSITIVE=true (case sensitive title matching)\");\n console.log(\"- EXACT_MATCH_ONLY=true (only delete exact 'test' matches)\");\n console.log(\"- CUSTOM_PATTERNS=pattern1,pattern2 (additional patterns to match)\");\n process.exit(1);\n}\n\ninterface ProjectData {\n id?: number;\n title: string;\n description: string;\n repositoryUrl: string;\n votes: number;\n comments: number;\n commitment?: string;\n skills?: string[];\n contribution?: string;\n author?: string;\n enabled: boolean;\n createdAt?: string;\n updatedAt?: string;\n deleted?: boolean;\n deletedAt?: string;\n}\n\ninterface GigyaResponse {\n errorCode: number;\n errorMessage?: string;\n results?: Array<{\n oid: string;\n data: ProjectData;\n }>;\n object?: {\n data: ProjectData;\n };\n}\n\ninterface DeletionStats {\n total: number;\n matched: number;\n deleted: number;\n errors: number;\n skipped: number;\n}\n\nasync function makeGigyaRequest(endpoint: string, params: Record): Promise {\n const url = `https://${GIGYA_DOMAIN}/${endpoint}?httpStatusCodes=true`;\n\n const body = new URLSearchParams({\n apiKey: GIGYA_API_KEY!,\n userKey: GIGYA_APP_KEY!,\n secret: GIGYA_APP_SECRET!,\n ...params,\n });\n\n const response = await fetch(url, {\n method: \"POST\",\n headers: { \"Content-Type\": \"application/x-www-form-urlencoded\" },\n body,\n });\n\n if (!response.ok) {\n const text = await response.text();\n throw new Error(`${response.statusText}: ${text}`);\n }\n\n const text = await response.text();\n return JSON.parse(text);\n}\n\nfunction isTestProject(title: string): { isMatch: boolean; reason: string } {\n const originalTitle = title.trim();\n const checkTitle = CONFIG.caseSensitive ? originalTitle : originalTitle.toLowerCase();\n\n // Check exact match for \"test\"\n if (checkTitle === \"test\") {\n return { isMatch: true, reason: \"Exact match: 'test'\" };\n }\n\n // If exact match only, stop here\n if (CONFIG.exactMatchOnly) {\n return { isMatch: false, reason: \"Not exact match\" };\n }\n\n // Check if starts with \"test\"\n if (checkTitle.startsWith(\"test\")) {\n return { isMatch: true, reason: \"Starts with 'test'\" };\n }\n\n // Check custom patterns\n for (const pattern of CONFIG.customPatterns) {\n if (pattern.trim()) {\n const checkPattern = CONFIG.caseSensitive ? pattern.trim() : pattern.trim().toLowerCase();\n if (checkTitle.includes(checkPattern)) {\n return { isMatch: true, reason: `Matches custom pattern: '${pattern}'` };\n }\n }\n }\n\n return { isMatch: false, reason: \"No match\" };\n}\n\nasync function analyzeProjects(): Promise {\n console.log(\"🔍 Analyzing projects for test patterns...\");\n\n try {\n const searchResponse = await makeGigyaRequest(\"ds.search\", {\n query: \"SELECT * FROM oss_projects WHERE deleted != true\",\n });\n\n if (searchResponse.errorCode !== 0) {\n throw new Error(`Failed to fetch projects: ${searchResponse.errorMessage}`);\n }\n\n const projects = searchResponse.results || [];\n\n const analysis = {\n total: projects.length,\n testProjects: 0,\n exactMatches: 0,\n startsWithTest: 0,\n customPatternMatches: 0,\n };\n\n const matchedProjects: Array<{ project: any; reason: string }> = [];\n\n for (const project of projects) {\n const { isMatch, reason } = isTestProject(project.data.title);\n\n if (isMatch) {\n analysis.testProjects++;\n matchedProjects.push({ project, reason });\n\n if (reason.includes(\"Exact match\")) {\n analysis.exactMatches++;\n } else if (reason.includes(\"Starts with\")) {\n analysis.startsWithTest++;\n } else if (reason.includes(\"custom pattern\")) {\n analysis.customPatternMatches++;\n }\n }\n }\n\n console.log(\"\\n📊 Project Analysis:\");\n console.log(` 📁 Total active projects: ${analysis.total}`);\n console.log(` 🧪 Test projects found: ${analysis.testProjects}`);\n console.log(` 🎯 Exact 'test' matches: ${analysis.exactMatches}`);\n console.log(` 🔤 Starts with 'test': ${analysis.startsWithTest}`);\n console.log(` 🔧 Custom pattern matches: ${analysis.customPatternMatches}`);\n\n if (matchedProjects.length > 0) {\n console.log(\"\\n📋 Projects that will be deleted:\");\n matchedProjects.forEach((item, index) => {\n const { project, reason } = item;\n console.log(` ${index + 1}. \"${project.data.title}\" - ${reason}`);\n if (project.data.author) {\n console.log(` 👤 Author: ${project.data.author}`);\n }\n if (project.data.createdAt) {\n console.log(` 📅 Created: ${new Date(project.data.createdAt).toLocaleDateString()}`);\n }\n });\n }\n } catch (error) {\n console.error(\"❌ Error during analysis:\", error);\n throw error;\n }\n}\n\nasync function confirmDeletion(projectCount: number): Promise {\n if (!CONFIG.requireConfirmation) {\n console.log(\"⚠️ Confirmation skipped (REQUIRE_CONFIRMATION=false)\");\n return true;\n }\n\n console.log(`\\n⚠️ WARNING: About to delete ${projectCount} test projects!`);\n console.log(\"This action cannot be undone.\");\n console.log(\"\\nTo proceed, type 'DELETE' (case sensitive):\");\n\n // In a real interactive environment, you would use readline\n // For this script, we'll check an environment variable\n const confirmation = process.env.CONFIRM_DELETE;\n\n if (confirmation === \"DELETE\") {\n console.log(\"✅ Deletion confirmed.\");\n return true;\n } else {\n console.log(\"❌ Deletion not confirmed. Exiting.\");\n console.log(\"To confirm deletion, set: CONFIRM_DELETE=DELETE\");\n return false;\n }\n}\n\nasync function deleteTestProjects(): Promise {\n console.log(`\\n🗑️ Starting test project deletion... ${CONFIG.dryRun ? \"(DRY RUN)\" : \"\"}`);\n\n const stats: DeletionStats = {\n total: 0,\n matched: 0,\n deleted: 0,\n errors: 0,\n skipped: 0,\n };\n\n try {\n // Fetch all projects\n const searchResponse = await makeGigyaRequest(\"ds.search\", {\n query: \"SELECT * FROM oss_projects WHERE deleted != true\",\n });\n\n if (searchResponse.errorCode !== 0) {\n throw new Error(`Failed to fetch projects: ${searchResponse.errorMessage}`);\n }\n\n const allProjects = searchResponse.results || [];\n stats.total = allProjects.length;\n\n // Identify test projects\n const testProjects = allProjects.filter(project => {\n const { isMatch } = isTestProject(project.data.title);\n return isMatch;\n });\n\n stats.matched = testProjects.length;\n\n if (testProjects.length === 0) {\n console.log(\"✅ No test projects found to delete.\");\n return stats;\n }\n\n // Confirm deletion\n if (!CONFIG.dryRun) {\n const confirmed = await confirmDeletion(testProjects.length);\n if (!confirmed) {\n stats.skipped = testProjects.length;\n return stats;\n }\n }\n\n // Process deletions in batches\n for (let i = 0; i < testProjects.length; i += CONFIG.batchSize) {\n const batch = testProjects.slice(i, i + CONFIG.batchSize);\n console.log(\n `\\n📦 Processing batch ${Math.floor(i / CONFIG.batchSize) + 1}/${\n Math.ceil(testProjects.length / CONFIG.batchSize)\n }`,\n );\n\n for (const project of batch) {\n try {\n const { reason } = isTestProject(project.data.title);\n console.log(`🔄 ${CONFIG.dryRun ? \"[DRY RUN] \" : \"\"}Deleting \"${project.data.title}\"`);\n console.log(` 📝 Reason: ${reason}`);\n\n if (!CONFIG.dryRun) {\n // Mark project as deleted (soft delete)\n const updatedProjectData = {\n ...project.data,\n deleted: true,\n deletedAt: new Date().toISOString(),\n updatedAt: new Date().toISOString(),\n };\n\n const deleteResponse = await makeGigyaRequest(\"ds.delete\", {\n type: \"oss_projects\",\n oid: project.oid,\n });\n\n if (deleteResponse.errorCode === 0) {\n console.log(` ✅ Successfully deleted`);\n stats.deleted++;\n } else {\n console.error(` ❌ Failed to delete: ${deleteResponse.errorMessage}`);\n stats.errors++;\n }\n\n // Rate limiting delay\n await new Promise((resolve) => setTimeout(resolve, CONFIG.delayBetweenRequests));\n } else {\n stats.deleted++; // Count as deleted for dry run stats\n }\n } catch (error) {\n console.error(`❌ Error deleting \"${project.data.title}\":`, error);\n stats.errors++;\n }\n }\n }\n\n return stats;\n } catch (error) {\n console.error(\"❌ Error during deletion process:\", error);\n throw error;\n }\n}\n\nasync function generateReport(stats: DeletionStats): Promise {\n console.log(\"\\n📊 Final Deletion Report:\");\n console.log(\"=\".repeat(50));\n console.log(`📁 Total projects analyzed: ${stats.total}`);\n console.log(`🎯 Test projects found: ${stats.matched}`);\n console.log(`🗑️ Successfully deleted: ${stats.deleted}`);\n console.log(`⏭️ Skipped: ${stats.skipped}`);\n console.log(`❌ Errors: ${stats.errors}`);\n\n if (stats.matched > 0) {\n const successRate = (stats.deleted / stats.matched * 100).toFixed(1);\n console.log(`📈 Success rate: ${successRate}%`);\n }\n\n if (CONFIG.dryRun) {\n console.log(\"\\n⚠️ This was a DRY RUN - no projects were actually deleted\");\n console.log(\" Set DRY_RUN=false and CONFIRM_DELETE=DELETE to execute deletions\");\n }\n}\n\nasync function verifyDeletion(): Promise {\n if (CONFIG.dryRun) return;\n\n console.log(\"\\n🔍 Verifying deletions...\");\n\n try {\n // Check active projects\n const activeResponse = await makeGigyaRequest(\"ds.search\", {\n query: \"SELECT * FROM oss_projects WHERE deleted != true\",\n });\n\n // Check deleted projects\n const deletedResponse = await makeGigyaRequest(\"ds.search\", {\n query: \"SELECT * FROM oss_projects WHERE deleted = true\",\n });\n\n if (activeResponse.errorCode === 0 && deletedResponse.errorCode === 0) {\n const activeProjects = activeResponse.results || [];\n const deletedProjects = deletedResponse.results || [];\n\n const remainingTestProjects = activeProjects.filter(project => {\n const { isMatch } = isTestProject(project.data.title);\n return isMatch;\n });\n\n const deletedTestProjects = deletedProjects.filter(project => {\n const { isMatch } = isTestProject(project.data.title);\n return isMatch;\n });\n\n console.log(`✅ Verification complete:`);\n console.log(` 📝 Total active projects: ${activeProjects.length}`);\n console.log(` 🧪 Remaining test projects: ${remainingTestProjects.length}`);\n console.log(` 🗑️ Deleted test projects: ${deletedTestProjects.length}`);\n\n if (remainingTestProjects.length > 0) {\n console.log(\"\\n⚠️ Test projects still active:\");\n remainingTestProjects.forEach((project, index) => {\n const { reason } = isTestProject(project.data.title);\n console.log(` ${index + 1}. \"${project.data.title}\" - ${reason}`);\n });\n } else {\n console.log(\"🎉 All matching test projects have been successfully deleted!\");\n }\n } else {\n console.error(\"❌ Verification failed\");\n }\n } catch (error) {\n console.error(\"❌ Error during verification:\", error);\n }\n}\n\n// Main execution\nasync function main() {\n console.log(\"🚀 Advanced Test Project Deletion Script\");\n console.log(\"=\".repeat(50));\n\n console.log(\"🔧 Configuration:\");\n console.log(` Dry Run: ${CONFIG.dryRun}`);\n console.log(` Require Confirmation: ${CONFIG.requireConfirmation}`);\n console.log(` Case Sensitive: ${CONFIG.caseSensitive}`);\n console.log(` Exact Match Only: ${CONFIG.exactMatchOnly}`);\n console.log(` Custom Patterns: ${CONFIG.customPatterns.length > 0 ? CONFIG.customPatterns.join(\", \") : \"None\"}`);\n\n try {\n await analyzeProjects();\n const stats = await deleteTestProjects();\n await generateReport(stats);\n await verifyDeletion();\n\n console.log(\"\\n🎉 Script completed successfully!\");\n } catch (error) {\n console.error(\"❌ Script execution failed:\", error);\n process.exit(1);\n }\n}\n\n// Run the script\nmain();",[],[380],{"_104":388,"_97":389,"_161":390,"_163":-5,"_164":146,"_165":391,"_167":118,"_106":392,"_101":33,"_169":190,"_171":393,"_172":22,"_173":-5,"_174":394,"_100":395},"928a9920-42e5-11f0-b5b9-76b3cceeab13","delete-test-projects.ts","928a9a06-42e5-11f0-b5b9-76b3cceeab13",65,["D",1749221422191],"// Script to delete projects with titles that are \"test\" or start with \"test\"\n\nconst GIGYA_DOMAIN = process.env.GIGYA_DOMAIN || \"accounts.eu1.gigya.com\";\nconst GIGYA_API_KEY = process.env.GIGYA_API_KEY;\nconst GIGYA_APP_KEY = process.env.GIGYA_APP_KEY;\nconst GIGYA_APP_SECRET = process.env.GIGYA_APP_SECRET;\n\nif (!GIGYA_API_KEY || !GIGYA_APP_KEY || !GIGYA_APP_SECRET) {\n console.error(\"Missing Gigya environment variables!\");\n console.log(\"Required variables: GIGYA_API_KEY, GIGYA_APP_KEY, GIGYA_APP_SECRET\");\n process.exit(1);\n}\n\ninterface ProjectData {\n id?: number;\n title: string;\n description: string;\n repositoryUrl: string;\n votes: number;\n comments: number;\n commitment?: string;\n skills?: string[];\n contribution?: string;\n author?: string;\n enabled: boolean;\n createdAt?: string;\n updatedAt?: string;\n deleted?: boolean;\n}\n\ninterface GigyaResponse {\n errorCode: number;\n errorMessage?: string;\n results?: Array<{\n oid: string;\n data: ProjectData;\n }>;\n object?: {\n data: ProjectData;\n };\n}\n\nasync function makeGigyaRequest(endpoint: string, params: Record): Promise {\n const url = `https://${GIGYA_DOMAIN}/${endpoint}?httpStatusCodes=true`;\n\n const body = new URLSearchParams({\n apiKey: GIGYA_API_KEY!,\n userKey: GIGYA_APP_KEY!,\n secret: GIGYA_APP_SECRET!,\n ...params,\n });\n\n const response = await fetch(url, {\n method: \"POST\",\n headers: { \"Content-Type\": \"application/x-www-form-urlencoded\" },\n body,\n });\n\n if (!response.ok) {\n const text = await response.text();\n throw new Error(`${response.statusText}: ${text}`);\n }\n\n const text = await response.text();\n return JSON.parse(text);\n}\n\nfunction isTestProject(title: string): boolean {\n const normalizedTitle = title.toLowerCase().trim();\n return normalizedTitle === \"test\" || normalizedTitle.startsWith(\"test\");\n}\n\nasync function deleteTestProjects() {\n console.log(\"🔍 Starting test project deletion process...\");\n \n try {\n // Step 1: Fetch all existing projects\n console.log(\"📥 Fetching all projects from Gigya DS...\");\n const searchResponse = await makeGigyaRequest(\"ds.search\", {\n query: \"SELECT * FROM oss_projects WHERE deleted != true\",\n });\n\n if (searchResponse.errorCode !== 0) {\n throw new Error(`Failed to fetch projects: ${searchResponse.errorMessage}`);\n }\n\n const allProjects = searchResponse.results || [];\n console.log(`📊 Found ${allProjects.length} total projects`);\n\n // Step 2: Identify test projects\n const testProjects = allProjects.filter(project => \n isTestProject(project.data.title)\n );\n\n console.log(`🎯 Found ${testProjects.length} test projects to delete:`);\n \n if (testProjects.length === 0) {\n console.log(\"✅ No test projects found. Nothing to delete.\");\n return { deletedCount: 0, errorCount: 0 };\n }\n\n // List the projects that will be deleted\n testProjects.forEach((project, index) => {\n console.log(` ${index + 1}. \"${project.data.title}\" (oid: ${project.oid})`);\n });\n\n // Step 3: Confirm deletion\n console.log(`\\n⚠️ About to delete ${testProjects.length} test projects!`);\n console.log(\"This action cannot be undone.\");\n \n // In a real environment, you might want to add a confirmation prompt\n // For automation, we'll proceed directly\n \n // Step 4: Delete projects\n let deletedCount = 0;\n let errorCount = 0;\n\n console.log(\"\\n🗑️ Starting deletion process...\");\n\n for (const project of testProjects) {\n try {\n console.log(`🔄 Deleting \"${project.data.title}\"...`);\n\n // Mark project as deleted\n const updatedProjectData = {\n ...project.data,\n deleted: true,\n deletedAt: new Date().toISOString(),\n updatedAt: new Date().toISOString(),\n };\n\n const deleteResponse = await makeGigyaRequest(\"ds.store\", {\n type: \"oss_projects\",\n data: JSON.stringify(updatedProjectData),\n oid: project.oid,\n });\n\n if (deleteResponse.errorCode === 0) {\n console.log(`✅ Successfully deleted \"${project.data.title}\"`);\n deletedCount++;\n } else {\n console.error(`❌ Failed to delete \"${project.data.title}\": ${deleteResponse.errorMessage}`);\n errorCount++;\n }\n\n // Add delay to avoid rate limiting\n await new Promise((resolve) => setTimeout(resolve, 100));\n\n } catch (error) {\n console.error(`❌ Error deleting project \"${project.data.title}\":`, error);\n errorCount++;\n }\n }\n\n console.log(\"\\n📊 Deletion Summary:\");\n console.log(`✅ Successfully deleted: ${deletedCount} projects`);\n console.log(`❌ Errors: ${errorCount} projects`);\n console.log(`📁 Total processed: ${deletedCount + errorCount} projects`);\n\n return { deletedCount, errorCount };\n\n } catch (error) {\n console.error(\"❌ Error during deletion process:\", error);\n throw error;\n }\n}\n\nasync function verifyDeletion() {\n console.log(\"\\n🔍 Verifying deletion...\");\n \n try {\n // Check for remaining test projects\n const response = await makeGigyaRequest(\"ds.search\", {\n query: \"SELECT * FROM oss_projects WHERE deleted != true\",\n });\n\n if (response.errorCode === 0) {\n const remainingProjects = response.results || [];\n const remainingTestProjects = remainingProjects.filter(project => \n isTestProject(project.data.title)\n );\n \n console.log(`✅ Verification complete:`);\n console.log(` 📝 Total active projects: ${remainingProjects.length}`);\n console.log(` 🧪 Remaining test projects: ${remainingTestProjects.length}`);\n \n if (remainingTestProjects.length > 0) {\n console.log(\"\\n⚠️ Test projects still found:\");\n remainingTestProjects.forEach((project, index) => {\n console.log(` ${index + 1}. \"${project.data.title}\" (oid: ${project.oid})`);\n });\n } else {\n console.log(\"🎉 All test projects have been successfully deleted!\");\n }\n\n // Also check deleted projects\n const deletedResponse = await makeGigyaRequest(\"ds.search\", {\n query: \"SELECT * FROM oss_projects WHERE deleted = true\",\n });\n\n if (deletedResponse.errorCode === 0) {\n const deletedProjects = deletedResponse.results || [];\n const deletedTestProjects = deletedProjects.filter(project => \n isTestProject(project.data.title)\n );\n console.log(`🗑️ Deleted test projects: ${deletedTestProjects.length}`);\n }\n\n } else {\n console.error(\"❌ Verification failed:\", response.errorMessage);\n }\n } catch (error) {\n console.error(\"❌ Error during verification:\", error);\n }\n}\n\n// Run the script\ndeleteTestProjects()\n .then(async (result) => {\n await verifyDeletion();\n \n if (result.deletedCount > 0) {\n console.log(\"\\n🎉 Test project deletion completed successfully!\");\n console.log(\"\\nNext steps:\");\n console.log(\"1. Verify the application no longer shows the deleted test projects\");\n console.log(\"2. Check that legitimate projects remain unaffected\");\n } else if (result.errorCount > 0) {\n console.log(\"\\n⚠️ Some deletions failed. Check the errors above.\");\n } else {\n console.log(\"\\n✅ No test projects were found to delete.\");\n }\n })\n .catch((error) => {\n console.error(\"❌ Script execution failed:\", error);\n process.exit(1);\n });",[],[389],{"_104":397,"_97":398,"_161":399,"_163":-5,"_164":146,"_165":400,"_167":118,"_106":401,"_101":402,"_169":190,"_171":403,"_172":22,"_173":-5,"_174":404,"_100":405},"cfe1306a-4216-11f0-98c9-76b3cceeab13","ds-schema.ts","e4ab55a4-4214-11f0-997e-76b3cceeab13",26,["D",1749132619268],12,"// Script to create Gigya DS schema for the OSS Contribution project\n\nconst GIGYA_DOMAIN = process.env.GIGYA_DOMAIN || \"accounts.eu1.gigya.com\";\nconst GIGYA_API_KEY = process.env.GIGYA_API_KEY;\nconst GIGYA_APP_KEY = process.env.GIGYA_APP_KEY;\nconst GIGYA_APP_SECRET = process.env.GIGYA_APP_SECRET;\n\nif (!GIGYA_API_KEY || !GIGYA_APP_KEY || !GIGYA_APP_SECRET) {\n console.error(\"Missing Gigya environment variables!\");\n console.log(\"Required variables: GIGYA_API_KEY, GIGYA_APP_KEY, GIGYA_APP_SECRET\");\n process.exit(1);\n}\n\nasync function makeGigyaRequest(endpoint, params) {\n const url = `https://${GIGYA_DOMAIN}/${endpoint}?httpStatusCodes=true`;\n\n const body = new URLSearchParams({\n apiKey: GIGYA_API_KEY,\n userKey: GIGYA_APP_KEY,\n secret: GIGYA_APP_SECRET,\n ...params,\n });\n\n const response = await fetch(url, {\n method: \"POST\",\n headers: { \"Content-Type\": \"application/x-www-form-urlencoded\" },\n body,\n });\n\n if (!response.ok) {\n const text = await response.text();\n throw new Error(`${response.statusText}: ${text}`);\n }\n\n const text = await response.text();\n return JSON.parse(text);\n}\n\nasync function createDSSchema() {\n console.log(\"Creating Gigya DS schema for OSS Contribution project...\");\n\n // Define the schema for projects\n const projectSchema = {\n dynamicSchema: true,\n fields: {\n \"id\": {\n type: \"long\",\n writeAccess: \"clientModify\",\n },\n \"title\": {\n type: \"text\",\n writeAccess: \"clientModify\",\n },\n \"description\": {\n type: \"text\",\n writeAccess: \"clientModify\",\n },\n \"repositoryUrl\": {\n type: \"text\",\n writeAccess: \"clientModify\",\n },\n \"votes\": {\n type: \"long\",\n writeAccess: \"serverOnly\",\n },\n \"comments\": {\n type: \"long\",\n writeAccess: \"clientModify\",\n },\n \"commitment\": {\n type: \"text\",\n writeAccess: \"clientModify\",\n },\n \"skills\": {\n type: \"text\",\n writeAccess: \"clientModify\",\n },\n \"contribution\": {\n type: \"text\",\n writeAccess: \"clientModify\",\n },\n \"author\": {\n type: \"text\",\n writeAccess: \"clientModify\",\n },\n \"enabled\": {\n type: \"boolean\",\n writeAccess: \"clientModify\",\n },\n \"createdAt\": {\n type: \"date\",\n writeAccess: \"clientModify\",\n },\n \"updatedAt\": {\n type: \"date\",\n writeAccess: \"clientModify\",\n },\n \"deleted\": {\n type: \"boolean\",\n writeAccess: \"clientModify\",\n },\n \"deletedAt\": {\n type: \"date\",\n writeAccess: \"serverOnly\",\n },\n },\n };\n\n try {\n // Create the schema\n console.log(\"Creating schema for type: oss_projects\");\n\n const response = await makeGigyaRequest(\"ds.setSchema\", {\n type: projectSchema.type,\n dynamicSchema: true,\n dataSchema: JSON.stringify(projectSchema),\n });\n\n if (response.errorCode === 0) {\n console.log(\"✅ Schema created successfully for oss_projects\");\n } else {\n console.error(\"❌ Failed to create schema:\", response.errorMessage);\n return false;\n }\n\n // Verify the schema was created\n console.log(\"Verifying schema...\");\n const verifyResponse = await makeGigyaRequest(\"ds.getSchema\", {\n type: projectSchema.type,\n });\n\n if (verifyResponse.errorCode === 0) {\n console.log(\"✅ Schema verification successful\");\n console.log(\n \"Schema fields:\",\n Object.keys(verifyResponse.schema).map((fieldName) => {\n const field = verifyResponse.schema[fieldName];\n return `${fieldName} (${field.type || \"unknown\"}, ${field.writeAccess || \"serverOnly\"})`;\n }).join(\", \"),\n );\n } else {\n console.error(\"❌ Schema verification failed:\", verifyResponse.errorMessage);\n }\n\n return true;\n } catch (error) {\n console.error(\"❌ Error creating DS schema:\", error.message);\n return false;\n }\n}\n\n// Run the script\ncreateDSSchema()\n .then((success) => {\n if (success) {\n console.log(\"\\n🎉 DS Schema creation completed successfully!\");\n console.log(\"\\nNext steps:\");\n console.log(\"1. Run the data loading script to populate projects\");\n console.log(\"2. Test the application with the new schema\");\n } else {\n console.log(\"\\n❌ DS Schema creation failed!\");\n process.exit(1);\n }\n })\n .catch((error) => {\n console.error(\"❌ Script execution failed:\", error);\n process.exit(1);\n });",[],[398],{"_104":407,"_97":408,"_161":409,"_163":-5,"_164":146,"_165":410,"_167":118,"_106":411,"_101":412,"_169":316,"_171":413,"_172":22,"_173":-5,"_174":414,"_100":415},"59e4a904-455f-11f0-aea3-76b3cceeab13","ds.md","2d119888-455f-11f0-9abf-76b3cceeab13",81,["D",1749493628075],3,"# SAP Customer Data Cloud\n\nGenerated on: 2025-06-09 18:21:06 GMT+\n\nSAP Customer Data Cloud | SHIP\n\nPublic\n\nOriginal content: https://help.sap.com/docs/SAP_CUSTOMER_DATA_CLOUD/8b8d6fffe113457094a17701f63e3d6a?locale=en-\n\nUS&state=PRODUCTION&version=SHIP\n\n### Warning\n\nThis document has been generated from SAP Help Portal and is an incomplete version of the official SAP product documentation.\n\nThe information included in custom documentation may not reect the arrangement of topics in SAP Help Portal, and may be\n\nmissing important aspects and/or correlations to other topics. For this reason, it is not for production use.\n\nFor more information, please visit https://help.sap.com/docs/disclaimer.\n\n\n## Data Store REST\n\nSAP Customer Data Cloud's Data Store (DS) API consists of the methods listed below.\n\n```\nds.delete REST\n```\n```\nds.deleteSchemaFields REST\n```\n```\nds.get REST\n```\n```\nds.getSchema REST\nds.getTypes REST\n```\n```\nds.search REST\n```\n```\nds.setSchema REST\nds.store REST\n```\n## ds.delete REST\n\n## Description\n\nDeletes object data or an entire object from Gigya's Data Store.\n\n## Request URL\n\n#### https://ds./ds.delete\n\nWhere is:\n\n#### us1.gigya.com - For the US data center.\n\n#### eu1.gigya.com - For the European data center.\n\n#### au1.gigya.com - For the Australian data center.\n\n#### eu2.gigya.com - For the European Azure data center.\n\n#### cn1.sapcdm.cn - For the Chinese data center.\n\n###  Note\n\n```\nIf you plan on integrating the DS, we highly recommend reading the Data Store Guide.\n```\n```\nThe DS is a premium platform that requires separate activation. If the DS is not part of your site package contact your SAP\nCustomer Data Cloud Customer Engagement Executive or email support@gigya-inc.com.\n```\n###  Note\n\n```\nIf you plan on integrating the DS, we highly recommend reading the Data Store Guide.\n```\n```\nThe DS is a premium platform that requires separate activation. If the DS is not part of your site package contact your Gigya\nCustomer Engagement Executive or email support@gigya-inc.com.\n```\n\n#### global.gigya.com - For all Global site groups.\n\nIf you are not sure of your site's data center, see Finding Your Data Center.\n\n## Parameters\n\n```\nRequired Name Type Description\n```\n```\noid string The ID of the object to delete.\n```\n```\ntype string A string indicating the type of the\nobject.\n```\n```\nelds string A comma separated list of elds\nto delete. Acceptable values for\nthis parameter:\n```\n```\nData eld names,\nspecifying the the\ncomplete path, i.e.\nalbum.photo.photoTitle_t\n```\n```\nPartial eld names (elds\nthat contain only a part\nof the path to sub-\nobjects, i.e. album.photo)\n```\n- indicate to retrieve\neverything below that\npath.\n\n```\n\"*\" - indicates to retrieve\nthe entire stored object.\n```\n```\nUID string If the object is associate with a\nuser, then the ID of the user\nshould be specied and forms a\ncompound key together with the\noid.\n```\n```\n* If you call this method through\nan external OAuth2 SDK, then\nthe UID may be passed implicitly\nwithin the access_token.\n```\n```\nformat string Determines the format of the\nresponse.\n```\n```\njson (default)\n```\n```\ncontext string/JSON This parameter may be used to\npass data through the current\nmethod and return it,\nunchanged, within the response.\n```\n```\nignoreInterruptions Boolean This may be used in some cases\nto suppress logic applied by the\nWeb SDK, such as automatic\nopening of screens (e.g., in a\nregistration completion\n```\n\n```\nRequired Name Type Description\n```\n```\nscenario). This parameter may\nnot be used with REST APIs.\n```\n```\nhttpStatusCodes Boolean The default value of this\nparameter is false, which means\nthat the HTTP status code in\nSAP Customer Data Cloud's\nresponse is always 200 (OK),\neven if an error occurs. The error\ncode and message is given within\nthe response data (see below). If\nthis parameter is set to true, the\nHTTP status code in SAP\nCustomer Data Cloud's response\nwould reect an error, if one\noccurred.\n```\n## Authorization Parameters\n\nEach REST API request must contain identication and authorization parameters.\n\nSome REST APIs may function without these authorization parameters, however, when that occurs, these calls are treated as\n\nclient-side calls and all client-side rate limits will apply. In order to not reach client-side IP rate limits that may impact your\n\nimplementation when using server-to-server REST calls, it is Recommended Best Practice to always use an application key and\n\nsecret or a bearer token when sending requests. A non-exhaustive list of REST APIs that this may apply to are as follows:\n\n```\naccounts.login\n```\n```\nsocialize.login\n```\n```\naccounts.notifyLogin\n```\n```\nsocialize.notifyLogin\n```\n```\naccounts.nalizeRegistration\n```\n```\naccounts.linkAccounts\n```\nPlease refer to the Authorization Parameters section for details.\n\n## Sample Requests\n\n###  Note\n\n```\nAs of January 31, 2023, you may no longer use a Partner Secret as a valid authentication method for requests to SAP Customer\nData Cloud servers.\n```\n\n## Response Data\n\n```\nField Type Description\n```\n```\napiVersion integer Denes the API version that returned the\nresponse and may not always be returned.\n```\n```\ncallId string Unique identier of the transaction, for\ndebugging purposes.\n```\n```\nerrorCode integer The result code of the operation. Code '0'\nindicates success, any other number\nindicates failure. For a complete list of error\ncodes, see the Error Codes table.\n```\n```\nerrorDetails string This eld will appear in the response only in\ncase of an error and will contain the\nexception info, if available.\n```\n```\nerrorMessage string\n```\n```\nfullEventName string The full name of the event that triggered\nthe response. This is an internally used\nparameter that is not always returned and A\n```\n```\nCopyright Disclaimer Privacy Statement Legal Disclosure Trademark Terms of Use\n```\n\n```\nField Type Description\n```\n```\nshort textual description of an error,\nassociated with the errorCode, for logging\npurposes. This eld will appear in the\nresponse only in case of an error.should not\nbe relied upon by your implementation.\n```\n```\ntime string The time of the response represented in\nISO 8601 format: yyyy-mm-dd-\nThh:MM:ss.SSSZ (for example, 2021-03-\n05T06:11:31.513Z)\n```\n```\nstatusCode integer The HTTP response code of the operation.\nCode '200' indicates success.\n```\n```\nThis property is deprecated and only\nreturned for backward compatibility.\n```\n```\nstatusReason string A brief explanation of the status code.\n```\n```\nThis property is deprecated and only\nreturned for backward compatibility.\n```\n### Response Example\n\n## ds.deleteSchemaFields REST\n\n## Description\n\nDeletes a eld from a specied Gigya Data Store schema type.\n\nOnce a eld is deleted:\n\n```\nYou cannot save data to that eld, nor retrieve data that was saved to that eld.\n```\n```\nYou cannot recreate a eld of the same name in the schema.\n```\nThis parameter or feature is part of our Early Adopters Program. To nd out if you are eligible for participation, contact your SAP\n\nCustomer Data Cloud Customer Engagement Executive or contact us at SAP Support.\n\n##### {\n\n```\n\"statusCode\": 200,\n\"errorCode\": 0,\n\"statusReason\": \"OK\",\nA short textua\"callId\": \"31ba039fb8d340ceb2f43d52c89bf187\",\n\"time\": \"2015-03-22T11:42:25.943Z\"\n}\n```\n###  Note\n\n```\nIf you plan on integrating the DS, we highly recommend reading the Data Store Guide.\n```\n```\nThe DS is a premium platform that requires separate activation. If the DS is not part of your site package, contact your SAP\nCustomer Data Cloud Customer Engagement Executive or contact us at SAP Support.\n```\n\n## Request URL\n\n#### https://ds./ds.deleteSchemaFields\n\nWhere is:\n\n#### us1.gigya.com - For the US data center.\n\n#### eu1.gigya.com - For the European data center.\n\n#### au1.gigya.com - For the Australian data center.\n\n#### eu2.gigya.com - For the European Azure data center.\n\n#### cn1.sapcdm.cn - For the Chinese data center.\n\n#### global.gigya.com - For all Global site groups.\n\nIf you are not sure of your site's data center, see Finding Your Data Center.\n\n## Parameters\n\n```\nRequired Name Type Description\n```\n```\ntype string The schema type dened in the\nData Store from which to delete\nelds.\n```\n```\ndataSchema array The elds to delete from the\nspecied Data Store type. For\nexample:\n```\n```\nformat string Determines the format of the\nresponse.\n```\n```\njson (default)\n```\n```\ncontext string/JSON This parameter may be used to\npass data through the current\nmethod and return it,\nunchanged, within the\nresponse.\n```\n```\nignoreInterruptions Boolean This may be used in some cases\nto suppress logic applied by the\nWeb SDK, such as automatic\nopening of screens (e.g., in a\nregistration completion\nscenario). This parameter may\nnot be used with REST APIs.\n```\n```\nhttpStatusCodes Boolean The default value of this\nparameter is false, which means\nthat the HTTP status code in\nSAP Customer Data Cloud's\nresponse is always 200 (OK),\neven if an error occurs. The\n```\n```\n[\"field1\",\"field2\"]\n```\n\n```\nRequired Name Type Description\n```\n```\nerror code and message is given\nwithin the response data (see\nbelow). If this parameter is set\nto true, the HTTP status code in\nSAP Customer Data Cloud's\nresponse would reect an error,\nif one occurred.\n```\n## Authorization Parameters\n\nEach REST API request must contain identication and authorization parameters.\n\nSome REST APIs may function without these authorization parameters, however, when that occurs, these calls are treated as\n\nclient-side calls and all client-side rate limits will apply. In order to not reach client-side IP rate limits that may impact your\n\nimplementation when using server-to-server REST calls, it is Recommended Best Practice to always use an application key and\n\nsecret or a bearer token when sending requests. A non-exhaustive list of REST APIs that this may apply to are as follows:\n\n```\naccounts.login\n```\n```\nsocialize.login\n```\n```\naccounts.notifyLogin\n```\n```\nsocialize.notifyLogin\n```\n```\naccounts.nalizeRegistration\n```\n```\naccounts.linkAccounts\n```\nPlease refer to the Authorization Parameters section for details.\n\n## Sample Requests\n\n###  Note\n\n```\nAs of January 31, 2023, you may no longer use a Partner Secret as a valid authentication method for requests to SAP Customer\nData Cloud servers.\n```\n\n## Response Data\n\n```\nField Type Description\n```\n```\napiVersion integer Denes the API version that returned the\nresponse and may not always be returned.\n```\n```\ncallId string Unique identier of the transaction, for\ndebugging purposes.\n```\n```\nerrorCode integer The result code of the operation. Code '0'\nindicates success, any other number\nindicates failure. For a complete list of error\ncodes, see the Error Codes table.\n```\n```\nerrorDetails string This eld will appear in the response only in\ncase of an error and will contain the\nexception info, if available.\n```\n```\nerrorMessage string A short textual description of an error,\nassociated with the errorCode, for logging\npurposes. This eld will appear in the\nresponse only in case of an error.\n```\n```\nCopyright Disclaimer Privacy Statement Legal Disclosure Trademark Terms of Use\n```\n\n```\nField Type Description\n```\n```\nfullEventName string The full name of the event that triggered\nthe response. This is an internally used\nparameter that is not always returned and\nshould not be relied upon by your\nimplementation.\n```\n```\ntime string The time of the response represented in\nISO 8601 format: yyyy-mm-dd-\nThh:MM:ss.SSSZ (for example, 2021-03-\n05T06:11:31.513Z)\n```\n```\nstatusCode integer The HTTP response code of the operation.\nCode '200' indicates success.\n```\n```\nThis property is deprecated and only\nreturned for backward compatibility.\n```\n```\nstatusReason string A brief explanation of the status code.\n```\n```\nThis property is deprecated and only\nreturned for backward compatibility.\n```\n### Response Example\n\n## ds.get REST\n\n## Description\n\nRetrieves an object's or the specied datum from Gigya's Data Store.\n\n## Request URL\n\n#### https://ds./ds.get\n\nWhere is:\n\n#### us1.gigya.com - For the US data center.\n\n##### {\n\n```\n\"statusCode\": 200,\n\"errorCode\": 0,\n\"statusReason\": \"OK\",\n\"callId\": \"31ba039fb8d340ceb2f43d52c89bf187\",\n\"time\": \"2015-03-22T11:42:25.943Z\"\n}\n```\n###  Note\n\n```\nIf you plan on integrating the DS, we highly recommend reading the Data Store Guide.\n```\n```\nThe DS is a premium platform that requires separate activation. If the DS is not part of your site package contact your Gigya\nCustomer Engagement Executive or email support@gigya-inc.com.\n```\n\n#### eu1.gigya.com - For the European data center.\n\n#### au1.gigya.com - For the Australian data center.\n\n#### eu2.gigya.com - For the European Azure data center.\n\n#### cn1.sapcdm.cn - For the Chinese data center.\n\n#### global.gigya.com - For all Global site groups.\n\nIf you are not sure of your site's data center, see Finding Your Data Center.\n\n## Parameters\n\n```\nRequired Name Type Description\n```\n```\noid string The ID of the object to retrieve.\n```\n```\ntype string A string indicating the type of the\nobject, equivalent to a name\nclassifying objects as being of\nthe same type; used in searches\nand when applying schemas.\n```\n```\nelds string A comma separated list of elds\nto retrieve. Acceptable values for\nthis parameter:\n```\n```\nData eld names,\nspecifying the the\ncomplete path, i.e.\nalbum.photo.photoTitle_t\n```\n```\nPartial eld names (elds\nthat contain only a part\nof the path to sub-\nobjects, i.e. album.photo)\n```\n- indicate to retrieve\neverything below that\npath.\n\n```\n\"*\" - indicates to retrieve\nthe entire stored object.\n```\n```\nUID string If the object is associate with a\nuser, then the ID of the user\nshould be specied and forms a\ncompound key together with the\noid.\n```\n```\n* If you call this method through\nan external OAuth2 SDK, then\nthe UID may be passed implicitly\nwithin the access_token.\n```\n```\nformat string Determines the format of the\nresponse.\n```\n```\njson (default)\n```\n\n```\nRequired Name Type Description\n```\n```\ncontext string/JSON This parameter may be used to\npass data through the current\nmethod and return it,\nunchanged, within the response.\n```\n```\nignoreInterruptions Boolean This may be used in some cases\nto suppress logic applied by the\nWeb SDK, such as automatic\nopening of screens (e.g., in a\nregistration completion\nscenario). This parameter may\nnot be used with REST APIs.\n```\n```\nhttpStatusCodes Boolean The default value of this\nparameter is false, which means\nthat the HTTP status code in\nSAP Customer Data Cloud's\nresponse is always 200 (OK),\neven if an error occurs. The error\ncode and message is given within\nthe response data (see below). If\nthis parameter is set to true, the\nHTTP status code in SAP\nCustomer Data Cloud's response\nwould reect an error, if one\noccurred.\n```\n## Authorization Parameters\n\nEach REST API request must contain identication and authorization parameters.\n\nSome REST APIs may function without these authorization parameters, however, when that occurs, these calls are treated as\n\nclient-side calls and all client-side rate limits will apply. In order to not reach client-side IP rate limits that may impact your\n\nimplementation when using server-to-server REST calls, it is Recommended Best Practice to always use an application key and\n\nsecret or a bearer token when sending requests. A non-exhaustive list of REST APIs that this may apply to are as follows:\n\n```\naccounts.login\n```\n```\nsocialize.login\n```\n```\naccounts.notifyLogin\n```\n```\nsocialize.notifyLogin\n```\n```\naccounts.nalizeRegistration\n```\n```\naccounts.linkAccounts\n```\nPlease refer to the Authorization Parameters section for details.\n\n###  Note\n\n```\nAs of January 31, 2023, you may no longer use a Partner Secret as a valid authentication method for requests to SAP Customer\nData Cloud servers.\n```\n\n## Sample Requests\n\n## Response Data\n\n```\nField Type Description\n```\n```\napiVersion integer Denes the API version that returned the\nresponse and may not always be returned.\n```\n```\ncallId string Unique identier of the transaction, for\ndebugging purposes.\n```\n```\nerrorCode integer The result code of the operation. Code '0'\nindicates success, any other number\nindicates failure. For a complete list of error\ncodes, see the Error Codes table.\n```\n```\nerrorDetails string This eld will appear in the response only in\ncase of an error and will contain the\nexception info, if available.\n```\n```\nerrorMessage string A short textual description of an error,\nassociated with the errorCode, for logging\n```\n```\nCopyright Disclaimer Privacy Statement Legal Disclosure Trademark Terms of Use\n```\n\n```\nField Type Description\n```\n```\npurposes. This eld will appear in the\nresponse only in case of an error.\n```\n```\nfullEventName string The full name of the event that triggered\nthe response. This is an internally used\nparameter that is not always returned and\nshould not be relied upon by your\nimplementation.\n```\n```\ntime string The time of the response represented in\nISO 8601 format: yyyy-mm-dd-\nThh:MM:ss.SSSZ (for example, 2021-03-\n05T06:11:31.513Z)\n```\n```\nstatusCode integer The HTTP response code of the operation.\nCode '200' indicates success.\n```\n```\nThis property is deprecated and only\nreturned for backward compatibility.\n```\n```\nstatusReason string A brief explanation of the status code.\n```\n```\nThis property is deprecated and only\nreturned for backward compatibility.\n```\n```\ndata JSON object The object data retrieved from Gigya's Data\nStore.\n```\n```\noid string The ID of the object\n```\n```\nUID string If the object is associate with a user, then\nthe ID of the user.\n```\n```\nlastUpdated long The time of the latest change in this object,\nin Java time (number of milliseconds since\nJan. 1st 1970).\n```\n```\nlastUpdatedTime string The time of the latest change in this object,\nin ISO 8601 format.\n```\n```\ncreated long The time of this object's creation, in Java\ntime (number of milliseconds since Jan. 1st\n1970).\n```\n```\ncreatedTime string The time of this object's creation, in ISO\n8601 format.\n```\n### Response Example\n\n##### {\n\n```\n\"data\": {\n\"BloodType\": \"A\",\n\"Dislikes\": \"Evil\",\n\"EyeColor\": \"Brown\",\n\"HairColor\": \"Brown\",\n\"Height\": \"179 cms\",\n\"Likes\": \"Justice\",\n\"Occupation\": \"QA\",\n\"Weight\": \"94.1 kgs\"\n},\n\"oid\": \"8b8972c3b3114db2a0acdfa2617693bf\",\n```\n\n## ds.getSchema REST\n\n## Description\n\nThis method retrieves the schema of a specied data type in Gigya's Data Store (DS).\n\n## Request URL\n\n#### https://ds./ds.getSchema\n\nWhere is:\n\n#### us1.gigya.com - For the US data center.\n\n#### eu1.gigya.com - For the European data center.\n\n#### au1.gigya.com - For the Australian data center.\n\n#### eu2.gigya.com - For the European Azure data center.\n\n#### cn1.sapcdm.cn - For the Chinese data center.\n\n#### global.gigya.com - For all Global site groups.\n\nIf you are not sure of your site's data center, see Finding Your Data Center.\n\n## Parameters\n\n```\nRequired Name Type Description\n```\n```\ntype string A string indicating the type of\nthe object, equivalent to a\nschema name. To see all the\n```\n```\n\"lastUpdatedTime\": \"2012-08-08T12:16:24Z\",\n\"lastUpdated\": 1344428184385,\n\"createdTime\": \"2012-08-08T12:16:24Z\",\n\"created\": 1344428184385,\n\"statusCode\": 200,\n\"errorCode\": 0,\n\"statusReason\": \"OK\",\n\"callId\": \"d02ada709b494be18d47cab5a23c3470\",\n\"time\": \"2015-03-22T11:42:25.943Z\"\n}\n```\n###  Note\n\n```\nFor security reasons this method is not available for client-side SDKs, only for server-side SDKs.\n```\n###  Note\n\n```\nIf you plan on integrating the DS, we highly recommend reading the Data Store Guide.\n```\n```\nThe DS is a premium platform that requires separate activation. If the DS is not part of your site package contact your Gigya\nCustomer Engagement Executive or email support@gigya-inc.com.\n```\n\nRequired Name Type Description\n\n```\ntypes currently dened in the\nschema, use ds.getTypes or the\nSchema Editor.\n```\n```\nlter string Species what parts of the\nschema to return, can be one of\nthe following options:\n```\n```\nfull - (default) return the\ncomplete schema\nincluding implicit elds\nand dynamic elds.\n```\n```\nexplicitOnly - return\nonly the parts of the\nschema that were\nexplicitly set by the\npartner using a\nsetSchema call.\n```\n```\nclientOnly - return only\nthe elds in the schema\nthat allow client access.\nFor those elds return\nonly the type and\nformat and required\nproperties (see the\nformat denition of the\nschema object).\n```\n```\nformat string Determines the format of the\nresponse.\n```\n```\njson (default)\n```\n```\ncontext string/JSON This parameter may be used to\npass data through the current\nmethod and return it,\nunchanged, within the\nresponse.\n```\n```\nignoreInterruptions Boolean This may be used in some cases\nto suppress logic applied by the\nWeb SDK, such as automatic\nopening of screens (e.g., in a\nregistration completion\nscenario). This parameter may\nnot be used with REST APIs.\n```\n```\nhttpStatusCodes Boolean The default value of this\nparameter is false, which means\nthat the HTTP status code in\nSAP Customer Data Cloud's\nresponse is always 200 (OK),\neven if an error occurs. The\nerror code and message is given\nwithin the response data (see\nbelow). If this parameter is set\nto true, the HTTP status code in\n```\n\n```\nRequired Name Type Description\n```\n```\nSAP Customer Data Cloud's\nresponse would reect an error,\nif one occurred.\n```\n```\nincludeDynamicSchema Boolean Deprecated. When it is explicitly\nset to false it should be\ninterpreted as\nschemaType=explicit.\n```\n## Authorization Parameters\n\nEach REST API request must contain identication and authorization parameters.\n\nSome REST APIs may function without these authorization parameters, however, when that occurs, these calls are treated as\n\nclient-side calls and all client-side rate limits will apply. In order to not reach client-side IP rate limits that may impact your\n\nimplementation when using server-to-server REST calls, it is Recommended Best Practice to always use an application key and\n\nsecret or a bearer token when sending requests. A non-exhaustive list of REST APIs that this may apply to are as follows:\n\n```\naccounts.login\n```\n```\nsocialize.login\n```\n```\naccounts.notifyLogin\n```\n```\nsocialize.notifyLogin\n```\n```\naccounts.nalizeRegistration\n```\n```\naccounts.linkAccounts\n```\nPlease refer to the Authorization Parameters section for details.\n\n## Sample Requests\n\n###  Note\n\n```\nAs of January 31, 2023, you may no longer use a Partner Secret as a valid authentication method for requests to SAP Customer\nData Cloud servers.\n```\n\n## Response Data\n\n```\nField Type Description\n```\n```\napiVersion integer Denes the API version that returned the\nresponse and may not always be returned.\n```\n```\ncallId string Unique identier of the transaction, for\ndebugging purposes.\n```\n```\nerrorCode integer The result code of the operation. Code '0'\nindicates success, any other number\nindicates failure. For a complete list of error\ncodes, see the Error Codes table.\n```\n```\nerrorDetails string This eld will appear in the response only in\ncase of an error and will contain the\nexception info, if available.\n```\n```\nerrorMessage string A short textual description of an error,\nassociated with the errorCode, for logging\npurposes. This eld will appear in the\nresponse only in case of an error.\n```\n```\nCopyright Disclaimer Privacy Statement Legal Disclosure Trademark Terms of Use\n```\n\n```\nField Type Description\n```\n```\nfullEventName string The full name of the event that triggered\nthe response. This is an internally used\nparameter that is not always returned and\nshould not be relied upon by your\nimplementation.\n```\n```\ntime string The time of the response represented in\nISO 8601 format: yyyy-mm-dd-\nThh:MM:ss.SSSZ (for example, 2021-03-\n05T06:11:31.513Z)\n```\n```\nstatusCode integer The HTTP response code of the operation.\nCode '200' indicates success.\n```\n```\nThis property is deprecated and only\nreturned for backward compatibility.\n```\n```\nstatusReason string A brief explanation of the status code.\n```\n```\nThis property is deprecated and only\nreturned for backward compatibility.\n```\n```\nschema JSON object A JSON object that details the schema\nstructure. See the format denition of the\nschema object.\n```\n### Response Example\n\n## ds.getTypes REST\n\n## Description\n\nThis method retrieves the schema data types dened in Gigya's Data Store (DS).\n\n##### {\n\n```\n\"schema\": {\n\"fields\": {\n\"customField1\": {\n\"type\": \"integer\"\n},\n\"customField2\": {\n\"type\": \"string\"\n},\n\"customField3\": {\n\"type\": \"string\"\n}\n},\n\"dynamicSchema\": false\n},\n\"statusCode\": 200,\n\"errorCode\": 0,\n\"statusReason\": \"OK\",\n\"callId\": \"0d8382a314ac4329a53add3067e863d9\",\n\"time\": \"2015-03-22T11:42:25.943Z\"\n}\n```\n###  Note\n\n\n## Request URL\n\n#### https://ds./ds.getTypes\n\nWhere is:\n\n#### us1.gigya.com - For the US data center.\n\n#### eu1.gigya.com - For the European data center.\n\n#### au1.gigya.com - For the Australian data center.\n\n#### eu2.gigya.com - For the European Azure data center.\n\n#### cn1.sapcdm.cn - For the Chinese data center.\n\n#### global.gigya.com - For all Global site groups.\n\nIf you are not sure of your site's data center, see Finding Your Data Center.\n\n## Authorization Parameters\n\nEach REST API request must contain identication and authorization parameters.\n\nSome REST APIs may function without these authorization parameters, however, when that occurs, these calls are treated as\n\nclient-side calls and all client-side rate limits will apply. In order to not reach client-side IP rate limits that may impact your\n\nimplementation when using server-to-server REST calls, it is Recommended Best Practice to always use an application key and\n\nsecret or a bearer token when sending requests. A non-exhaustive list of REST APIs that this may apply to are as follows:\n\n```\naccounts.login\n```\n```\nsocialize.login\n```\n```\naccounts.notifyLogin\n```\n```\nsocialize.notifyLogin\n```\n```\naccounts.nalizeRegistration\n```\n```\naccounts.linkAccounts\n```\nPlease refer to the Authorization Parameters section for details.\n\n```\nFor security reasons this method is not available for client-side SDKs, only for server-side SDKs.\n```\n###  Note\n\n```\nIf you plan on integrating the DS, we highly recommend reading the Data Store Guide.\n```\n```\nThe DS is a premium platform that requires separate activation. If the DS is not part of your site package contact your Gigya\nCustomer Engagement Executive or email support@gigya-inc.com.\n```\n###  Note\n\n```\nAs of January 31, 2023, you may no longer use a Partner Secret as a valid authentication method for requests to SAP Customer\nData Cloud servers.\n```\n\n## Sample Requests\n\n## Response Data\n\n```\nField Type Description\n```\n```\napiVersion integer Denes the API version that returned the\nresponse and may not always be returned.\n```\n```\ncallId string Unique identier of the transaction, for\ndebugging purposes.\n```\n```\nerrorCode integer The result code of the operation. Code '0'\nindicates success, any other number\nindicates failure. For a complete list of error\ncodes, see the Error Codes table.\n```\n```\nerrorDetails string This eld will appear in the response only in\ncase of an error and will contain the\nexception info, if available.\n```\n```\nerrorMessage string A short textual description of an error,\nassociated with the errorCode, for logging\n```\n```\nCopyright Disclaimer Privacy Statement Legal Disclosure Trademark Terms of Use\n```\n\n```\nField Type Description\n```\n```\npurposes. This eld will appear in the\nresponse only in case of an error.\n```\n```\nfullEventName string The full name of the event that triggered\nthe response. This is an internally used\nparameter that is not always returned and\nshould not be relied upon by your\nimplementation.\n```\n```\ntime string The time of the response represented in\nISO 8601 format: yyyy-mm-dd-\nThh:MM:ss.SSSZ (for example, 2021-03-\n05T06:11:31.513Z)\n```\n```\nstatusCode integer The HTTP response code of the operation.\nCode '200' indicates success.\n```\n```\nThis property is deprecated and only\nreturned for backward compatibility.\n```\n```\nstatusReason string A brief explanation of the status code.\n```\n```\nThis property is deprecated and only\nreturned for backward compatibility.\n```\n```\ntypes array A list of the types which make up this DS\nschema.\n```\n### Response Example\n\n## ds.search REST\n\n## Description\n\nSearches and retrieves data from Gigya's Data Store (DS) using an SQL-like query. For security reasons this method is not\n\navailable for client side SDKs, only for server side SDKs. SQL queries are converted into Gigya's proprietary query language. SQL\n\ninjection attacks are not possible because queries are both created by the customer and then converted by Gigya.\n\nA short delay is possible between the writing of account data to the data base and its availability in queries.\n\n##### {\n\n```\n\"types\": [\n\"myType\"\n],\n\"statusCode\": 200,\n\"errorCode\": 0,\n\"statusReason\": \"OK\",\n\"callId\": \"f293e7d275fa4656b6bf197d90027ae2\",\n\"time\": \"2017-08-17T07:32:49.229Z\"\n}\n```\n###  Note\n\n```\nIf you plan on integrating the DS, we highly recommend reading the Data Store Guide.\n```\n\nThe DS is a premium platform that requires separate activation. If the DS is not part of your site package contact your Gigya\n\nCustomer Engagement Executive or email support@gigya-inc.com.\n\n## Query Syntax Specication\n\nGigya queries use the same syntax rules as SQL, however not all standard SQL key words are available.\n\n```\nWhen querying for string values, value must be wrapped in double quotes. e.g., SELECT * FROM data.music WHERE guitar\n= \"Fender\".\n```\n```\nWhen querying for Integer (and other non-textual elds) values, value must not be wrapped in quotes. e.g., SELECT * FROM\ndata.userAccounts WHERE age = 42.\n```\n```\nUnsupported SQL syntax in the query string (e.g., HAVING) will produce an error.\n```\n```\nThe query string clauses must be ordered in the following way*:\n```\n```\n. Select clause\n```\n```\n. From clause\n```\n```\n. Where clause\n```\n```\n. Filter clause\n```\n```\n. Group By clause\n```\n```\n. Order By clause\n```\n```\n. Start clause Or/And Limit clause\n```\n```\nDeleted objects do not appear in queries.\n```\n```\nEncrypted elds are decrypted during searches but comparison operators (>, >=, <, <=) and regex expressions are not\navailable on these elds. The Contains keyword can be used for case-insensitive searches on encrypted elds but does not\nsupport partial strings.\n```\n```\nExample queries and responses can be viewed at DS.search Examples.\n```\nselect - The \"select\" statement accepts a comma separated list of elds or objects to retrieve. Acceptable values for this\n\nstatement are:\n\n```\nField names, specifying the complete path, i.e. data.album.photo.photoTitle_t. Specifying partial elds names (data.album)\nwill return all the elds in the path.\n```\n```\nObject names, specifying an object name, i.e. user_likes will return all the elds in the user_likes object.\n```\n```\nPartial eld names (elds that contain only a part of the path to sub-objects, i.e. data.album) - will retrieve everything below\nthat path.\n```\n```\n* - will retrieve every eld in the schema.\n```\n```\ncount(*) - Returns the number of objects for a particular object type in the data store. The result is given in the response as\na single value inside the \"data\" eld.\n```\n```\nas - create an alias (temporary title) for the returned object or eld. 'Select data.track.title as song...' will return a eld\ncalled track.song containing the values of data.track.title. Example:\n```\n```\n// Query\nSELECT data.music.trackName AS Track\n// Result\n{\"results\": [\n{\"track\": {\"song\": \"I will follow\"} },\n{\"track\": {\"song\": \"Into the Heart\"} },\n{\"track\": {\"song\": \"The Ocean\"} },\n{\"track\": {\"song\": \"A Day Without Me\"} },\n{\"track\": {\"song\": \"Shadows and Trees\"} }\n],\n\"objectsCount\": 5,\n\"totalCount\": 1840,\n\"statusCode\": 200,\n```\n\n```\nsum(), min(), max(), avg(), sum_of_squares(), variance(), std() - Mathematical functions, must all be performed on the\nsame numeric eld. Fields with null values will be ignored.\n```\n```\nThe name of the eld on which the function is to be performed must be entered in the brackets. For example: 'Select\nmin(track) from data.music'.\n```\n```\nsum - provides a total for the eld in the brackets.\n```\n```\nmin/max - minimum/maximum value for the eld. If no values are found, min will return \"innity\" and max will\nreturn \"-innity\".\n```\n```\navg - average value of the eld.\n```\n```\nvariance - the extent that the eld's values vary.\n```\n```\nstd - standard deviation, the likelihood that values vary.\n```\nfrom - Name of the data source. Only one data source is supported. Queries on objects in the Data Store (DS.search) must specify\n\nthe object \"type\" classic ation as dened in the DS.store method.\n\nwhere - The \"where\" clause denes conditions for selecting items from the collection. Supported operators:\n\n```\n> , >=, <, <= , = , != - the left operand must be a data eld name (with a proper suffix letter) and the right operand must be a\nconstant of the same type as the eld. For example: \"where track.# >= 18 \".\n```\n```\nOnly = and != can be used with encrypted elds.\n```\n```\nand , or\n```\n```\ncontains, not contains - may be used only on text (string) elds and arrays.\n```\n```\nText (string) elds - support standard full text search capabilities. Contains is not case-sensitive. The left operand\nmust be a text eld name and the right operand must be a constant string. You can search for a specic word within\nthe string, for example: WHERE data.about_t CONTAINS \"music\". Underscores are treated as separators between\nwords. Contains cannot be used to locate words within encrypted elds (you must enter the full string) and is case\ninsensitive.\n```\n```\nArrays - the left operand must be an array eld name and the right operand must be a constant of the same type as\nthe array values. The array eld name must have a suffix denoting the type of the arrays values. For example:\nWHERE data.hobbies_s CONTAINS \"swimming\".\n```\n```\nin() - only retrieve items if the eld contains one of the list values. For example: 'select * from data.music where\ntrack.album_artist in (\"Elvis\", \"Beatles\", \"Santana\")' will return tracks recorded by the specied artists.\n```\n```\nis null , is not null\n```\n```\nnot\n```\n```\nregex ('') - denes a search term using regex formatting. Regex patterns cannot be used on encrypted elds.\n```\norder by - The \"order by\" clause species a list of elds by which to sort the result objects.\n\nlimit - Using the \"LIMIT\" clause, you may specify the maximum number of returned result objects. If not specied, the default is\n\n300. The maximum number of results that will be returned is 10000 ; setting a limit higher than 10000 will have no affect on\n\nnumber of results. If the search is sent with openCursor = true, LIMIT will set the batch size. LIMIT must be the last item in the\n\nquery.\n\n```\n\"errorCode\": 0,\n\"statusReason\": \"OK\",\n\"callId\": \"2222\"\n}\n```\n###  Note\n\n```\nYou can only search words that are part of a sentence, you cannot search for parts of a word.\n```\n\nstart - The \"start\" clause (not an SQL standard clause) may be used for paging. The clause species the start index from which to\n\nreturn result objects.\n\nThe 'select - from - where - order by' query creates an (internal) indexed list of objects. By using the start & limit clauses, you will\n\nreceive a subset of this list, starting with the start index and ending with start+limit index.\n\n### Query Optimization\n\nBelow are a few points to note regarding query optimization:\n\n```\n. Query execution is based on clause position and is executed from left to right.\n```\n```\n. Place clauses that have the greatest impact on records returned at the beginning of your SQL statement. For example, to\nretrieve a list of male users over the age of 25:\n```\n```\nThis is because lt ering rst by gender automatically reduces the result set by half, so the server only needs to run the next\nlt er on half of the overall population.\n```\n```\n. A NOT clause (NOT or !) is executed on a single statement immediately to it's right, after analyzing the statement. A single\nstatement can hold several conditions inside parentheses.\n```\n```\n. Date ranges are calculated much more efficiently using a timestamp eld rather than a date eld.\n```\n```\n. Use of regex is computationally intensive and can signicantly increase response time.\n```\n```\n. AND clauses take precedence over OR clauses (i.e., AND clauses are executed before OR clauses).\n```\n```\n. Use parentheses to modify default precedence (e.g., to execute an OR operation before an AND operation).\n```\n### Pagination\n\nWhen running long queries (>5,000 records returned), it's best practice to paginate your results using cursors. If you do not use\n\ncursors, results are limited to a total of 5,000 records per query (not just per page).\n\nTo use cursors, during the rst request, pass query= and openCursor=true. The response will include the\n\nnextCursorId eld, containing a cursor ID to be used in the next request. On subsequent requests, pass cursorId= and do not submit the query again. The absence of the nextCursorId eld in a response indicates the end of the\n\nresult set.\n\nWhen using openCursor, you cannot use 'START'.\n\n###  Note\n\n```\nWhen implementing paging, there is no guarantee that there will be no duplications or that recently added data will show up in\nthe query results.\n```\n###  Note\n\n```\nAlways prefer accessing data objects directly using their IDs (with ds.get) rather than using search, whenever possible.\nAccessing data objects directly using their OIDs is faster and optimal for run-time.\n```\n```\nAfter data is published to the DS, building the indexes is done asynchronously for performance reasons, and may take\nup to one second to complete.\n```\n```\nPlease note, when using a cursor, the number of results in a batch (limit) is not guaranteed.\n```\n```\nWhen querying for large numbers of results (>500) it is Best Practice to use the openCursor and then the cursorId with\nthe nextCursorId value rather than attempting to page through results using timestamps of the user records.\n```\n```\nSELECT * FROM data.userAccounts where gender=\"male\" AND age > 25\n```\n\n## Request URL\n\n#### https://ds./ds.search\n\nIf you are not sure of your site's data center, see Finding Your Data Center.\n\nWhere is:\n\n#### us1.gigya.com - For the US data center.\n\n#### eu1.gigya.com - For the European data center.\n\n#### au1.gigya.com - For the Australian data center.\n\n#### eu2.gigya.com - For the European Azure data center.\n\n#### cn1.sapcdm.cn - For the Chinese data center.\n\n#### global.gigya.com - For all Global site groups.\n\nIf you are not sure of your site's data center, see Finding Your Data Center.\n\n## Parameters\n\n```\nRequired Name Type Description\n```\n```\nquery string A SQL-like query specifying the\ndata to retrieve. Please refer to\nthe Query language\nspecication section above.\n```\n```\nquerySig string An HMAC_SHA1 signature\nproving that the search call is in\nfact coming from your client\napplication, in order to prevent\nfraud. Follow the instructions in\nConstructing a Signature using\nthe following base-string: query\n+ \"_\" + expTime. When using\ncursors, this parameter should\nonly be sent with the initial\nrequest and omitted from\nsubsequent requests.\n```\n```\nThis parameter is required only\nwhen calling the search method\nfrom client side (i.e., Mobile\nSDKs)\n```\n```\nexpTime string The GMT time when the\nquerySig parameter should\nexpire. The expected format is\nthe Unix time format (i.e., the\nnumber of seconds since Jan.\n1st 1970). Gigya checks the time\nwhen the search request is\nreceived. If the time succeeds\nexpTime, the request is\nconsidered forged.\n```\n\nRequired Name Type Description\n\n```\nThis parameter is required only\nwhen calling the search method\nfrom client side (i.e., Mobile\nSDKs)\n```\n```\nopenCursor Boolean When set to true, the search\nresponse will include, in\naddition to the rst page,\nanother eld named\nnextCursorId, which is used to\nfetch the next batch of results.\nThis parameter should only be\nused on the rst request and\nlater should be removed from\nthe request. When openCursor\nis true, the Limit clause sets the\nnumber of results returned in\nthe batch.\n```\n```\ncursorId string The cursor ID that contains the\nnextCursorId value received in\nthe rst search call. Note: You\ncannot pass both cursorId and\nquery on the same request -\ncursorId brings the next page\nfor the search for which it was\nopened. Also, the time between\nsearch requests using a\ncursorId must not exceed 5\nminutes.\n```\n```\ntimeout integer The timeout for the request (in\nmilliseconds). Default value is\n20000 (20 seconds). Maximum\n```\n###  Note\n\n```\nYou cannot use a cursor if\nyou have a 'group by' or\nwhen using 'start'.\n```\n###  Note\n\n```\nEach request should contain\na different cursorId obtained\nfrom the response of the\nprevious request (not the\nrst) using the nextCursorId\neld. The exception to this\nrule is when a request fails\nor when a particular result\nset needs to be resent; in\nthis case, resend the same\ncursorID (as long as it has\nnot expired) to receive its\nassociated result set.\n```\n\n```\nRequired Name Type Description\n```\n```\nallowed value is 60000 (60\nseconds).\n```\n```\nformat string Determines the format of the\nresponse.\n```\n```\njson (default)\n```\n```\ncontext string/JSON This parameter may be used to\npass data through the current\nmethod and return it,\nunchanged, within the\nresponse.\n```\n```\nignoreInterruptions Boolean This may be used in some cases\nto suppress logic applied by the\nWeb SDK, such as automatic\nopening of screens (e.g., in a\nregistration completion\nscenario). This parameter may\nnot be used with REST APIs.\n```\n```\nhttpStatusCodes Boolean The default value of this\nparameter is false, which means\nthat the HTTP status code in\nSAP Customer Data Cloud's\nresponse is always 200 (OK),\neven if an error occurs. The\nerror code and message is given\nwithin the response data (see\nbelow). If this parameter is set\nto true, the HTTP status code in\nSAP Customer Data Cloud's\nresponse would reect an error,\nif one occurred.\n```\n## Authorization Parameters\n\nEach REST API request must contain identication and authorization parameters.\n\nSome REST APIs may function without these authorization parameters, however, when that occurs, these calls are treated as\n\nclient-side calls and all client-side rate limits will apply. In order to not reach client-side IP rate limits that may impact your\n\nimplementation when using server-to-server REST calls, it is Recommended Best Practice to always use an application key and\n\nsecret or a bearer token when sending requests. A non-exhaustive list of REST APIs that this may apply to are as follows:\n\n```\naccounts.login\n```\n```\nsocialize.login\n```\n```\naccounts.notifyLogin\n```\n```\nsocialize.notifyLogin\n```\n```\naccounts.nalizeRegistration\n```\n```\naccounts.linkAccounts\n```\nPlease refer to the Authorization Parameters section for details.\n\n\n## Sample Requests\n\n## Response Data\n\n```\nField Type Description\n```\n```\napiVersion integer Denes the API version that returned the\nresponse and may not always be returned.\n```\n```\ncallId string Unique identier of the transaction, for\ndebugging purposes.\n```\n```\nerrorCode integer The result code of the operation. Code '0'\nindicates success, any other number\nindicates failure. For a complete list of error\ncodes, see the Error Codes table.\n```\n###  Note\n\n```\nAs of January 31, 2023, you may no longer use a Partner Secret as a valid authentication method for requests to SAP Customer\nData Cloud servers.\n```\n```\nCopyright Disclaimer Privacy Statement Legal Disclosure Trademark Terms of Use\n```\n\n```\nField Type Description\n```\n```\nerrorDetails string This eld will appear in the response only in\ncase of an error and will contain the\nexception info, if available.\n```\n```\nerrorMessage string A short textual description of an error,\nassociated with the errorCode, for logging\npurposes. This eld will appear in the\nresponse only in case of an error.\n```\n```\nfullEventName string The full name of the event that triggered\nthe response. This is an internally used\nparameter that is not always returned and\nshould not be relied upon by your\nimplementation.\n```\n```\ntime string The time of the response represented in\nISO 8601 format: yyyy-mm-dd-\nThh:MM:ss.SSSZ (for example, 2021-03-\n05T06:11:31.513Z)\n```\n```\nstatusCode integer The HTTP response code of the operation.\nCode '200' indicates success.\n```\n```\nThis property is deprecated and only\nreturned for backward compatibility.\n```\n```\nstatusReason string A brief explanation of the status code.\n```\n```\nThis property is deprecated and only\nreturned for backward compatibility.\n```\n```\ndata Array An array of data objects retrieved from the\nDS.\n```\n```\nobjectsCount integer The number of objects returned in the\n\"data\" array.\n```\n```\ntotalCount integer The total number of object that satisfy the\nquery in the DB. This is useful for knowing\nhow many objects are in the DB, when\nfetching limited amount using the \"limit\"\nparameter.\n```\n```\nnextCursorId string Used to fetch the next batch of results. This\nparameter is not returned on the last batch\nof results, its absence means that the result\nset is nished.\n```\n### Response Example\n\n##### {\n\n```\n\"results\": [{\n\"oid\": \"050\",\n\"lastUpdated\": 1344151787611,\n\"lastUpdatedTime\": \"2012-08-05T07:29:47Z\",\n\"created\": 1344151532974,\n\"createdTime\": \"2012-08-05T07:25:32Z\",\n\"data\": {\n\"FN\": 7,\n\"Fn\": 7,\n```\n\n\"field1\": 7,\n\"field2\": 7,\n\"field3\": 7,\n\"field4\": \"7\",\n\"field5\": \"7\",\n\"field6\": \"7\",\n\"field7\": \"7\",\n\"field8\": \"7\",\n\"field10\": \"d1_0\",\n\"field11\": \"d1_0\",\n\"field12\": \"d1_0\",\n\"field13\": \"d1_0\",\n\"fn\": 7\n}},\n{\n\"oid\": \"1c675e20f7724c93b9ca82aa7b206b41\",\n\"lastUpdated\": 1344172297960,\n\"lastUpdatedTime\": \"2012-08-05T13:11:37Z\",\n\"created\": 1344172297960,\n\"createdTime\": \"2012-08-05T13:11:37Z\",\n\"data\": {\n\"BloodType\": \"A\",\n\"Dislikes\": \"Evil\",\n\"EyeColor\": \"Brown\",\n\"HairColor\": \"Brown\",\n\"Height\": \"179 cms\",\n\"Likes\": \"Justice\",\n\"Occupation\": \"QA\",\n\"Weight\": \"94.1 kgs\"\n}},\n{\n\"UID\": \"_gid_t6BWv8yeJG6QZyq7Wtav1Q==\",\n\"oid\": \"51b5d8e72c664520a27c7020ff2f1494\",\n\"lastUpdated\": 1344414722808,\n\"lastUpdatedTime\": \"2012-08-08T08:32:02Z\",\n\"created\": 1344414722808,\n\"createdTime\": \"2012-08-08T08:32:02Z\",\n\"data\": {\n\"BloodType\": \"A\",\n\"Dislikes\": \"Evil\",\n\"EyeColor\": \"Brown\",\n\"HairColor\": \"Brown\",\n\"Height\": \"179 cms\",\n\"Likes\": \"Justice\",\n\"Occupation\": \"QA\",\n\"Weight\": \"94.1 kgs\"\n}},\n{\n\"oid\": \"677cc8b3437b40959b9b1288add0a2ec\",\n\"lastUpdated\": 1344172153286,\n\"lastUpdatedTime\": \"2012-08-05T13:09:13Z\",\n\"created\": 1344172153286,\n\"createdTime\": \"2012-08-05T13:09:13Z\",\n\"data\": {\n\"BloodType\": \"A\",\n\"Dislikes\": \"Evil\",\n\"EyeColor\": \"Brown\",\n\"HairColor\": \"Brown\",\n\"Height\": \"179 cms\",\n\"Likes\": \"Justice\",\n\"Occupation\": \"QA\",\n\"Weight\": \"94.1 kgs\"\n}},\n{\n\"oid\": \"8b8972c3b3114db2a0acdfa2617693bf\",\n\"lastUpdated\": 1344428184385,\n\"lastUpdatedTime\": \"2012-08-08T12:16:24Z\",\n\"created\": 1344428184385,\n\"createdTime\": \"2012-08-08T12:16:24Z\",\n\"data\": {\n\"BloodType\": \"A\",\n\"Dislikes\": \"Evil\",\n\"EyeColor\": \"Brown\",\n\"HairColor\": \"Brown\",\n\n\n## More Information\n\nds.search Examples\n\n## ds.search Examples REST\n\n## Description\n\nThis page shows examples using the ds.search REST API.\n\n## Examples\n\n```\n. Examples of searching objects by UID:\n```\n```\n1.1 First associate an object to a UID using ds.store:\n```\n```\n1.2 Search objects by UID:\n```\n```\n\"Height\": \"179 cms\",\n\"Likes\": \"Justice\",\n\"Occupation\": \"QA\",\n\"Weight\": \"94.1 kgs\"\n}},\n{\n\"oid\": \"super1\",\n\"lastUpdated\": 1344172332701,\n\"lastUpdatedTime\": \"2012-08-05T13:12:12Z\",\n\"created\": 1344172332701,\n\"createdTime\": \"2012-08-05T13:12:12Z\",\n\"data\": {\n\"BloodType\": \"A\",\n\"Dislikes\": \"Evil\",\n\"EyeColor\": \"Brown\",\n\"HairColor\": \"Brown\",\n\"Height\": \"179 cms\",\n\"Likes\": \"Justice\",\n\"Occupation\": \"QA\",\n\"Weight\": \"94.1 kgs\"\n}}],\n\"objectsCount\": 9,\n\"totalCount\": 9,\n\"statusCode\": 200,\n\"errorCode\": 0,\n\"statusReason\": \"OK\",\n\"callId\": \"fb5e8b258afc4016ad454cc9fd1d64ec\",\n\"time\": \"2015-03-22T11:42:25.943Z\"\n}\n```\n```\nds.store({\ndata:{bands:{rock:'zeppelin', jazz:'coltrain'}},\ntype:'music',\noid:'auto',\nUID='_gid_PJwNlJ5N11BLPAXIls8ty6mDdjQD6XzMT2+N/zrztsM='\n});\n```\n```\nSELECT * FROM music WHERE UID='_gid_PJwNlJ5N11BLPAXIls8ty6mDdjQD6XzMT2+N/zrztsM='\n```\n\n```\n1.3 Response to the query:\n```\n. Example of a count of objects:\n\n```\nResponse to the query:\n```\n. Example of a query using limit and start. The query lists 3 elds in a music object where the musician is \"U2\". The query is\nlimited to 5 results, starting with the 100th valid user.\n\n```\nResponse to the query:\n```\n. Example of a query using as. The query lists 3 elds in a music object where the musician is \"U2\". The query will return 5\nresults, starting with the 100th valid user.\n\n```\nResponse to the query:\n```\n##### {\n\n```\n\"results\": [\n{\n\"data\": {\n\"bands\": {\n\"jazz\": \"coltrain\",\n\"rock\": \"zeppelin\"\n}\n},\n\"lastUpdated\": 1419426021590,\n\"created\": 1419426021590,\n\"lastUpdatedTime\": \"2014-12-24T13:00:21Z\",\n\"createdTime\": \"2014-12-24T13:00:21Z\",\n\"UID\": \"_gid_PJwNlJ5N11BLPAXIls8ty6mDdjQD6XzMT2+N/zrztsM=\",\n\"oid\": \"3dfaa6836ac64711837cb98e3893007a\"\n}\n],\n\"objectsCount\": 1,\n\"totalCount\": 1,\n\"statusCode\": 200,\n\"errorCode\": 0,\n\"statusReason\": \"OK\",\n\"callId\": \"d126af8d2d21446d867fa67f61cef832\"\n}\n```\n```\nSELECT COUNT(*) FROM music\n```\n```\n{\"results\": [{ \"count(*)\": 1527}],\n\"objectsCount\": 1,\n\"totalCount\": 1527,\n\"statusCode\": 200,\n\"errorCode\": 0,\n\"statusReason\": \"OK\",\n\"callId\": \"11111\"}\n```\n```\nSELECT music.trackName, music.album, music.format FROM music WHERE music.musician=\"U2\" LIMIT\n```\n```\n{\"results\": [\n{\"music\": {\"trackName\": \"I will follow\", \"format\": \"mp3\"} },\n{\"music\": {\"trackName\": \"Into the Heart\", \"album\": \"Boy\", \"format\": \"mp3\" } },\n{\"music\": {\"trackName\": \"The Ocean\", \"album\": \"Boy\" } },\n{\"music\": {\"trackName\": \"A Day Without Me\", \"album\": \"Boy\", \"format\": \"mp3\" } },\n{\"music\": {\"trackName\": \"Shadowns and Tall Trees\", \"album\": \"Boy\", \"format\": \"mp3\" } } ],\n\"objectsCount\": 5,\n\"totalCount\": 1840,\n\"statusCode\": 200,\n\"errorCode\": 0,\n\"statusReason\": \"OK\",\n\"callId\": \"2222\" }\n```\n```\nSELECT music.trackName AS Track, music.album AS Disk, music.format AS Extension FROM music WH\n```\n\n```\nResponse to the query:\n```\n. Example of a query using contains. This query counts pictures of \"Madrid\":\n\n```\nResponse to the query\n```\n. Example of a query using regex. This query searches for photos starting with the letter \"A\".\n\n```\nResponse to the query:\n```\n```\n{\"results\": [\n{\"music\": {\"Track\": \"I will follow\", \"Extension\": \"mp3\" } },\n{\"music\": {\"Track\": \"Into the Heart\", \"Disk\": \"Boy\", \"Extension\": \"mp3\" } },\n{\"music\": {\"Track\": \"The Ocean\", \"Disk\": \"Boy\" } },\n{\"music\": {\"Track\": \"A Day Without Me\", \"Disk\": \"Boy\", \"Extension\": \"mp3\" } },\n{\"music\": {\"Track\": \"Shadows and Trees\",\"Disk\": \"Boy\", \"Extension\": \"mp3\" } } ],\n\"objectsCount\": 5,\n\"totalCount\": 1840,\n\"statusCode\": 200,\n\"errorCode\": 0,\n\"statusReason\": \"OK\",\n\"callId\": \"2222\" }\n```\n```\n{\"results\": [\n{\"music\": {\"Track\": \"I will follow\", \"Extension\": \"mp3\" } },\n{\"music\": {\"Track\": \"Into the Heart\", \"Disk\": \"Boy\", \"Extension\": \"mp3\" } },\n{\"music\": {\"Track\": \"The Ocean\", \"Disk\": \"Boy\" } },\n{\"music\": {\"Track\": \"A Day Without Me\", \"Disk\": \"Boy\", \"Extension\": \"mp3\" } },\n{\"music\": {\"Track\": \"Shadows and Trees\",\"Disk\": \"Boy\", \"Extension\": \"mp3\" } } ],\n\"objectsCount\": 5,\n\"totalCount\": 1840,\n\"statusCode\": 200,\n\"errorCode\": 0,\n\"statusReason\": \"OK\",\n\"callId\": \"2222\" }\n```\n```\nSELECT COUNT(*) FROM album WHERE album.photo.title CONTAINS \"Madrid\"\n```\n```\n{ \"results\": [ { \"count(*)\": 28 } ],\n\"objectsCount\": 1,\n\"totalCount\": 28,\n\"statusCode\": 200,\n\"errorCode\": 0,\n\"statusReason\": \"OK\",\n\"callId\": \"3333\" }\n```\n```\nSELECT album.photo.title FROM album WHERE album.photo.title = regex('A.*')\n```\n##### {\n\n```\n\"results\": [{\n\"album\": {\n\"photo\": {\n\"title:\"At the party\",\n\"title\": \"At the sea\",\n\"industry\": \"Computer Software\" }\n}\n}, {\n\"profile\": {\n\"name\": \"Andy Goslan\",\n\"religion\": \"Atea\",\n\"industry\": \"Computer Software\" }\n}\n],\n\"objectsCount\": 2,\n\"totalCount\": 2,\n\"statusCode\": 200,\n\"errorCode\": 0,\n\"statusReason\": \"OK\",\n```\n\n## ds.setSchema REST\n\n## Description\n\nThis method allows specifying a schema for a data type in Gigya's Data Store (DS). The schema sets eld names, data types,\n\nformatting and encryption as well as client side access restrictions. Data object schemas act as meta-data, guiding Gigya how to\n\nhandle the data in the specied elds.\n\n```\nDepending on schema setting, other elds can be added to the storage outside the schema, Gigya will add them as is\nwithout special treatment.\n```\n```\nField deletion: a eld in the Data object schema is eligible for deletion if no data has been saved to it. To delete a eld in the\nschema call ds.deleteSchemaFields.\n```\n```\nChanges to schema are incremental, when setting the schema for part of the elds, the properties of the omitted elds\nremain unchanged.\n```\n```\nUnless specied otherwise, schema dened elds are only accessible from the server.\n```\n## Request URL\n\n#### https://ds./ds.setSchema\n\nWhere is:\n\n#### us1.gigya.com - For the US data center.\n\n#### eu1.gigya.com - For the European data center.\n\n#### au1.gigya.com - For the Australian data center.\n\n#### eu2.gigya.com - For the European Azure data center.\n\n#### cn1.sapcdm.cn - For the Chinese data center.\n\n#### global.gigya.com - For all Global site groups.\n\nIf you are not sure of your site's data center, see Finding Your Data Center.\n\n## Parameters\n\n```\n\"callId\": \"1234567\"\n}\n```\n###  Note\n\n```\nFor security reasons this method is not available for client side SDKs, only for server side SDKs.\n```\n###  Note\n\n```\nIf you plan on integrating the DS, we highly recommend reading the Data Store Guide.\n```\n```\nThe DS is a premium platform that requires separate activation. If the DS is not part of your site package contact your Gigya\nCustomer Engagement Executive or email support@gigya-inc.com.\n```\n\n```\nRequired Name Type Description\n```\n```\ntype string A string indicating the type of\nthe object, equivalent to a\nschema name. The objective of\nthis eld is to classify objects as\nsharing the same schema.\n```\n```\ndataSchema JSON object A JSON object dening the\nschema to be set. See the\nformat denition of the Schema\nObject, below.\n```\n```\nformat string Determines the format of the\nresponse.\n```\n```\njson (default)\n```\n```\nhttpStatusCodes Boolean The default value of this\nparameter is false, which means\nthat the HTTP status code in\nSAP Customer Data Cloud's\nresponse is always 200 (OK),\neven if an error occurs. The\nerror code and message is given\nwithin the response data (see\nbelow). If this parameter is set\nto true, the HTTP status code in\nSAP Customer Data Cloud's\nresponse would reect an error,\nif one occurred.\n```\n## Authorization Parameters\n\nEach REST API request must contain identication and authorization parameters.\n\nSome REST APIs may function without these authorization parameters, however, when that occurs, these calls are treated as\n\nclient-side calls and all client-side rate limits will apply. In order to not reach client-side IP rate limits that may impact your\n\nimplementation when using server-to-server REST calls, it is Recommended Best Practice to always use an application key and\n\nsecret or a bearer token when sending requests. A non-exhaustive list of REST APIs that this may apply to are as follows:\n\n```\naccounts.login\n```\n```\nsocialize.login\n```\n```\naccounts.notifyLogin\n```\n```\nsocialize.notifyLogin\n```\n```\naccounts.nalizeRegistration\n```\n```\naccounts.linkAccounts\n```\nPlease refer to the Authorization Parameters section for details.\n\n###  Note\n\n```\nAs of January 31, 2023, you may no longer use a Partner Secret as a valid authentication method for requests to SAP Customer\nData Cloud servers.\n```\n\n## Schema Object\n\n```\nField Type Description\n```\n```\nelds JSON object This object denes properties per data\nelds. The object contains eld names and\ntheir corresponding list of properties (see\nthe example below). The eld name should\nbe the full path name with dots, i.e.\n\"work.address\".\n```\n```\nThe properties in option are:\n```\n```\ntype - Denes the data type of this\neld. The supported values are\n\"integer\", \"oat\", \"boolean\",\n\"string\", \"date\", \"long\", \"text\" and\n\"binary\".\n```\n```\nWhen the 'type' property is not\nspecied the type will be deduced\nfrom the eld name extension or\nautomatically according to the\ncontent of the rst item. When\ndening a 'binary' eld type, it is not\ninferred from the data must be\ndeclared explicitly through the\n'type' parameter.\n```\n```\nPlease note that eld's type cannot\nbe changed after it contains data.\n```\n```\nwriteAccess - Species whether to\nallow unsigned requests to write\ninto this eld. The supported values\nare:\n```\n```\n\"serverOnly\" (default ) -\nOnly signed requests\ncoming from the server are\nallowed.\n```\n```\n\"clientCreate\" - Unsigned\nrequests coming from the\nclient are allowed to write\ninto this eld, only if it\nwasn't set before.\n```\n```\n\"clientModify\" - Unsigned\nrequests coming from the\nclient are allowed to write\ninto this eld and modify\nexisting values.\n```\n```\nformat - Allows assigning a regular\nexpression that denes the format\nof this data eld. Gigya will verify\nthat data set in this data eld\nmatches the format. If the data set\nin this eld doesn't match the\nformat, Gigya will not set the data\n```\n\nField Type Description\n\n```\nand will return an error. The best\npractice is to validate the data\nformat on your client application.\nThe format property accepts a\nstring of the form: \"regex('')\". The\nregex syntax can be found in:\nRegular Expression Language\nReference.\n```\n```\nlanguages - An array of strings\ncontaining languages with which a\ntext eld is compatible, in addition\nto the default languages. A\nmaximum of four such languages\nare supported. The values passed in\nthis property are added to the\nexisting languages in the eld, and if\nthe total number exceeds four\nlanguages, the operation fails.\n```\n```\nencrypt - May be applied to string,\nbasic-string. Passing a value of\n'AES' (the encryption standard\napplied) sets the eld to encrypted.\nWhen string elds are encrypted,\nyou may use them in a search (e.g.\nusing accounts.search) only by\npassing an exact match (such as x =\n\"ABCDE\"), and not partial matches\n(x CONTAINS \"ABC\"). String search\nvalues are case sensitive.\n```\n```\nIf you set the encrypt\nproperty on a eld that\nalready contains data, the\nexisting data will remain un-\nencrypted. Only new data\nwill be encrypted.\n```\n```\nOnce a eld is set to\nencrypt, it cannot be\nundone.\n```\n```\nTo encrypt a eld that is not\nstring or basic-string, use\nthe\nencryptedNonSearchable\nparameter instead\n```\n```\nTo delete a eld from the schema, you\nmust ensure that data has never been\nsaved to it (even if said data has been\ndeleted), it has no dened type, and then\n```\n###  Note\n\n```\nThe only language currently\nsupported for this functionality\nis Japanese.\n```\n\n```\nField Type Description\n```\n```\nset it to null (see \"eld6\" in the example\nbelow). Saving data to a eld automatically\nassigns a type.\n```\n```\nSetting a eld's properties to null will reset\nthe writeAccess property to \"serverOnly\"\n(without deleting the eld), if the eld\ncontains/contained data and/or has a type\nsetting.\n```\n```\ndynamicSchema Boolean Species whether the schema is strict or\ndynamic. The default value of this\nparameter is true i.e. dynamic schema. In a\ndynamic schema you may add new elds\nthat are not dened in the schema to the\nDS. The new elds are automatically added\nto the dynamic schema. In a strict schema\nyou can only write into elds that are\nalready dened in the schema.\n```\n## Schema Object Example\n\n## Sample Requests\n\n##### {\n\n```\nfields: {\n\"field1\": {\nwriteAccess:\"clientCreate\",\nformat:\"regex('/^[a-z0-9_-]{3,16}$/')\"\n},\n\"field4\": {\ntype:\"float\"\n},\n\"field5\": {\ntype:\"string\",\nencrypt:\"AES\"\n},\n\"field6\": null,\n\"field7\": {\ntype:\"text\",\nlanguages:[\"ja\"]\n}\n},\ndynamicSchema: false\n}\n```\n\n## Response Data\n\n```\nField Type Description\n```\n```\napiVersion integer Denes the API version that returned the\nresponse and may not always be returned.\n```\n```\ncallId string Unique identier of the transaction, for\ndebugging purposes.\n```\n```\nerrorCode integer The result code of the operation. Code '0'\nindicates success, any other number\nindicates failure. For a complete list of error\ncodes, see the Error Codes table.\n```\n```\nerrorDetails string This eld will appear in the response only in\ncase of an error and will contain the\nexception info, if available.\n```\n```\nerrorMessage string A short textual description of an error,\nassociated with the errorCode, for logging\npurposes. This eld will appear in the\nresponse only in case of an error.\n```\n```\nCopyright Disclaimer Privacy Statement Legal Disclosure Trademark Terms of Use\n```\n\n```\nField Type Description\n```\n```\nfullEventName string The full name of the event that triggered\nthe response. This is an internally used\nparameter that is not always returned and\nshould not be relied upon by your\nimplementation.\n```\n```\ntime string The time of the response represented in\nISO 8601 format: yyyy-mm-dd-\nThh:MM:ss.SSSZ (for example, 2021-03-\n05T06:11:31.513Z)\n```\n```\nstatusCode integer The HTTP response code of the operation.\nCode '200' indicates success.\n```\n```\nThis property is deprecated and only\nreturned for backward compatibility.\n```\n```\nstatusReason string A brief explanation of the status code.\n```\n```\nThis property is deprecated and only\nreturned for backward compatibility.\n```\n### Response Example\n\n## ds.store REST\n\n## Description\n\nStores an object data in SAP Customer Data Cloud's Data Store (DS). The Data Store is only available for use with fully registered\n\naccounts.\n\n## Request URL\n\n#### https://ds./ds.store\n\nWhere is:\n\n#### us1.gigya.com - For the US data center.\n\n##### {\n\n```\n\"statusCode\": 200,\n\"errorCode\": 0,\n\"statusReason\": \"OK\",\n\"callId\": \"31ba039fb8d340ceb2f43d52c89bf187\",\n\"time\": \"2015-03-22T11:42:25.943Z\"\n}\n```\n###  Note\n\n```\nIf you plan on integrating the DS, we highly recommend reading the Data Store Guide. The DS is part of the Customer Identity\npremium package that requires separate activation. If the DS is not part of your site package contact your SAP Customer Data\nCloud Customer Engagement Executive or email support@gigya-inc.com.\n```\n\n#### eu1.gigya.com - For the European data center.\n\n#### au1.gigya.com - For the Australian data center.\n\n#### eu2.gigya.com - For the European Azure data center.\n\n#### cn1.sapcdm.cn - For the Chinese data center.\n\n#### global.gigya.com - For all Global site groups.\n\nIf you are not sure of your site's data center, see Finding Your Data Center.\n\n## Parameters\n\n```\nRequired Name Type Description\n```\n```\ndata JSON object Species the data to store. The data object\nshould be specied as a JSON object\ncomplying with the following restrictions:\n```\n```\nA maximum size of 512K of data.\n```\n```\nUser dened eld names must\nbegin with a character and may\ncontain characters, digits and\nunderscores.\n```\n```\nWe highly recommend that you give\nevery eld a type specication by\nappending the type to the eld\nname in the following manner: \"_\".\nValid types are:\n```\n```\ni - an integer number (may\ncontain 64bit long values\nas well), allows exact\nmatching or range\nsearches.\n```\n```\nf - a oating point number,\nallows exact matching or\nrange searches.\n```\n```\ns - a string only allows\nexact matching.\n```\n```\nt - a full text search eld,\nallows for partial searching\nbased on keywords.\n```\n```\nb - Boolean.\n```\n```\nd - a date eld, allows exact\nmatching or range\nsearches. The valid date\nformats are:\n```\n```\nStandard ISO time\nformat (like \"2011-\n07-\n14T11:42:32.123+3\",\nmay be specied\n```\n\nRequired Name Type Description\n\n```\nwithout a time at all\nor without a time\nzone)\n```\n```\n\"YYYY-MM-DD\nHH:MM:SS\"\n```\n```\nWhen the eld type is not specied\nexplicitly we will try to auto detect\nit. Fields that fail auto detection will\nbe considered strings.\n```\n```\nFor example:\n```\n```\n{ rstName_s : \"david\", birthDate_d : \"1978-\n07-22\", about_t : \"I love tracking,...\",\nacademicDegree : { university_s:\n\"Berkeley\", degree_s: \"MBA\",\ndepartment_s: \"Business\", courses : [{...},\n{...},...] }, hobbies_s: [\"running\", \"music\",\n\"movies\"]}\n```\n```\nImportant\n```\n```\nWhen saving data as a nested eld, it is\nimportant to save the object in the format\nbelow:\n```\n```\nand not as:\n```\n```\nDS always returns an object as it was\nsubmitted, this is different than other SAP\nCustomer Data Cloud schemas, which\nexpand nested objects automatically.\n```\n```\ntype string A string indicating the type of the object,\nequivalent to a name classifying objects as\nbeing of the same type; used in searches\nand when applying schemas.\n```\n###  Note\n\n```\nWhen dening a 'binary' eld\ntype, it is not inferred from the\ndata, and must be set explicitly\nusing the 'setSchema' method.\n```\n```\n// Correct\n{\n'a': {\n'b': 'value'\n}\n}\n```\n```\n// Incorrect\n{\na.b:'value'\n}\n```\n\n```\nRequired Name Type Description\n```\n```\noid string A unique object identier. If this parameter\nis set with the \"auto\" value, SAP Customer\nData Cloud will generate a unique ID for the\nobject.\n```\n```\nUID string A unique ID of a user. Setting this\nparameter associates the data object with\nthe specied user. The identier of this\nobject is the compound of oid and UID.\n```\n```\nupdateBehavior string This parameter denes how to handle\nconicting updates. The parameter may\nreceive one of the following values:\n```\n```\n\"arrayPush\" (default) - will cause\narrays data provided with this API\ncall to be appended to existing\narrays data in the DB.\n```\n```\n\"arraySet\" - will replace the content\nof existing arrays data in the DB\nwith the values of arrays data\nprovided with this API call.\n```\n```\n\"replace\" - will cause the entire\nobject data in the DB to be\nreplaced with the new data\nprovided with this call.\n```\n```\nformat string Determines the format of the response.\n```\n```\njson (default)\n```\n```\ncontext string/JSON This parameter may be used to pass data\nthrough the current method and return it,\nunchanged, within the response.\n```\n```\nignoreInterruptions Boolean This may be used in some cases to\nsuppress logic applied by the Web SDK,\nsuch as automatic opening of screens (e.g.,\nin a registration completion scenario). This\nparameter may not be used with REST\nAPIs.\n```\n```\nhttpStatusCodes Boolean The default value of this parameter is false,\nwhich means that the HTTP status code in\nSAP Customer Data Cloud's response is\nalways 200 (OK), even if an error occurs.\nThe error code and message is given within\nthe response data (see below). If this\nparameter is set to true, the HTTP status\ncode in SAP Customer Data Cloud's\nresponse would reect an error, if one\noccurred.\n```\n## Authorization Parameters\n\n\nEach REST API request must contain identication and authorization parameters.\n\nSome REST APIs may function without these authorization parameters, however, when that occurs, these calls are treated as\n\nclient-side calls and all client-side rate limits will apply. In order to not reach client-side IP rate limits that may impact your\n\nimplementation when using server-to-server REST calls, it is Recommended Best Practice to always use an application key and\n\nsecret or a bearer token when sending requests. A non-exhaustive list of REST APIs that this may apply to are as follows:\n\n```\naccounts.login\n```\n```\nsocialize.login\n```\n```\naccounts.notifyLogin\n```\n```\nsocialize.notifyLogin\n```\n```\naccounts.nalizeRegistration\n```\n```\naccounts.linkAccounts\n```\nPlease refer to the Authorization Parameters section for details.\n\n## Sample Requests\n\n###  Note\n\n```\nAs of January 31, 2023, you may no longer use a Partner Secret as a valid authentication method for requests to SAP Customer\nData Cloud servers.\n```\n\n## Response Data\n\n```\nField Type Description\n```\n```\napiVersion integer Denes the API version that returned the\nresponse and may not always be returned.\n```\n```\ncallId string Unique identier of the transaction, for\ndebugging purposes.\n```\n```\nerrorCode integer The result code of the operation. Code '0'\nindicates success, any other number\nindicates failure. For a complete list of error\ncodes, see the Error Codes table.\n```\n```\nerrorDetails string This eld will appear in the response only in\ncase of an error and will contain the\nexception info, if available.\n```\n```\nerrorMessage string A short textual description of an error,\nassociated with the errorCode, for logging\npurposes. This eld will appear in the\nresponse only in case of an error.\n```\n```\nCopyright Disclaimer Privacy Statement Legal Disclosure Trademark Terms of Use\n```\n\n```\nField Type Description\n```\n```\nfullEventName string The full name of the event that triggered\nthe response. This is an internally used\nparameter that is not always returned and\nshould not be relied upon by your\nimplementation.\n```\n```\ntime string The time of the response represented in\nISO 8601 format: yyyy-mm-dd-\nThh:MM:ss.SSSZ (for example, 2021-03-\n05T06:11:31.513Z)\n```\n```\nstatusCode integer The HTTP response code of the operation.\nCode '200' indicates success.\n```\n```\nThis property is deprecated and only\nreturned for backward compatibility.\n```\n```\nstatusReason string A brief explanation of the status code.\n```\n```\nThis property is deprecated and only\nreturned for backward compatibility.\n```\n```\noid string The object's unique identier. The value is\neither the oid parameter that you specied\nin the API call or a unique string generated\nby SAP Customer Data Cloud (if you have\nset the parameter to be \"auto\").\n```\n### Response Example\n\n##### {\n\n```\n\"oid\": \"8b8972c3b3114db2a0acdfa2617693bf\",\n\"statusCode\": 200,\n\"errorCode\": 0,\n\"statusReason\": \"OK\",\n\"callId\": \"bcb794e7b8ca41b1b3baf99e7bc1c86a\",\n\"time\": \"2015-03-22T11:42:25.943Z\"\n}\n```",[],[408],{"_104":417,"_97":418,"_161":419,"_163":-5,"_164":146,"_165":145,"_167":118,"_106":420,"_101":421,"_169":231,"_171":422,"_172":22,"_173":-5,"_174":423,"_100":424},"003a65ba-162e-11f1-a2c6-42dde27851f2","groups.tsx","ef69929c-162d-11f1-919a-42dde27851f2",["D",1772452225322],4,"/** @jsxImportSource https://esm.sh/hono@4.0.0/jsx */\n\nimport { Hono } from \"https://esm.sh/hono@4.0.0\";\n\nconst app = new Hono();\napp.onError((err, c) => {\n throw err;\n});\n\nconst GIGYA_DOMAIN = Deno.env.get(\"GIGYA_DOMAIN\") || \"accounts.eu1.gigya.com\";\nconst GIGYA_API_KEY = Deno.env.get(\"GIGYA_API_KEY\") || \"\";\nconst GIGYA_APP_KEY = Deno.env.get(\"GIGYA_APP_KEY\") || \"\";\nconst GIGYA_APP_SECRET = Deno.env.get(\"GIGYA_APP_SECRET\") || \"\";\n\n// ── Gigya API helper ───────────────────────────────────────────\nasync function makeGigyaRequest(\n endpoint: string,\n params: Record,\n): Promise {\n const url = `https://${GIGYA_DOMAIN}/${endpoint}?httpStatusCodes=true`;\n const body = new URLSearchParams({\n apiKey: GIGYA_API_KEY,\n userKey: GIGYA_APP_KEY,\n secret: GIGYA_APP_SECRET,\n ...params,\n });\n const response = await fetch(url, {\n method: \"POST\",\n headers: { \"Content-Type\": \"application/x-www-form-urlencoded\" },\n body,\n });\n if (!response.ok) {\n const text = await response.text();\n throw new Error(`HTTP ${response.status}: ${text}`);\n }\n const result = await response.json();\n if (result.errorCode !== 0) {\n throw new Error(\n `Gigya API Error ${result.errorCode}: ${\n result.errorMessage || \"Unknown error\"\n }`,\n );\n }\n return result;\n}\n\n// ── Action definitions ─────────────────────────────────────────\nconst ACTIONS = [\n {\n id: \"addToGroup\",\n label: \"Add to Group\",\n icon: \"👥\",\n desc: \"Assign selected users to a Gigya group\",\n params: [\n { key: \"groupID\", label: \"Group\", type: \"group_select\", required: true },\n {\n key: \"roleSetID\",\n label: \"Role Set ID (optional)\",\n type: \"text\",\n placeholder: \"e.g. member\",\n },\n {\n key: \"data\",\n label: \"Membership Data (JSON)\",\n type: \"json\",\n placeholder: '{\"tier\":\"gold\"}',\n },\n ],\n },\n {\n id: \"removeFromGroup\",\n label: \"Remove from Group\",\n icon: \"🚫\",\n desc: \"Remove selected users from a group\",\n params: [\n { key: \"groupID\", label: \"Group\", type: \"group_select\", required: true },\n ],\n },\n {\n id: \"updateRelationship\",\n label: \"Update Relationship\",\n icon: \"🔗\",\n desc: \"Modify group relationship / membership data\",\n params: [\n { key: \"groupID\", label: \"Group\", type: \"group_select\", required: true },\n {\n key: \"relationshipData\",\n label: \"Relationship Data (JSON)\",\n type: \"json\",\n placeholder: '{\"role\":\"admin\",\"tier\":\"vip\"}',\n },\n ],\n },\n {\n id: \"sendInvitation\",\n label: \"Send Invitation\",\n icon: \"✉️\",\n desc: \"accounts.groups.invitation.send — invite users to a group by email\",\n params: [\n { key: \"groupId\", label: \"Group\", type: \"group_select\", required: true },\n {\n key: \"model\",\n label: \"Model ID\",\n type: \"text\",\n required: true,\n placeholder: \"e.g. playground-access\",\n },\n {\n key: \"type\",\n label: \"Invitation Type\",\n type: \"select\",\n required: true,\n options: [\"emailLink\"],\n default: \"emailLink\",\n },\n {\n key: \"channel\",\n label: \"Email Channel Override\",\n type: \"text\",\n placeholder: \"Leave blank — uses each user's profile.email\",\n },\n {\n key: \"memberInfo\",\n label: \"Member Info (JSON)\",\n type: \"json\",\n placeholder: '{\"firstName\":\"Jane\",\"lastName\":\"Doe\"}',\n },\n {\n key: \"adminInfo\",\n label: \"Admin / Inviter Info (JSON)\",\n type: \"json\",\n placeholder: '{\"firstName\":\"Admin\",\"lastName\":\"User\"}',\n },\n {\n key: \"language\",\n label: \"Language\",\n type: \"text\",\n placeholder: \"en\",\n default: \"en\",\n },\n {\n key: \"relationship\",\n label: \"Relationship Data (JSON)\",\n type: \"json\",\n placeholder: '{\"emailDomain\":\"sap.com\"}',\n },\n {\n key: \"permissions\",\n label: \"Permissions (comma-sep)\",\n type: \"text\",\n placeholder: \"groupRead,groupWrite,membersInvite,membersRemove\",\n },\n ],\n },\n {\n id: \"setAccountData\",\n label: \"Update Account Data\",\n icon: \"📝\",\n desc: \"Bulk-update custom data / profile fields\",\n params: [\n {\n key: \"data\",\n label: \"Data Fields (JSON)\",\n type: \"json\",\n placeholder: '{\"newsletter\":true,\"tier\":\"premium\"}',\n },\n {\n key: \"profile\",\n label: \"Profile Fields (JSON, optional)\",\n type: \"json\",\n placeholder: '{\"age\":30}',\n },\n ],\n },\n {\n id: \"sendEmail\",\n label: \"Send OTP / Email\",\n icon: \"📧\",\n desc: \"Trigger an OTP email for selected users\",\n params: [\n {\n key: \"lang\",\n label: \"Language\",\n type: \"text\",\n placeholder: \"en\",\n default: \"en\",\n },\n ],\n },\n] as const;\n\ntype ActionId = typeof ACTIONS[number][\"id\"];\n\n// ── Shared CSS ─────────────────────────────────────────────────\nconst STYLES = `\n .step-inactive{opacity:.4;pointer-events:none}\n .tag{display:inline-flex;align-items:center;gap:4px;background:#e0e7ff;color:#3730a3;border-radius:9999px;padding:2px 10px;font-size:12px;font-weight:600}\n .badge-success{background:#dcfce7;color:#166534}\n .badge-error{background:#fee2e2;color:#991b1b}\n .result-row-ok{border-left:3px solid #22c55e}\n .result-row-err{border-left:3px solid #ef4444}\n .spin{animation:spin 1s linear infinite}\n @keyframes spin{to{transform:rotate(360deg)}}\n .user-row.selected{background:#eff6ff}\n .user-row{transition:background .1s}\n .user-row:hover{background:#f8fafc}\n .action-card{cursor:pointer;border:2px solid #e5e7eb;border-radius:12px;padding:16px;transition:all .15s}\n .action-card:hover{border-color:#6366f1;background:#f5f3ff}\n .action-card.selected{border-color:#6366f1;background:#eef2ff}\n .step-header{display:flex;align-items:center;gap:12px;margin-bottom:16px}\n .step-num{width:32px;height:32px;border-radius:9999px;display:flex;align-items:center;justify-content:center;font-weight:700;font-size:14px}\n .step-num.done{background:#22c55e;color:#fff}\n .step-num.active{background:#6366f1;color:#fff}\n .step-num.idle{background:#e5e7eb;color:#9ca3af}\n .inv-note{background:#f0fdf4;border:1px solid #bbf7d0;border-radius:8px;padding:10px 14px;font-size:12px;color:#166534;margin-bottom:12px}\n .htmx-indicator{display:none}\n .htmx-request .htmx-indicator{display:inline-block}\n .htmx-request.htmx-indicator{display:inline-block}\n`;\n\n// ── Progress bar component ─────────────────────────────────────\nfunction ProgressBar({ step }: { step: number }) {\n const labels = [\n \"\",\n \"Define criteria\",\n \"Preview users\",\n \"Choose action\",\n \"Configure params\",\n \"Execute\",\n ];\n return (\n

\n {[1, 2, 3, 4, 5].map((i) => (\n <>\n \n {i < step ? \"✓\" : String(i)}\n

\n {i < 5 && (\n \n )}\n \n ))}\n

Step {step}: {labels[step]}

\n );\n}\n\n// ── Spinner SVG ────────────────────────────────────────────────\nfunction Spinner() {\n return (\n \n );\n}\n\n// ── Field renderer ─────────────────────────────────────────────\nfunction ParamField({ p, groups }: { p: any; groups: any[] }) {\n const base =\n \"w-full px-3 py-2 border border-gray-300 rounded-lg focus:outline-none focus:ring-2 focus:ring-indigo-500 text-sm\";\n const req = p.required ? * : null;\n\n const label = (\n \n {p.label}\n {req}\n \n );\n\n if (p.type === \"group_select\") {\n return (\n

\n {label}\n \n

\n );\n }\n\n if (p.type === \"select\") {\n return (\n

\n {label}\n \n

\n );\n }\n\n if (p.type === \"checkbox\") {\n return (\n

\n \n {p.label}\n {req}\n \n \n

\n );\n }\n\n if (p.type === \"json\" || p.type === \"textarea\") {\n return (\n

\n {label}\n \n {p.default ? JSON.stringify(p.default) : \"\"}\n \n {p.type === \"json\" && (\n

Enter valid JSON

\n )}\n

\n );\n }\n\n return (\n

\n {label}\n \n

\n );\n}\n\n// ══════════════════════════════════════════════════════════════\n// GET / — Shell page\n// ══════════════════════════════════════════════════════════════\napp.get(\"/\", (c) => {\n return c.html(\n \n \n \n \n Group Management\n

dinavinter

os