ATG search API changes from 2006.3 to 9.1. i want the API differences so i can show them what we need to change
The changes go beyond the API differences. 9.1 Search is quite different from 2006.3 or 2007.1 I'd say there is no simple, short answer to your question that would fit this forum.
See
ATG 9.1 Search documentation: http://www.atg.com/repositories/ContentCatalogRepository_en/manuals/Search9.1/
ATG 2006.3 Search documentation:
http://www.atg.com/repositories/ContentCatalogRepository_en/manuals/Search2006.3/
Both link require ATG.com account.
Related
Moodle is a platform for creating training and educational material. By default, it is possible to make the content by clicking on controls.
GitHub is a place for version management and teamwork.
Question: I wondered if there is a way to (programmatically) populate/update a Moodle training from a GitHub repository. Does Moodle offer an API that would allow the implementation of such a functionality?
Idea:
The GitHub repository contains mark-down files in a specific format and folder structure.
Yes. Theoretically. Moodle offers an API (https://docs.moodle.org/dev/Web_service_API_functions) through which you can update courses along with much other functionality.
You would have to write the script yourself, of course. I've been briefly looking in to this as well, but the moodle webservice API is not intuitive and is underdocumented. There's been talk of making a more sensible, RESTful API (https://tracker.moodle.org/browse/MDL-49607) but it doesn't seem to have gotten anywhere.
I want to connect shopware6 with TYPO3.Tried the plugin shopware-typo3-connector but it is not compatible with shopware6. Is there any other possible way?
If you do not find a plugin the community store you can look out for a partner from the agency listing and reach out to a partner claiming to have TYPO3 experience. If you are not happy with the search of an agency you really want to build it on your own. I personally do not find it difficult to do but this often depends on the cases of data you want to connect. You likely want to look into the API of Shopware 6. You can find in the Shopware docs links to different APIs and how to use them. Likely you want to use the Admin API or write an app for Shopware 6. They have several guides (written and visual) in their docs. Depending on any follow up question you can post a new one here with the Shopware-6 tag.
I've been looking into NoSQL integration for Splunk using Hunk but there seems to be virtually no documentation on this process?
Is it possible? Are there docs?
I'm using Hunk 6.1
Specifically I am trying to use MongoDB as a backend datastore to splunk.
The short answer, is likely that there is no other NoSQL integrations out of the box and you'll have to roll your own for now.
Hunk has been marketed widely as Splunk for Hadoop and that is their first use case. (This can be seen in the Developer PDF still. General user documentation can be found http://docs.splunk.com/Documentation/Hunk/latest.
But the design of Hunk is that you define a "Virtual Index" that instead of connecting to and querying data from Splunk's built in indexes, you connect externally to another NoSQL data store. This requires a library to make requests to the NoSQL store and stream results back to Splunk (as can be seen in the diagram on this page)
I would suspect that they may expand the virtual index concept and ship libraries for other NoSQL datastores in the future as they have demand, but for now they have provided an example app that reportedly has documentation inside the app itself guide you on how to roll your own connecting library: http://apps.splunk.com/app/1802/
This functionality now exists with Hunk and the Hunk App for MongoDB. Here is the announcement : http://www.mongodb.com/presentations/splunks-hunk-powerful-way-visualize-your-data-stored-mongodb
The app is available here: https://apps.splunk.com/app/1810/
I hope that helps!
Facebook has introduced Field Expansion feature in Graph API to help developers to construct complex nested queries.
https://developers.facebook.com/docs/reference/api/field_expansion/
There is no doubt about the benefits this feature would give us. But what about the existing apps? Will this affect them or backward compatibility has been taken care?
I'm an engineer on the Platform team and worked on this feature. Everything is 100% backwards compatible; existing apps do not need to update.
From the document you linked - 'This is meant as an advanced feature with no cost on the simplicity of the basic Graph API.'
I don't see any reason this feature of the API wouldn't be compatible with the basic usage that's already in place. It would have been announced as a breaking change otherwise
My Application is affected. the daily_active_users, weekly_active_users, monthly_active_users on graph.facebook.com/{APP_ID} has been disappeared where did it go?
I am working on a Web Project similar to Google-Video.
As for now, I want to start coding the site.
I know some PHP, HTML and MySQL.
I already have:
Database built and ready (in MySQL)
Links and Tags in the Database
The thing is, I don't want to code everything from hand.
As I've seen so far, with CMS it's not possible to use my own database. Or am I wrong?
And what Framework would you suggest me?
Looking forward for your advice!
Thanks
You should probably start over, but use your existing DB design as your logical schema to be implemented in the CMS you eventually choose.
Go to http://cmsmatrix.org/ and compare Drupal, Joomla!, eZ Publish and TYPO3 for the best fit for your requirements.
Also, pay attention to the search engine features available with each one. e.g. eZ Publish eZ Find is based on Lucene.
In terms of functionality ( but excluding add management and your specific layout or graphic-design) you should be able to create a reasonable clone within a few hours using eZ. Here is one example http://untoldstories.eu/ezinfo/about