# View a Publisher Profile [view data packages associated to a publisher or user]

As a Consumer i want to see the profile and activity of the user so that i can see how good that user is so that i can trust on his published data packages to reuse.

Activity and profile is stuff like: their list of data packages including how many they have published, how many person downloaded their data packages, how many followers the user has …

As a Consumer I want to find a publisher and see their profile so that [similar to registered user but also to find out who is involved] …

- Profile = published packages under this publisher and the registered users associated with this publisher [owner or member], their title etc (esp important to know if this is the world bank or not)
- so that: I can gather and know how complete the available published data for my research.

### Profile Activity:
As a publisher i want to keep track of my activity so that other users can see my profile reputation.

What are the profile activities:
1. Published data packages.
2. data publication history. [A time line of the publication]
3. How many followers.
4. Members of the publishers.

## See My Own Packages
As a Publisher owner I want to have a list of the data packages published by me (my member users) so that:
- other people can see how many great data packages i have
- I can find a data package i want to look at quickly
- I can find the link for a data package to send to someone else
- People want to share what they have done. This is probably the number one way the site gets prominence at the start (along with simple google traffic)
- So that I can check that members do not abuse their rights to publish and only publish topical data packages.

Other points:
- What are the permissions here?
- Do we show your own private data packages to you (Yes!)
- What data packages to show?
- Publishers of which i am the owner
- Publishers of which i am member to.
- Do we distinguish: “Your” publisher vs publishers which are more organizational?

- What should be the attributes of a data package when some one views that.
- Number of share
- Number of downloads
- Number of stars

### Search among publishers packages
As a Consumer i want to search among all data packages owned by a publisher so that I can easily find one data package amongst all the data packages by this publisher.

- This should only by the name of the data packages

### Registered Users Packages
As a Registered User I want to see the data packages i am associated with so that I can easily find one data package I publisher.

- This should only by the name of the data packages

## Tasks

### Find a publisher

- Search publisher by name
- **dpr-api** [10]
- **dpr-js** search bar

### View a Publisher Profile

- Get publisher details via API
- name, descriptions ... [5]
- does API already exist?
- Get all list of packages of the publisher
- dpr-api [7] - should this not just be part of the GET publisher (can we inline the main data packages?)
- dpr-js
- Get metadata of the package [Repeat this for every packages] - would this be separate from the previous point?
- API for meta data preview [8]
- Front end for preview (?)

- Search packages in my own list (can we do this in page with the JS? if we load all packages?)
- Search Package API [6]

> Search packages packages with-in user and with-in publisher is a single api with a small database column change.

-----------------
## Task Details
### Browse Data Package
> Api /api/package/search

This is initial implementation of the search api. Right now will show all based on the sorted on updated date.
Response

{
    "packages": [
        {
            "name": "package1",
            "description": "",
            "private": true
        },
        {
        
        }
    ],
    "total": 152,
    "page":1,
    "limit": 10
}

Later we can add other search implementations.

### Publisher Profile
> Api /api/profile/{name}?type={publisher|user}

Response

{
    "name": "",
    "description":"",
    "package": {
        "page": 1,
        "limit": 10,
        "total": 91
        "packages": [ //will be generated by {package description}
            {
                "name": "package1",
                "description": "",
                "private": true
            },
            {
                "name": "package2",
                "description": "",
                "private": false
            }
        ]
    }
    
}

Server Side process:
- Get publisher details from ```publisher``` table
- Get paginated list of packages from ```package``` table
- Authorization will be ```Package::Read```
- if sysadmin or owner or member get all
- If not the query with ```filter(Package.private == false)```

Client Side Process:
- ???