Dante and Luiz,
The request must be in the format:
{"key":"dc.XXX.YYY", "value":"Query"}
Example:
curl -k -4 -H "accept: application/json" -H "Content-Type:
application/json" -X POST "
https://demo.dspace.org/rest/items/find-by-metadata-field; -d
"{"key":"dc.title","value":"Test"}"
Hope this
I've updated the app with several fixes, including Item edit, Table style
and adding buttons to create an object directly inside some other object.
The only thing that is still missing is adding/removing metadata fields to
item's form. For now there are only title and author fields for new items
Hi,
On 09/15/2016 03:41 AM, Donald Bynum wrote:
I am using the XMLUI implementation. I cannot see any option in the
Administrative menu area to edit the license text. I have updated the
text in the default.license file in both the dspacesource\config
directory as well as the dspace\config
need help + 1
On Wed, Sep 14, 2016 at 3:57 PM, Dante Valencia
wrote:
> Hi friends
> I need help with understanding how to use (find-vy-metadata) with Rest
> For example, I do this in loggout
> try {
>
>
> DefaultHttpClient httpClient = new
Hi friends
I need help with understanding how to use (find-vy-metadata) with Rest
For example, I do this in loggout
try {
DefaultHttpClient httpClient = new DefaultHttpClient();
HttpPost postRequest = new HttpPost(
"http://10.3.11.134:8080/rest/logout;);
Yes Monika, I know - this is what I am doing now. And what I want is to
delegate ONLY this to somebody else. My reason to hope that it could be
possible is this:
- the policies are attached to resources
- the policies say who can perform an action on the resource (e.g.
ADD/REMOVE)
- the
Hello all,
Words in the full item view record abstract are being split between lines
when using Firefox and Internet Explorer.
Using the Firefox inspect tool we removed the word-break class and this
resulted in the expected display.
Which scss file should we edit in dspace-source to prevent
I am using the XMLUI implementation. I cannot see any option in the
Administrative menu area to edit the license text. I have updated the text
in the default.license file in both the dspacesource\config directory as
well as the dspace\config directory. But I still don't see any change when
> Hi Evgeni
>
> As far as I know only administrators can create accounts and change group
> memberships for other accounts
> So to enable a power user to change other users group memberships you will
> have to add that power user to the administrator group.
> This of cause will allow the
Awesome. That's good to hear. Thanks for the feedback, helix.
Regards,
On Sun, Sep 11, 2016 at 11:03 PM, helix84 wrote:
> Hi Alan, I filed a (non-public) security issue when it was first
> reported. Seems like an easy fix to just upgrade pdfbox, but we'll
> still have to
I need to authorize a user (a group) to create users and add/delete them to
one other group.
In DSpace-Manual I see things like "custom policy" (policy_id: 4847;
resource_type_id: 2; resource_id: 89; ...). There are "DSpace types"
(Bitstream: 0; ... Group: 6; Eperson: 7).
But I can not figure
Hello,
I'm currently setting up our dspace instance and doing a few changes to
customize it. Till. ex. some changes in
[dspace-source]/config/input-forms.xml and
[dspace-source]/config/registries/dublin-core-types.xml to support DOI.
Now I wonder what the best way is to preserve this changes
Is there a "canonical" way of moving collections to different community? There
is some old advice on this, which involves direct modifications to the
database, and a recent one here:
https://gist.github.com/alanorth/392c4660e8b022d99dfa
Is this still the way to do this?
br,
Ilja Sidoroff
This seems to be a common question, so I detailed it here:
https://wiki.duraspace.org/display/DSPACE/TechnicalFAQ#TechnicalFAQ-MetadatavaluesinCSVexportseemtohaveduplicatecolumns
Regards,
~~helix84
Compulsory reading: DSpace Mailing List Etiquette
14 matches
Mail list logo