Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Current »





The feed method works when the application transmits the information to GEODI in case of changes in data or privileges. GEODI Functions as the opposite of the service connection method.

 In this method information of an authorized user that has rights add data layer on GEODI is needed.You can use this method to send as many content as you want at any time if your application is standing, if there are internal methods to trigger, or if you don't have a Web application

*  If you have a question you can check the Frequently Asked Questions .


Multiple Content Feed

BulkFeed
DefinitionThe contents are forwarded to GEODI as a result of a BulkFeed call. GEODI only returns status information without waiting for the call. Suitable for sending multiple contents. Feed method is more convenient for sending single content.
Request

[GEODIURL]/FeedHandler?op=BulkFeed&Content=[ContentJson]&UserSession=[Token]

  • UserSession: The feed authorized Token to be received from the system administrator must be specified. The Token rendering interface can be accessed from [geodiurl] / API ( Geodi REST API )
  • wsName (Optional): wsName must be passed if the provided Token is authorized to feed multiple projects.
  • enumeratorID (Optional): The enumeratorID must be passed if the provided Token is authorized to feed multiple sources (geodi enumerator).
HttpMethodGET, POST
Expected Errors

401 Unauthorized access / Access denied

403 Forbidden

511 Network Authentication Required

501 Server Error

470 Unsupported extension, Server configuration error

471 Content Required

481 This Token cannot access any workspaces

453 wsName Required - If Token can feed multiple projects, wsname is required.

452 enumeratorID Required  - If Token can feed multiple projects, enumeratorID is required.

480 wsname or enumeratorID is not accessible - Token does not have sufficient authority


Return Value

OK is returned.

  • Indicates that scanning has started. If no error is received, the scan starts. It is not necessary to check the result.
Examples
//Request : 
[ServiceURL]/FeedHandler?op=BulkFeed&UserSession=[Token]&content=
 {
	Contents : 
	[
		{ 
			ContentURL : '~/MyApplication/Content.php?id=1811',
			DisplayName:'Document1',
			ContentDate:'Wed, 06 May 2015 10:15:20 GMT',
			ViewURL : '~/MyApplication/ContentView.php?id=1811&wsName={wsName}',
			Permission : {   Permit : ['S-151...','Role2','Role3']  },
            MetaData:  [
					 { Name:"Description", Value:"This document is ...... ... " } 
				]

		},
		{ 
			ContentURL : '~/MyApplication/Content.php?id=1812',
			DisplayName:'Document2',
			ContentDate:'Wed, 06 May 2015 10:15:20 GMT',
			ViewURL : '~/MyApplication/ContentView.php?id=1812&wsName={wsName}',
			Permission : {   Permit : ['S-151...','Role2','Role3']  }
		},
		{ 
			ContentURL : '~/MyApplication/Content.php?id=1813',
			DisplayName:'Document3',
			ContentDate:'Wed, 06 May 2015 10:15:20 GMT',
			ViewURL : '~/MyApplication/ContentView.php?id=1813&wsName={wsName}',
			Permission : {   Permit : ['S-151...','Role2','Role3']  }
		},
	]
 }
Example application


Single Content Feed

Feed
DefinitionThe contents are forwarded to GEODI as a result of a BulkFeed call. GEODI only returns status information without waiting for the call. Suitable for sending multiple content. Feed method is more convenient for sending single content.
Request

[GEODIURL]/FeedHandler?op=Feed&Content=[ContentJson]&UserSession=[Token]

  • content: A JSON object that contains content information.Object details can be reached from Geodi ContentObject - İçerik Tanım Nesnesi#İçerikTanımNesnesi-Tekİçerik document. JSON can grow more than expected. It should be preferred to send by POST.
  • UserSession: The feed authorized Token to be received from the system administrator must be specified. The Token rendering interface can be accessed from [geodiurl] / API ( Geodi REST API )
  • wsName (Optional): wsName must be passed if the provided Token is authorized to feed multiple projects.
  • enumeratorID (Optional): The enumeratorID must be passed if the provided Token is authorized to feed multiple sources (geodi enumerator).
HttpMethodGET,POST
Expected Errors

401 Unauthorized access / Access denied

403 Forbidden

511 Network Authentication Required

501 Server Error

470 Unsupported extension, Server configuration error

471 Content Required

481 This Token cannot access any workspaces

453 wsName Required - If Token can feed multiple projects, wsname is required.

452 enumeratorID Required  - If the Token can feed multiple projects, enumeratorID is required.

480 wsname or enumeratorID is not accessible - Token does not have sufficient authority

Return Value

OK is returned.

  • Indicates that scanning has started. If no error is received, the scan starts. It is not necessary to check the result.
Examples
//Request : 
[ServiceURL]/FeedHandler?op=Feed&UserSession=[Token]&content=
{ 
	ContentURL : '~/MyApplication/Content.php?id=1811',
	DisplayName:'New Document',
	ContentDate:'Wed, 06 May 2015 10:15:20 GMT',
	ViewURL : '~/MyApplication/ContentView.php?id=1811',
	Permission : {   Permit : ['S-151...','Role2','Role3']  }
}
Example applications

Sub Content Feed

BulkFeed
Definition

You can add sub-content to a content in GEODI. There are two methods for this.

If no authorization is defined for a child content, it inherits the rights of the parent. If authorization is defined, only the privileges defined are used. It does not inherit from the parent.


1. You can use the ParentContentIdOrURL value if you want to link the content you feed at any time to earlier content.

  [
  		{
            ContentURL : '.../MyApplication/Content.php?id=1810',
            DisplayName:'Main Document1',
            ContentDate:'Wed, 06 May 2015 10:15:20 GMT',
            Permission : {   Permit : ['S-151...','Role2','Role3']  },
            MetaData:  [
                     { Name:"Description", Value:"This document ...... ... " }
                ]
         },
        {
            ContentURL : '.../MyApplication/Content.php?id=1811',
            DisplayName:'Document1',
            ContentDate:'Wed, 06 May 2015 10:15:20 GMT',
            Permission : {   Permit : ['S-151...','Role2','Role3']  },
            MetaData:  [
                     { Name:"Description", Value:"This document ...... ... " }
                ],
			ParentContentIdOrURL :'.../MyApplication/Content.php?id=1810'
         }
	]

2. Subcontents of main content can be passed in bulk with the SubContents object.

[
  	{
        ContentURL : '.../MyApplication/Content.php?id=1810',
        DisplayName:'Main Document1',
        ContentDate:'Wed, 06 May 2015 10:15:20 GMT',
        Permission : {   Permit : ['S-151...','Role2','Role3']  },
        MetaData:  [
            { Name:"Description", Value:"This document ...... ... " }
        ]
    },
    SubContents: [ {
        ContentURL : '.../MyApplication/Content.php?id=1811',
        DisplayName:'Doküman1',
        ContentDate:'Wed, 06 May 2015 10:15:20 GMT',
        Permission : {   Permit : ['S-151...','Role2','Role3']  },
        MetaData:  [
             { Name:"Description", Value:"This document ...... ... " }
        ]
    } ]
]





  • No labels