I am trying to add a bitstream to an Item through Postman.When I post , I chose body as "form-data" and added a key as "file" and selected a file.In addition to it I have given key as "name" and value as the file name. It is getting successfully added to the Item but the name is null.
I assume you use DSpace 6.
First: Make sure you are logged in. Get the JSESSIONID cookie by calling
Post: http://yourserver.com/rest/login
with Query Params email and password
Then: Post the Bitstream like this
Post: http://yourserver.com/rest/items/your-item-id/bitstreams
Add the file under Body and select binary:
Set filename and description as Query Params:
Hit send.
Related
I have a Splunk dashboard where you have a table with selected encoded identifiers.
You can click on a row and select an identifier as a token which fills additional fields with data. Now on the intranet of my company we have a url where you can enter the encoded identifier and get back the decoded data in a GET request.
Right now I have a single-value field which displays the encoded identifier and when you click on it it makes a call to the decoder and opens the decoded result in a new tab. That's a standard Splunk link.
Is it possible to make Splunk call the URL automatically (do a GET request) when the identifier is selected (the token is set) and retrieve the response data as a string and extract (using regex) and display the decoded data automatically in the single value field?
If not, is it at least possible for Splunk to get the response data as a string instead of opening the result in a new tab when you click on the encoded identifier?
If I understand you correctly, you want to have the drilldown target be an external link.
If that is correct, just put the external URL in the drilldown:
If you want some value from an external link to be pulled-into Splunk, then you'll need to setup another mechanism.
For example, you might have a scripted input that will query an external endpoint, and add results to an index or lookup table.
Or you might utilize a REST endpoint app to achieve something similar.
I am trying to build a flow, where I want to show an URL(hyperlink) in the response, which on click will open another flow end-point.
Example:
GET /list
output:
{
"object" :{
"accounts" : **url**,
"customer" : **url**
}
}
I want to add the hyperlink in the url (show in bold in output), which on clicking will open another flow passing either "accounts" or "customer" to the other flow as end-point.
Thanks in advance
The example indicates that the response is a JSON and I guess you are receiving it from a browser. You can add the hyperlink as the value of the attributes. However JSON doesn't have an URL data type, so the URLs will need to be strings, surrounded by quotes. Note that it is up to the browser to decide if those URLs are 'clickable' or just plain text.
I have a "copy data" activity making a REST call to get some data in json format. The data should then be transfered to a SQL database.
The problem is I can only get a certain amount of data for the specified HTTP request. For this I need to implement pagination rules, and I have tried to understand this documentation: https://learn.microsoft.com/en-us/azure/data-factory/connector-rest#pagination-support
The HTTP response returns the absolute URL for the next request in the header, with the field named "Link". As I can see in the documentation, it is supposed to be possible to get the value from "Link" and put it into a pagination rule.
As stated in the documentation:
Next request’s absolute or relative URL = header value in current response headers
It says supported pagination keys are AbsoluteUrl, with the value of this should be set like this:
Headers.response_header OR Headers['response_header']
Where the response_header is defined like this in the docs:
"response_header" is user-defined which references one header name in the current HTTP response, the value of which will be used to issue next request.
What I can't seem to understand is how this "response_header" can be set to reference the HTTP response header value of "Link".
You need to replace the 'response_header' placeholder with your header name.
In your case - 'Link'
Or in code editor:
"paginationRules": {
"AbsoluteUrl": "Headers['Link']"
}
I am using Postman software to test update field of an item in Podio. The field is 'consomme-en-jh'. The value is updated in Podio with an empty value. Do I forget a key value in the body or another thing?[]
Looks like you are trying to use this api method: https://developers.podio.com/doc/items/update-item-field-values-22367
Please read docs on how to use it and follow cUrl example.
It's hard to tell from your screenshot, but verify:
Url should be like:
https://api.podio.com/item/<item-id>/value/<field-id>
Method is
PUT
Body is new value (and it depends on your field type, value
might be very different)
I'm implementing a Compony newsfeed on a website and ran into the following problem. The LinkedIn API doesn't provide a direct URL to a company update. Looking at the LinkedIn site there are direct URL's and they're like this for example:
https://www.linkedin.com/company/1441/comments?topic=5849556347070205952&type=U&scope=1441&stype=C&a=5uHW&goback=%2Ebzo_*1_*1_*1_*1_*1_*1_*1_1441
Trying stuff out it seems that the parameters topic, type, scope, stype and a are mandatory for the URL to work.. (goback is the only one that isn't).
Using the LinkedIn API with the Company updates call I'm able to buid the direct url, except for the a parameter. The value is always 4 (for me unexplainable) characters long.
Has anyone ever successfully build a direct URL to a company update or can someone maybe explain the a parameter or how to generate its value?
Updated to new format
You can link directly to any update (company or user) using the following url:
https://www.linkedin.com/feed/update/urn:li:activity:[topic_id]
You can get [topic_id] by getting the last bit of the updateKey in the api response from Linkedin. When updateKey = UPDATE-c7352-6410848097894756353, your topic_id = 6410848097894756353.
In your example that would become https://www.linkedin.com/feed/update/urn:li:activity:5849556347070205952 which links directly to the specific update. The post is too old to work with the new link format
The url used to be
https://www.linkedin.com/nhome/updates/?topic=[topic_id]
Updated thanks to the comment from #sethpollack
For anyone trying to get the topic id from the API response object (as already commented on the OP question), the topic id is the value after the last hyphen of the updateKey property, which can be used with #Daan answer:
"updateKey": "UPDATE-cXXXX-YYYYYYYYYYYYYYYYYY"
Direct URL:
https://www.linkedin.com/nhome/updates?topic=[YYYYYYYYYYYYYYYYYY]
Using the URL format above, get the topic_id by opening the update in its own window/tab, look at the page source code in your browser and search for the string :activity: the long number after the string is the infamous topic_id